Tawala Networks Limited: PeeringDB fix list

AS329367 · peeringdb.com/net/37714

PeeringDB

3 things to fix in Tawala Networks Limited's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Tawala Networks Limited'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 (3)

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-Mombasa Mombasa, Kenya · PeeringDB 2362
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:c0:1::76
    • In the entry with IPv4 196.60.68.76: set IPv6 to 2001:43f8:c0:1::76 (now empty).
  2. Kenya LINX Mombasa Mombasa, Kenya · PeeringDB 4653
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:1771::5:697:1
    • In the entry with IPv4 196.60.124.37: set IPv6 to 2001:43f8:1771::5:697:1 (now empty).
  3. Kenya LINX Nairobi Nairobi, Kenya · PeeringDB 4231
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:16d0::5:697:1
    • In the entry with IPv4 196.60.114.70: set IPv6 to 2001:43f8:16d0::5:697:1 (now empty).

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