ixreport

RegPEX: operator report

Ankara, Türkiye · PeeringDB 4986 · ixreport.com/ix/4986/report/

Download CSV

Members of RegPEX that PeeringDB has wrong, from its IX-F export (13 networks, read 2026-10-08 22:05 UTC) and its website members list (13 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 4 networks to follow up; 2 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 (3)

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

NetworkOn yourAddressesContact
AS13335 Cloudflare PeeringDBIX-F and website 95.133.136.30
2001:7f8:171::1e
10G
Policy: email address (needs JavaScript) +16503198930email address (needs JavaScript)
AS60847 AUTO-1 PeeringDBIX-F and website 95.133.136.29
2001:7f8:171::1d
10G
No public contact
AS208594 Netbone Telekomunikasyon AS208594 PeeringDBIX-F and website 95.133.136.32
2001:7f8:171::20
10G
No public contact

Addresses or port speeds that differ (1)

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

NetworkProblemPeeringDB hasYour export hasContact
AS200010 Olfe Veri Merkezi - İzmir PeeringDB IPv6 address missing from PeeringDBnone2001:7f8:171::1a NOC: email address (needs JavaScript) +908503046527
Port speed differs20G10G

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.