Rackdog: PeeringDB fix list
AS398465 · peeringdb.com/net/23622
4 things to fix in Rackdog's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Rackdog'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 Rackdog's PeeringDB record. Add one entry per connection with these values.
-
CIX-NoVA Ashburn, Reston, Washington DC, United States · PeeringDB 4796From its IX-F export and website members listIPv4 149.112.69.39 IPv6 2001:504:40:69::1:39 Speed 400000 Mbps (400G) RS peer Yes
Correct these entries (3)
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 IPv6 address differs 2001:7f8:1:0:a500:39:8465:1 2001:7f8:1:0:a500:39:8465:2 Port speed differs 10G 9.9G - In the entry with IPv4 80.249.212.41: set IPv6 to 2001:7f8:1:0:a500:39:8465:2 (now 2001:7f8:1:0:a500:39:8465:1); set Speed to 9900 (9.9G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 20G 10G - In the entry with IPv4 195.66.227.122: set Speed to 10000 (10G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 100G 12.5G - In the entry with IPv4 185.0.21.63: set Speed to 12500 (12.5G) (now 100000).
From ixreport.com/net/398465/: 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.