ixreport

GOPAS Solutions: PeeringDB fix list

AS13157 · peeringdb.com/net/3623

PeeringDB

6 things to fix in GOPAS Solutions's PeeringDB record, from what its exchanges publish: 6 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on GOPAS Solutions'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 (6)

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
    IPv6 address missing from PeeringDBnone2001:7f8:1::a501:3157:1
    Port speed differs200M100M
    • In the entry with IPv4 80.249.211.22: set IPv6 to 2001:7f8:1::a501:3157:1 (now empty); set Speed to 100 (100M) (now 200).

    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 Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::3365:0:1
    Port speed differs200M1G
    • In the entry with IPv4 80.81.194.189: set IPv6 to 2001:7f8::3365:0:1 (now empty); set Speed to 1000 (1G) (now 200).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:3d::3365:0:1
    • In the entry with IPv4 185.1.210.32: set IPv6 to 2001:7f8:3d::3365:0:1 (now empty).
  4. Germany MegaIX Berlin Berlin, Germany · PeeringDB 209
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8:5:0:3365:0:1
    • In the entry with IPv4 194.9.117.57: set IPv6 to 2001:7f8:8:5:0:3365:0:1 (now empty).

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

  5. Germany MegaIX Dusseldorf Dusseldorf, Germany · PeeringDB 91
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8::3365:0:1
    • In the entry with IPv4 194.146.118.86: set IPv6 to 2001:7f8:8::3365:0:1 (now empty).

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

  6. Germany MegaIX Hamburg Hamburg, Germany · PeeringDB 291
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8:10:0:3365:0:1
    • In the entry with IPv4 193.42.155.36: set IPv6 to 2001:7f8:8:10:0:3365:0:1 (now empty).

    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/13157/: 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.