ACIX Route Servers: PeeringDB fix list

AS37799 · peeringdb.com/net/29916

PeeringDB

One thing to fix in ACIX 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 ACIX 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.

  1. DR Congo ACIX Kinshasa, DR Congo · PeeringDB 4122
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.60.92.252 196.60.92.253196.60.92.66 196.60.92.252 196.60.92.253
    IPv6 address missing from PeeringDB2001:43ff:6000::93a7:a:1 2001:43ff:6000::93a7:a:22001:43ff:6000::93a7:a:1 2001:43ff:6000::93a7:a:2 2001:43ff:6000::93a7:b:dead
    Port speed differs2 × 10G3 × 20G
    • In the entry with IPv4 196.60.92.252: set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 196.60.92.253: set Speed to 20000 (20G) (now 10000).
    • Add an entry: IPv4 196.60.92.66, IPv6 2001:43ff:6000::93a7:b:dead, speed 20000 (20G), RS peer no.

From ixreport.com/net/37799/: 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.