Massive Networks: PeeringDB fix list
AS21777 · peeringdb.com/net/7957
2 things to fix in Massive Networks's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on Massive Networks'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 Massive Networks's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Massive Networks has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204Not on its website members listIPv4 206.51.40.117 IPv6 2001:504:13:1::117 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/21777/: 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.