OCCAID: PeeringDB fix list

AS30071 · peeringdb.com/net/442

PeeringDB

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

Make the changes on OCCAID'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 OCCAID 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 Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204Not on its website members list
    IPv4–
    IPv62001:504:13:1::22
    Speed1000 Mbps (1G)

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

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