AF-CIX Route Servers: PeeringDB fix list
AS37793 · peeringdb.com/net/31160
One thing to fix in AF-CIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on AF-CIX Route Servers'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 196.49.90.252 196.49.90.253 196.49.90.66 196.49.90.252 196.49.90.253 IPv6 address missing from PeeringDB 2001:43f8:1690::93a1:a:1 2001:43f8:1690::93a1:a:2 2001:43f8:1690::93a1:a:1 2001:43f8:1690::93a1:a:2 2001:43f8:1690::93a1:b:dead Port speed differs 2 × 10G 3 × 20G - In the entry with IPv4 196.49.90.252: set Speed to 20000 (20G) (now 10000).
- In the entry with IPv4 196.49.90.253: set Speed to 20000 (20G) (now 10000).
- Add an entry: IPv4 196.49.90.66, IPv6 2001:43f8:1690::93a1:b:dead, speed 20000 (20G), RS peer no.
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/37793/: 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.