ixreport

Web4Africa: PeeringDB fix list

AS327813 · peeringdb.com/net/7461

PeeringDB

2 things to fix in Web4Africa'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 Web4Africa'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 Web4Africa's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:d0::5:85:1
    SpeedNot published
    RS peerYes

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. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:43f8:bb1::82none
    • In the entry with IPv4 196.216.148.82: set IPv6 to (empty) (now 2001:43f8:bb1::82).

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