ixreport

Simba Fiber Africa Limited: PeeringDB fix list

AS328727 · peeringdb.com/net/29080

PeeringDB

3 things to fix in Simba Fiber Africa Limited's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Simba Fiber Africa Limited's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Simba Fiber Africa Limited's PeeringDB record. Add one entry per connection with these values.

  1. Kenya LINX Nairobi Nairobi, Kenya · PeeringDB 4231From its IX-F export and website members list
    IPv4196.60.114.67
    IPv62001:43f8:16d0::5:417:1
    Speed4000 Mbps (4G)
    RS peerYes

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
    IPv6 address missing from PeeringDBnone2001:43f8:60:1::98
    • In the entry with IPv4 196.223.21.98: set IPv6 to 2001:43f8:60:1::98 (now empty).
  2. Uganda UIXP Kampala, Uganda · PeeringDB 422
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:130::52
    • In the entry with IPv4 196.223.25.52: set IPv6 to 2001:43f8:130::52 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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