InterCloud: PeeringDB fix list
AS197981 · peeringdb.com/net/4345
2 things to fix in InterCloud'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 InterCloud'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 in PeeringDB, not in the export 195.66.225.164 195.66.231.111 195.66.225.164 IPv6 address in PeeringDB, not in the export 2001:7f8:4::3:55d:1 2001:7f8:4::3:55d:2 2001:7f8:4::3:55d:1 Port speed differs 2 × 10G 10G - The entry with IPv4 195.66.231.111, IPv6 2001:7f8:4::3:55d:2 isn't in the export: delete it if that connection is gone.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If InterCloud has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 101.203.90.114 IPv6 2001:de8:c::19:7981: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/197981/: 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.