CC INTERNET: PeeringDB fix list
AS202921 · peeringdb.com/net/11443
2 things to fix in CC INTERNET's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on CC INTERNET'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 CC INTERNET's PeeringDB record. Add one entry per connection with these values.
-
IPv4 91.210.16.237 IPv6 2001:7f8:14::72:1 Speed 25000 Mbps (25G) 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.
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 185.0.20.60 185.0.20.60 185.0.21.60 IPv6 address missing from PeeringDB none 2001:7f8:7f::60 2001:7f8:7f::c:60 Port speed differs 160G 20G - In the entry with IPv4 185.0.20.60: set IPv6 to 2001:7f8:7f::60 (now empty); set Speed to 20000 (20G) (now 160000).
- Add an entry: IPv4 185.0.21.60, IPv6 2001:7f8:7f::c:60, speed 20000 (20G), RS peer yes.
From ixreport.com/net/202921/: 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.