Cloud Gateway: PeeringDB fix list
AS205098 · peeringdb.com/net/17892
2 things to fix in Cloud Gateway's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Cloud Gateway'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 (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 4G 5G - In the entry with IPv4 195.66.231.248: set Speed to 5000 (5G) (now 4000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4:2:0:3:212a:1 Port speed differs 1G 2G - In the entry with IPv4 195.66.244.14: set IPv6 to 2001:7f8:4:2:0:3:212a:1 (now empty); set Speed to 2000 (2G) (now 1000).
From ixreport.com/net/205098/: 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.