ixreport

aurologic GmbH: PeeringDB fix list

AS30823 · peeringdb.com/net/8850

PeeringDB

2 things to fix in aurologic GmbH's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 21:56 UTC.

Make the changes on aurologic GmbH's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (2)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany ERA-IX Frankfurt Frankfurt, Germany · PeeringDB 4630
    ProblemPeeringDB hasThe export has
    Port speed differs200G100G
    • In the entry with IPv4 185.0.27.12: set Speed to 100000 (100G) (now 200000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G200G + 100G
    • In the entry with IPv4 178.18.237.64: set Speed to 100000 (100G) (now 200000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

From ixreport.com/net/30823/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.