MTN Business Kenya: PeeringDB fix list

AS9129 · peeringdb.com/net/16456

PeeringDB

2 things to fix in MTN Business Kenya's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on MTN Business Kenya'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.

  1. Kenya KIXP - Nairobi Nairobi, Kenya · PeeringDB 236
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB196.223.21.212196.223.21.171 196.223.21.212
    IPv6 address missing from PeeringDB2001:43f8:60:1::122001:43f8:60:1::12 2001:43f8:60:1::171
    Port speed differs1G10G + 1G
    • Add an entry: IPv4 196.223.21.171, IPv6 2001:43f8:60:1::171, speed 10000 (10G), RS peer yes.
  2. Kenya KIXP-Mombasa Mombasa, Kenya · PeeringDB 2362
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:43f8:c0:1::252001:43f8:c0:1::26
    • In the entry with IPv4 196.60.68.25: set IPv6 to 2001:43f8:c0:1::26 (now 2001:43f8:c0:1::25).

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