NerdNet: PeeringDB fix list

AS5418 · peeringdb.com/net/800

PeeringDB

One thing to fix in NerdNet's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on NerdNet'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 (1)

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 NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.119.5 193.239.119.6193.239.116.23 193.239.119.5 193.239.119.6
    IPv6 address missing from PeeringDB2001:7f8:13::a500:5418:1 2001:7f8:13::a500:5418:22001:7f8:13::a500:5418:1 2001:7f8:13::a500:5418:2 2001:7f8:13::a500:5418:3
    • In the entry with IPv4 193.239.119.5: set IPv4 to 193.239.116.23 (now 193.239.119.5).
    • In the entry with IPv4 193.239.119.6: set IPv6 to 2001:7f8:13::a500:5418:3 (now 2001:7f8:13::a500:5418:2).
    • Add an entry: IPv4 193.239.119.5, IPv6 2001:7f8:13::a500:5418:2, RS peer yes.

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