Cape Town · South Africa
PeeringDB records four internet exchanges in Cape Town, South Africa, with 406 participants counted across them. NAPAfrica IX Cape Town has the most at 280, ahead of CINX at 121. Six colocation facilities list 264 networks. An address that geolocates to Cape Town shows where an operator registered the block rather than where a device is.
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.
| Exchange | Participants | Registry carriers peering |
|---|---|---|
NAPAfrica IX Cape Town | 280 | |
CINX Cape Town Internet Exchange | 121 | |
NAPAfrica MAPS Cape Town | 5 | none in the registry |
CINX Voice | 0 | none in the registry |
Exchange records: PeeringDB.
Colocation facilities
Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which shows where capacity in the city sits.
| Facility | Networks present | Address |
|---|---|---|
| Teraco CT1 Cape Town, South Africa | 195 | Great Westerford Building, 240 Main Road |
| Teraco CT2 Cape Town, South Africa | 25 | Brackengate 2, 57 Tiber Rd Brackenfell |
| Africa Data Centres, Cape Town CPT1, South Africa | 20 | 108 De Waal Road Elfindale, Diep River |
| OADC CPT3 - Cape Town | 12 | 7th Floor, The Terraces |
| OADC CPT1 - Cape Town | 11 | Burg House Belmont Road, Rondebosch |
| OADC CPT2 - Brackenfell | 1 | Viro Crescent Stikland Industrial |
What a Cape Town IP address tells you
Cape Town's peering sits in two exchanges of unequal size. NAPAfrica IX Cape Town holds 280 participants and CINX holds 121, while NAPAfrica MAPS Cape Town records 5 and CINX Voice none. Colocation follows the same split. Teraco CT1 lists 195 networks against 25 at Teraco CT2, 20 at Africa Data Centres Cape Town CPT1 and 12 at OADC CPT3. No South African mobile operator appears in the city's carrier list, so the registry says nothing about mobile network peering here.
An address that a database places in Cape Town need not be a device in Cape Town. Operators announce prefixes from a registry object whose address is whatever they filed, and one filing can cover a network reaching the whole country. Mobile traffic narrows things further, leaving through a handful of gateways, so a handset in another province can present an address that databases read as Cape Town. Those databases follow the operator's published location and change only when the operator changes it.
The useful check is the prefix itself. Read the origin ASN and the netname on the registry object covering the address, then set that against the 406 exchange participants and 264 facility networks Cape Town records. A prefix announced inside those facilities by a fixed network is a different thing from one announced by a mobile operator, however the city label reads.
Questions
Which internet exchanges are in Cape Town?
PeeringDB lists four. NAPAfrica IX Cape Town has 280 participants, CINX has 121, NAPAfrica MAPS Cape Town has 5 and CINX Voice has none recorded. Between them they account for the 406 exchange participants counted in the city.
Do South African mobile carriers peer in Cape Town?
The registry does not answer that. No South African mobile operator appears in the carrier list for Cape Town, so the exchange entries neither show nor exclude mobile peering. The origin ASN on a specific prefix is the direct way to check an address.
Does an IP that geolocates to Cape Town mean the device is there?
No. The location comes from what an operator published for the address block, not from the device. A Cape Town registration can cover traffic from across the operator's network, and mobile connections reach the internet through gateways that may sit in another city.
Sources
- PeeringDB - exchanges, participant counts, facilities and network presence, snapshot 2026-09-07
- PROXIES.SX carrier and ASN registry - operator ASNs used to match peering participants