ixreport

Open Peering: PeeringDB fix list

AS20562 · peeringdb.com/net/821

PeeringDB

5 things to fix in Open Peering's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Open Peering'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 (5)

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 DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.170.45: set Speed to 100000 (100G) (now 10000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.210.64: set Speed to 100000 (100G) (now 10000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.208.53: set Speed to 100000 (100G) (now 10000).
  4. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 195.66.225.53: set Speed to 100000 (100G) (now 30000).
  5. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G12.5G
    • In the entry with IPv4 185.0.20.18: set Speed to 12500 (12.5G) (now 100000).

From ixreport.com/net/20562/: 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.