Defaultroute: PeeringDB fix list

AS61081 · peeringdb.com/net/13323

PeeringDB

3 things to fix in Defaultroute's PeeringDB record, from what its exchanges publish: 3 to check. As of 2026-10-08 21:35 UTC.

Make the changes on Defaultroute'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 (3)

In PeeringDB, but on none of the exchange's own lists. If Defaultroute 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.226.131
    IPv62001:7f8:4::ee99:1
    Speed10000 Mbps (10G)
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.238.131
    IPv62001:7f8:4:1::ee99:1
    Speed10000 Mbps (10G)
  3. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members list
    IPv4195.66.244.94
    IPv62001:7f8:4:2::ee99:1
    Speed1000 Mbps (1G)

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