ixreport

Mymanga Networks: PeeringDB fix list

AS329029 · peeringdb.com/net/29528

PeeringDB

2 things to fix in Mymanga Networks's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Mymanga Networks'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 in PeeringDB, not in the export196.223.21.153 196.223.21.207none
    IPv6 address in PeeringDB, not in the export2001:43f8:60:1::153 2001:43f8:60:1::207none
    Port speed differs2 × 10G10G
    • The entry with IPv4 196.223.21.153, IPv6 2001:43f8:60:1::153 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 196.223.21.207, IPv6 2001:43f8:60:1::207 isn't in the export: delete it if that connection is gone.
  2. Kenya KIXP-Mombasa Mombasa, Kenya · PeeringDB 2362
    ProblemPeeringDB hasThe export has
    Port speed differs100G40G
    • In the entry with IPv4 196.60.68.53: set Speed to 40000 (40G) (now 100000).

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