icolo.io: PeeringDB fix list
AS328162 · peeringdb.com/net/14510
4 things to fix in icolo.io's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on icolo.io'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 (1)
On the exchange's own member list, but not in icolo.io's PeeringDB record. Add one entry per connection with these values.
-
IPv4 196.60.124.24 IPv6 2001:43f8:1771::5:1e2:1 Speed 10000 Mbps (10G) 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 Port speed differs 10G 1G - In the entry with IPv4 196.223.21.184: set Speed to 1000 (1G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 196.60.114.6: set Speed to 10000 (10G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If icolo.io has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 196.60.68.62 IPv6 2001:43f8:c0:1::62 Speed 10000 Mbps (10G)
From ixreport.com/net/328162/: 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.