RouteFEED: PeeringDB fix list

AS45686 · peeringdb.com/net/10726

PeeringDB

One thing to fix in RouteFEED's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on RouteFEED'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 RouteFEED has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan JPNAP Tokyo Tokyo, Japan · PeeringDB 95Not on its website members list
    IPv4210.173.176.211
    IPv62001:7fa:7:1:0:4:5686:1
    Speed10000 Mbps (10G)
    IPv4210.173.176.212
    IPv62001:7fa:7:1:0:4:5686:2
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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