INETCOM: PeeringDB fix list
AS35598 · peeringdb.com/net/20759
2 things to fix in INETCOM's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on INETCOM'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 178.18.226.101 178.18.225.235 178.18.226.101 178.18.227.24 IPv6 address missing from PeeringDB 2a03:5f80:4::226:101 2a03:5f80:4::225:235 2a03:5f80:4::226:101 2a03:5f80:4::227:24 - Add an entry: IPv4 178.18.227.24, IPv6 2a03:5f80:4::227:24, speed 100000 (100G), RS peer yes.
- Add an entry: IPv4 178.18.225.235, IPv6 2a03:5f80:4::225:235, speed 100000 (100G), 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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If INETCOM has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.224.242 IPv6 2001:7f8:4::8b0e:1 Speed 20000 Mbps (20G)
From ixreport.com/net/35598/: 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.