Colt: PeeringDB fix list
AS8220 · peeringdb.com/net/91
6 things to fix in Colt's PeeringDB record, from what its exchanges publish: 2 to add, 4 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Colt'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 (2)
On the exchange's own member list, but not in Colt's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.69.119.104 IPv6 2001:7f8:d:fb::104 Speed 50000000 Mbps (50T) RS peer Yes -
IPv4 195.245.240.104 IPv6 2001:7f8:d:fc::104 Speed 50000000 Mbps (50T) RS peer Yes
Correct these entries (4)
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 100G 50T - In the entry with IPv4 212.237.192.104: set Speed to 50000000 (50T) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 50T - In the entry with IPv4 212.237.193.104: set Speed to 50000000 (50T) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 50T - In the entry with IPv4 194.68.128.104: set Speed to 50000000 (50T) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 50T - In the entry with IPv4 194.68.123.104: set Speed to 50000000 (50T) (now 100000).
From ixreport.com/net/8220/: 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.