Johannesburg · South Africa
PeeringDB records five internet exchanges in Johannesburg, South Africa, with 798 peering participants counted across them. NAPAfrica IX Johannesburg has the most participants at 543, ahead of JINX at 206. Six colocation facilities list 458 networks between them. An address that geolocates to Johannesburg says where an operator registered the block, not where a device sits.
Internet exchanges in Johannesburg
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 Johannesburg | 543 | |
JINX Johannesburg Internet Exchange | 206 | |
NAPAfrica MAPS Johannesburg MAPS @ NAPAfrica Johannesburg | 26 | none in the registry |
BGP.Exchange - Johannesburg | 19 | none in the registry |
JINX Voice | 4 | 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 Johannesburg Campus, South Africa | 390 | 5 Brewery Street Isando |
| Teraco Johannesburg Bredell Campus | 22 | 1 Riverfields Boulevard Bredell |
| OADC - Parklands | 21 | 7 - 9 Keyes Drive Rosebank |
| OADC JNB1 - Johannesburg | 10 | 18 Electron Avenue Isando |
| Equinix JN1 - Johannesburg | 9 | 103 Brollo Road Tunney, Germiston |
| Reflex Solutions | 6 | 220 Jan Smuts Avenue Dunkeld |
What a Johannesburg IP address tells you
Johannesburg's peering weight sits in one exchange. NAPAfrica IX Johannesburg carries 543 participants, more than twice the 206 at JINX, and the other three exchanges account for 49 between them. Colocation is concentrated the same way. The Teraco Johannesburg Campus lists 390 networks, while the Bredell campus lists 22, OADC Parklands 21 and Equinix JN1 9. No South African mobile operator appears in the carrier list for this city, so the registry does not record whether the country's mobile networks peer at these exchanges.
An address that a database places in Johannesburg may not be a device in Johannesburg. Operators announce address blocks from a registry record, and that record carries whichever address the operator filed for the range, often a head office rather than the site the traffic comes from. Mobile networks compound this because handset traffic leaves through a small number of gateways, so a phone on the coast can present an address a database reads as Johannesburg. Geolocation providers follow the operator's published location and update when the operator does.
Someone checking an address here is better off reading the routing data. Look at the origin ASN on the specific prefix and the netname on the registry object, then set that against the 798 exchange participants and 458 facility networks Johannesburg records. A prefix announced by a fixed network inside the Teraco campus behaves differently from one announced by a mobile operator, even when both resolve to the same city string.
Questions
Which internet exchanges are in Johannesburg?
PeeringDB lists five. NAPAfrica IX Johannesburg has 543 participants, JINX has 206, NAPAfrica MAPS Johannesburg has 26, BGP.Exchange - Johannesburg has 19 and JINX Voice has 4. Together they make up the 798 participants counted in the city.
Do South African mobile carriers peer in Johannesburg?
The registry does not say. No South African mobile operator appears in the carrier list for this city, so the exchange records here neither confirm nor rule out peering by the country's mobile networks. Reading the origin ASN of a given prefix answers it for that address.
Does an IP that geolocates to Johannesburg mean the device is there?
No. Geolocation databases repeat the location an operator published for the address block. A block registered to a Johannesburg address can carry traffic from anywhere the operator's network reaches, and mobile traffic in particular leaves through gateways far from the handset.
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