ixreport

DO-IX: operator report

Dortmund, Germany · PeeringDB 762 · ixreport.com/ix/762/report/

Download CSV

Members of DO-IX that PeeringDB has wrong, from its IX-F export (12 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 4 networks to follow up.

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 (3)

These networks could add DO-IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS8881 1&1 Versatel Deutschland PeeringDBIX-F 185.1.18.60
2001:67c:2b9c::100:60
100G		 No public contact
AS36040 Google LLC AS36040 PeeringDBIX-F 185.1.18.28
2001:67c:2b9c::100:28
100G		 No public contact
AS39138 rrbone PeeringDBIX-F 185.1.18.42
2001:67c:2b9c::100:42
100G		 No public contact

Addresses or port speeds that differ (1)

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

NetworkProblemPeeringDB hasYour export hasContact
AS200117 DO-IX Route Servers PeeringDB Port speed differs2 × 1G1G No public contact

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.