Copaco Cloud: PeeringDB fix list
AS38983 · peeringdb.com/net/26393
One thing to fix in Copaco Cloud's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Copaco Cloud'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 80.249.214.188 80.249.211.203 80.249.214.188 IPv6 address missing from PeeringDB 2001:7f8:1::a503:8983:1 2001:7f8:1::a503:8983:1 2001:7f8:1::a503:8983:2 Port speed differs 10G 20G + 10G - Add an entry: IPv4 80.249.211.203, IPv6 2001:7f8:1::a503:8983:2, speed 20000 (20G), 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.
From ixreport.com/net/38983/: 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.