ixreport

Rasmilink Communication: PeeringDB fix list

AS37129 · peeringdb.com/net/24440

PeeringDB

2 things to fix in Rasmilink Communication's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 21:56 UTC.

Make the changes on Rasmilink Communication'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
    IPv6 address missing from PeeringDBnone2001:43f8:60:1::138
    Port speed differs20G10G
    • In the entry with IPv4 196.223.21.138: set IPv6 to 2001:43f8:60:1::138 (now empty); set Speed to 10000 (10G) (now 20000).
  2. Kenya KIXP-Mombasa Mombasa, Kenya · PeeringDB 2362
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export196.60.68.68none
    IPv6 address in PeeringDB, not in the export2001:43f8:c0:1::68none
    • The entry with IPv4 196.60.68.68, IPv6 2001:43f8:c0:1::68 isn't in the export: delete it if that connection is gone.

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