ixreport

Simba Fiber Africa Limited

AS328727 · Simba Tv/Fiber

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
3Using the route servers
3To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Simba Fiber Africa Limited? · Where should Simba Fiber Africa Limited peer next? · Compare Simba Fiber Africa Limited with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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-11-19 18:41 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.

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Simba Fiber Africa Limited's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 24G across 3 exchanges.

Kenya KIXP - Nairobi Nairobi, Kenya 196.223.21.98 10G 20 routes Both IPv6 not in PeeringDB
Kenya LINX Nairobi Nairobi, Kenya 196.60.114.67 2001:43f8:16d0::5:417:1 4G 10 routes Not in PeeringDB
Uganda UIXP Kampala, Uganda 196.223.25.52 10G 12 routes Both IPv6 not in PeeringDB
Facilities (1)

The buildings Simba Fiber Africa Limited lists in PeeringDB, and how many of the exchanges in each it's on.

Kenya Africa Data Centres, Nairobi NBO1, KenyaNairobi 2 of 2