ixreport

Vayacom Limited: PeeringDB fix list

AS328986 · peeringdb.com/net/34261

PeeringDB

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

Make the changes on Vayacom Limited'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.

  1. Kenya LINX Mombasa Mombasa, Kenya · PeeringDB 4653
    ProblemPeeringDB hasThe export has
    Port speed differs10G5G
    • In the entry with IPv4 196.60.124.145: set Speed to 5000 (5G) (now 10000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Vayacom Limited has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Kenya KIXP-Mombasa Mombasa, Kenya · PeeringDB 2362Not on its IX-F export
    IPv4196.60.68.65
    IPv62001:43f8:c0:1::65
    Speed10000 Mbps (10G)

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