Psychz Networks: PeeringDB fix list
AS40676 · peeringdb.com/net/6747
3 things to fix in Psychz Networks's PeeringDB record, from what its exchanges publish: 1 to add, 2 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Psychz 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 Psychz Networks'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.33 IPv6 2001:504:13:1::33 Speed Not published RS peer Not published
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If Psychz Networks has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members list
IPv4 206.72.211.46 IPv6 2001:504:13::211:46 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 218.100.7.69 IPv6 2001:de8:c::4:676:1 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/40676/: 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.