Packetsurge: PeeringDB fix list
AS22147 · peeringdb.com/net/5548
One thing to fix in Packetsurge's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.
Make the changes on Packetsurge's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Packetsurge's PeeringDB record. Add one entry per connection with these values.
-
Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204From its website members listIPv4 206.51.40.63 IPv6 2001:504:13:1::63 Speed Not published RS peer Not published
From ixreport.com/net/22147/: 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.