KIXP - Nairobi Route Servers: PeeringDB fix list
AS37704 · peeringdb.com/net/11937
One thing to fix in KIXP - Nairobi Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on KIXP - Nairobi 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 in PeeringDB, not in the export 196.223.21.65 196.223.21.66 none IPv6 address in PeeringDB, not in the export 2001:43f8:60:1::65 2001:43f8:60:1::66 none - The entry with IPv4 196.223.21.65, IPv6 2001:43f8:60:1::65 isn't in the export: delete it if that connection is gone.
- The entry with IPv4 196.223.21.66, IPv6 2001:43f8:60:1::66 isn't in the export: delete it if that connection is gone.
From ixreport.com/net/37704/: 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.