Kaldera: PeeringDB fix list
AS37722 · peeringdb.com/net/20651
3 things to fix in Kaldera's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Kaldera'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 10G 1G - In the entry with IPv4 196.60.97.31: set Speed to 1000 (1G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 196.223.0.13 196.223.0.10 196.223.0.13 IPv6 address missing from PeeringDB 2001:43f8:270:d0d0::13 2001:43f8:270:d0d0::10 2001:43f8:270:d0d0::13 Port speed differs 10G 10G + 1G - In the entry with IPv4 196.223.0.13: set Speed to 1000 (1G) (now 10000).
- Add an entry: IPv4 196.223.0.10, IPv6 2001:43f8:270:d0d0::10, speed 10000 (10G), 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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Kaldera has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.224.57 IPv6 2001:7f8:4::935a:1 Speed 1000 Mbps (1G)
From ixreport.com/net/37722/: 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.