IX Reach: PeeringDB fix list
AS43531 · peeringdb.com/net/2927
5 things to fix in IX Reach's PeeringDB record, from what its exchanges publish: 3 to add, 2 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on IX Reach'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 (3)
On the exchange's own member list, but not in IX Reach's PeeringDB record. Add one entry per connection with these values.
-
IPv4 217.29.66.123 IPv6 2001:7f8:b:100:1d1:a5d0:4455:123 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 185.1.195.12 IPv6 2001:7f8:34::12 Speed Not published RS peer Not published -
IPv4 185.1.8.13 IPv6 2001:7f8:73::1167:0:1 Speed 1000 Mbps (1G) RS peer Yes
Correct these entries (2)
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 Address belongs to another network in PeeringDB 217.29.66.123 is AS4455 BSO 217.29.66.123 Address belongs to another network in PeeringDB 2001:7f8:b:100:1d1:a5d0:4455:123 is AS4455 BSO 2001:7f8:b:100:1d1:a5d0:4455:123 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 185.1.8.13 is AS4455 BSO 185.1.8.13 Address belongs to another network in PeeringDB 2001:7f8:73::1167:0:1 is AS4455 BSO 2001:7f8:73::1167:0:1 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/43531/: 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.