DNS:NET Internet Service: PeeringDB fix list

AS15366 · peeringdb.com/net/1138

PeeringDB

5 things to fix in DNS:NET Internet Service's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on DNS:NET Internet Service'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 BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 193.178.185.16: set Speed to 200000 (200G) (now 100000).

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

  2. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 185.1.170.194: set Speed to 200000 (200G) (now 10000).
  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 80.81.194.30: set Speed to 200000 (200G) (now 100000).
  4. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 185.1.210.175: set Speed to 200000 (200G) (now 10000).
  5. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 185.1.208.169: set Speed to 200000 (200G) (now 10000).

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