InterArena: PeeringDB fix list
AS198906 · peeringdb.com/net/12162
2 things to fix in InterArena's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 21:35 UTC.
Make the changes on InterArena'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 (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 IPv4 address missing from PeeringDB 178.216.41.144 178.216.42.114 178.216.40.17 178.216.41.144 178.216.42.114 IPv6 address missing from PeeringDB none 2001:7f8:5b::17 2001:7f8:5b::350 2001:7f8:5b::683 Port speed differs 2 × 10G 3 × 10G - In the entry with IPv4 178.216.41.144: set IPv6 to 2001:7f8:5b::350 (now empty).
- In the entry with IPv4 178.216.42.114: set IPv6 to 2001:7f8:5b::683 (now empty).
- Add an entry: IPv4 178.216.40.17, IPv6 2001:7f8:5b::17, 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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:678:3ac::174 2001:678:3ac::611 Port speed differs 2 × 10G 20G + 10G - In the entry with IPv4 89.46.144.174: set IPv6 to 2001:678:3ac::174 (now empty).
- In the entry with IPv4 89.46.145.6: set IPv6 to 2001:678:3ac::611 (now empty); set Speed to 20000 (20G) (now 10000).
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/198906/: 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.