Ninja-IX Raleigh Route Servers: PeeringDB fix list
AS23064 · peeringdb.com/net/26047
One thing to fix in Ninja-IX Raleigh Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Ninja-IX Raleigh Route Servers'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 IPv4 address in PeeringDB, not in the export 206.80.232.5 206.80.232.6 206.80.232.5 IPv6 address in PeeringDB, not in the export 2001:504:67::5 2001:504:67::6 2001:504:67::5 Port speed differs 2 × 10G 10G - The entry with IPv4 206.80.232.6, IPv6 2001:504:67::6 isn't in the export: delete it if that connection is gone.
From ixreport.com/net/23064/: 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.