ixreport

Web4Africa

AS327813 · VIDOLU Group

6Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
6Using the route servers
2To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with Web4Africa? · Where should Web4Africa peer next? · Compare Web4Africa with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Web4Africa's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 18:41 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).

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where Web4Africa's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 23G, at the 5 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::5:85:1 Yes Not in PeeringDB
Ghana Accra Internet Exchange LBG Accra, Ghana 196.60.12.15 2001:7f8:b6:5:0:5:85:1 1G Yes Both
Nigeria IXPN Lagos Lagos, Nigeria 196.216.148.82 2001:43f8:bb1::82 1G 5 routes Both IPv6 not in export
Kenya KIXP - Nairobi Nairobi, Kenya 196.223.21.209 2001:43f8:60:1::209 1G 2 routes Both
South Africa NAPAfrica IX Cape Town Cape Town, South Africa 196.60.71.153 2001:43f8:6d1::71:153 10G Yes Both
South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa 196.60.8.176 2001:43f8:6d0::176 10G Yes Both

Exchanges in its buildings that it isn't on (8)

These exchanges have a switch in a facility where Web4Africa lists itself in PeeringDB, but don't have Web4Africa as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (5)

The buildings Web4Africa lists in PeeringDB, and how many of the exchanges in each it's on.