City network · South Africa

Cape Town internet exchanges, data centers and carriers

PeeringDB's 2026-09-07 snapshot records 4 internet exchanges and 6 colocation facilities in Cape Town, South Africa. The largest exchange is NAPAfrica IX Cape Town, with 280 participant entries. 2 mobile carriers from our registry peer here.

Exchanges
4
Facilities
6
Snapshot
2026-09-07
Country
South Africa (ZA)
Internet exchanges
4
Largest exchange
NAPAfrica IX Cape Town (280 participants)
Exchange participant entries
406
Colocation facilities
6
Facility network presences
264
Registry carriers peering here
2
Snapshot
2026-09-07

The 2026-09-07 PeeringDB snapshot records 4 exchanges and 6 facilities in Cape Town, South Africa. Their entries sum to 406 exchange participants and 264 facility network presences; the same network can appear more than once.

Internet exchanges in Cape Town

An exchange is a shared switch where networks hand traffic to each other directly. Participant counts come from PeeringDB, where each network maintains its own record.
Internet exchanges in Cape Town
ExchangeParticipantsRegistry carriers peering
NAPAfrica IX Cape Town280Swisscom AS3303
CINXCape Town Internet Exchange121China Telecom AS4134
NAPAfrica MAPS Cape Town5none in the registry
CINX Voice0none in the registry

Colocation facilities in Cape Town

Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which records reported presence rather than available capacity.
Colocation facilities in Cape Town
FacilityNetworks presentAddress
Teraco CT1 Cape Town, South Africa195Great Westerford Building, 240 Main Road
Teraco CT2 Cape Town, South Africa25Brackengate 2, 57 Tiber Rd Brackenfell
Africa Data Centres, Cape Town CPT1, South Africa20108 De Waal Road Elfindale, Diep River
OADC CPT3 - Cape Town127th Floor, The Terraces
OADC CPT1 - Cape Town11Burg House Belmont Road, Rondebosch
OADC CPT2 - Brackenfell1Viro Crescent Stikland Industrial

What these records establish

This page groups the saved exchange and facility records for Cape Town. A sum of participant or facility counts is not a count of unique networks, traffic volume, available capacity or service coverage.

PeeringDB is user-maintained. Its records describe reported interconnection infrastructure; they do not trace a particular request or locate a subscriber. A missing record in this snapshot is not proof that an operator has no presence or private connection in the area.

An IP geolocation result is a separate estimate. MaxMind documents accuracy limits and explains that its location data cannot identify a specific household, person or street address. This registry does not perform a geolocation lookup or measure where an individual device is located.

Questions

How many exchanges and facilities are recorded in Cape Town?
4 exchanges and 6 facilities appear in the 2026-09-07 snapshot. The tables show the saved records and link to the publisher for current details.
Are the totals unique networks?
No. Participant entries are summed across exchanges and network presences across facilities. A network listed at several locations contributes to several entries.
Does a Cape Town IP label prove that a device is there?
No. These infrastructure records do not establish a device location. Consult the geolocation provider’s accuracy information and the specific network record for the claim you are evaluating.

Sources

PeeringDB supplies the exchanges, participant counts, facilities and network presence (snapshot 2026-09-07); MaxMind documents the limits of IP geolocation; the PROXIES.SX carrier registry supplies the operator ASNs used to match peering participants.

  1. [1]https://www.peeringdb.com/
  2. [2]https://support.maxmind.com/knowledge-base/articles/maxmind-geolocation-accuracy
  3. [3]https://www.proxies.sx/carriers

These records describe where networks interconnect. A Cape Town IP address does not show that a device is in Cape Town: mobile carriers route traffic from wide areas through shared gateways, and geolocation databases estimate from registration data.