ixreport

Zero Distance: PeeringDB fix list

AS57406 · peeringdb.com/net/31127

PeeringDB

One thing to fix in Zero Distance's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Zero Distance's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Zero Distance has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.231.100
    IPv62001:7f8:4::e03e:1
    Speed100 Mbps (100M)

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