Jamii Telecommunications: PeeringDB fix list
AS36866 · peeringdb.com/net/11047
One thing to fix in Jamii Telecommunications's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Jamii Telecommunications'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 missing from PeeringDB 196.223.21.11 196.223.21.11 196.223.21.165 IPv6 address missing from PeeringDB 2001:43f8:60:1::11 2001:43f8:60:1::11 2001:43f8:60:1::165 Port speed differs 40G 100G + 10G - In the entry with IPv4 196.223.21.11: set Speed to 100000 (100G) (now 40000).
- Add an entry: IPv4 196.223.21.165, IPv6 2001:43f8:60:1::165, speed 10000 (10G), RS peer no.
From ixreport.com/net/36866/: 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.