Rackspace: PeeringDB fix list
AS12200 · peeringdb.com/net/22
3 things to fix in Rackspace's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Rackspace'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 Rackspace's PeeringDB record. Add one entry per connection with these values.
-
IPv4 149.112.27.36 IPv6 2001:504:116::2fa8:0:2 Speed 200000 Mbps (200G) RS peer Yes
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 missing from PeeringDB 206.53.202.5 206.53.202.5 206.53.202.121 IPv6 address missing from PeeringDB 2001:504:61::2fa8:0:1 2001:504:61::2fa8:0:1 2001:504:61::2fa8:0:2 Port speed differs 10G 200G + 10G - Add an entry: IPv4 206.53.202.121, IPv6 2001:504:61::2fa8:0:2, speed 200000 (200G), RS peer yes.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Rackspace has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 198.32.160.111 IPv6 2001:504:1::a501:4492: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/12200/: 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.