ixreport

RICTA: PeeringDB fix list

AS328014 · peeringdb.com/net/36544

PeeringDB

2 things to fix in RICTA's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on RICTA'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 RICTA's PeeringDB record. Add one entry per connection with these values.

  1. Kenya KIXP - Nairobi Nairobi, Kenya · PeeringDB 236From its IX-F export and website members list
    IPv4196.223.21.96
    IPv62001:43f8:60:1::96
    Speed1000 Mbps (1G)
    RS peerNo

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 KIXP - Nairobi Nairobi, Kenya · PeeringDB 236
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB196.223.21.96 is AS328015 Sombha Solutions Store196.223.21.96

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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