Opteamax GmbH: PeeringDB fix list

AS48200 · peeringdb.com/net/2250

PeeringDB

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

Make the changes on Opteamax 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 (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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs1G500M
    • In the entry with IPv4 80.249.211.172: set Speed to 500 (500M) (now 1000).

    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 differs1G10G
    • In the entry with IPv4 185.1.170.126: set Speed to 10000 (10G) (now 1000).
  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs3G10G
    • In the entry with IPv4 80.81.192.63: set Speed to 10000 (10G) (now 3000).
  4. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.210.135: set Speed to 10000 (10G) (now 1000).
  5. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.208.136: set Speed to 10000 (10G) (now 1000).

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