Medianova: PeeringDB fix list

AS21245 · peeringdb.com/net/10432

PeeringDB

5 things to fix in Medianova's PeeringDB record, from what its exchanges publish: 4 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Medianova'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 (4)

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 differs1G200G
    • In the entry with IPv4 185.1.170.108: set Speed to 200000 (200G) (now 1000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 80.81.194.74: set Speed to 200000 (200G) (now 100000).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 185.1.210.120: set Speed to 200000 (200G) (now 1000).
  4. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 185.1.208.118: set Speed to 200000 (200G) (now 1000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Medianova has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587Not on its IX-F export or website members list
    IPv4185.1.8.68
    IPv62001:7f8:73::52fd:0:1
    Speed100000 Mbps (100G)

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