Globalreach: PeeringDB fix list

AS17895 · peeringdb.com/net/2290

PeeringDB

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

Make the changes on Globalreach'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 Globalreach 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 Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members list
    IPv4206.72.210.71
    IPv6–
    Speed100 Mbps (100M)

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

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