Infinity Connect: PeeringDB fix list
AS329058 · peeringdb.com/net/29914
One thing to fix in Infinity Connect's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Infinity Connect'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 missing from PeeringDB 196.60.10.227 196.60.9.130 196.60.10.227 IPv6 address missing from PeeringDB 2001:43f8:6d0::10:227 2001:43f8:6d0::9:130 2001:43f8:6d0::10:227 Port speed differs 10G 2 × 10G - Add an entry: IPv4 196.60.9.130, IPv6 2001:43f8:6d0::9:130, speed 10000 (10G), RS peer yes.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/329058/: 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.