ixreport

Any2 Route Servers: PeeringDB fix list

AS32184 · peeringdb.com/net/14231

PeeringDB

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

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

  1. United States Any2Chicago Chicago, United States · PeeringDB 226Not on its website members list
    IPv4206.51.43.252
    IPv62001:504:13:4::252
    Speed10000 Mbps (10G)
    IPv4206.51.43.253
    IPv62001:504:13:4::253
    Speed10000 Mbps (10G)

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

  2. United States Any2Denver Denver, United States · PeeringDB 254Not on its website members list
    IPv4206.51.46.64
    IPv62605:6c00:303:303::64
    Speed10000 Mbps (10G)
    IPv4206.51.46.65
    IPv62605:6c00:303:303::65
    Speed10000 Mbps (10G)

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

  3. United States Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204Not on its website members list
    IPv4206.51.40.252
    IPv62001:504:13:1::252
    Speed10000 Mbps (10G)
    IPv4206.51.40.253
    IPv62001:504:13:1::253
    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/32184/: 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.