Nodes Direct Holdings: PeeringDB fix list
AS19531 · peeringdb.com/net/3891
2 things to fix in Nodes Direct Holdings's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Nodes Direct Holdings's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 10G 2 × 10G
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Nodes Direct Holdings 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.127 IPv6 2001:504:13:1::127 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/19531/: 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.