ixreport

NL-ix 2: operator report

Amsterdam, Netherlands · PeeringDB 2569 · ixreport.com/ix/2569/report/

Download CSV

Members of NL-ix 2 that PeeringDB has wrong, from its IX-F export (19 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 6 networks to follow up; 1 with a public PeeringDB contact.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (6)

These networks could add NL-ix 2 to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS6830 Liberty Global PeeringDBIX-F 185.1.122.18
2001:7f8:cd::a500:6830:1
Policy: email address (needs JavaScript)
AS8211 Cooperatieve Rabobank U.A.IX-F 185.1.122.17
2001:7f8:cd::a500:8211:2
No PeeringDB record
AS42517 Schiphol Communication TechnologyIX-F 185.1.122.32
2001:7f8:cd::a504:2517:1
No PeeringDB record
AS46489 Amazon IVS PeeringDBIX-F 185.1.122.19
2001:7f8:cd::a504:6489:1
No public contact
AS206426 Conclusion Enablement B.V.IX-F 185.1.122.151
2001:7f8:cd::a520:6426:1
No PeeringDB record
AS213065 UWV PeeringDBIX-F 185.1.122.31
2001:7f8:cd::a521:3065:1
No public contact

Addresses or port speeds that differ (0)

PeeringDB against your IX-F export, for the 13 networks in both. Either the network's PeeringDB record or the export is out of date.

None: every network's addresses and port speed match.

In PeeringDB, not on your lists (0)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

None.