ixreport

NETSPEED: PeeringDB fix list

AS206375 · peeringdb.com/net/21496

PeeringDB

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

Make the changes on NETSPEED'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 (3)

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 differs100G5G
    • In the entry with IPv4 80.249.211.36: set Speed to 5000 (5G) (now 100000).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs100G800G
    • In the entry with IPv4 80.81.192.137: set Speed to 800000 (800G) (now 100000).
  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs100G1G
    • In the entry with IPv4 195.66.228.140: set Speed to 1000 (1G) (now 100000).

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