Durban · South Africa
PeeringDB records two internet exchanges in Durban, South Africa, with 238 participants between them. NAPAfrica IX Durban has 139 and DINX has 99. Three colocation facilities list 138 networks, most of them at Teraco DB1. An address that geolocates to Durban tells you what an operator registered, not where a device sits.
Internet exchanges in Durban
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 Durban | 139 | none in the registry |
DINX Durban Internet Exchange | 99 | 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 DB1 Durban, South Africa | 120 | Riverhorse Valley Riverhorse Cl, Newlands East |
| OADC, Umhlanga | 16 | East Coast House Umhlanga |
| OADC DUR1 - Durban | 2 | McGowan Place Umbogintwini, Amanzimtoti |
What a Durban IP address tells you
Durban's two exchanges are close in size. NAPAfrica IX Durban carries 139 participants and DINX carries 99, so neither one holds the city's peering on its own. Colocation is less even. Teraco DB1 lists 120 of the 138 networks recorded across the city, with OADC Umhlanga at 16 and OADC DUR1 at 2. No South African mobile operator appears in Durban's carrier list, so the registry does not record mobile network peering here either way.
An address that a database places in Durban may belong to a device elsewhere. An operator announces the block from a registry record, and that record shows the location the operator filed, which can be an office rather than the equipment. Mobile networks route handset traffic through a small set of gateways, so the address a phone presents reflects the gateway and not the tower it connects to. Geolocation providers read the operator's published location and repeat it.
Anyone checking a Durban address should look at the origin ASN on the prefix and the netname on the registry object that covers it. Those two fields say which network announces the address and how that network described itself, which is more than a city label carries. The 238 exchange participants and 138 facility networks recorded here are the pool any genuinely local route would come from.
Questions
Which internet exchanges are in Durban?
PeeringDB lists two. NAPAfrica IX Durban has 139 participants and DINX, the Durban Internet Exchange, has 99. Together they account for the 238 participants counted in the city, alongside three colocation facilities holding 138 networks.
Do South African mobile carriers peer in Durban?
Not according to this data. No South African mobile operator appears in Durban's carrier list, so the registry cannot say whether the country's mobile networks peer at either exchange. Reading the origin ASN on a specific prefix settles it for that address.
Does an IP that geolocates to Durban mean the device is there?
No. Geolocation databases report the location an operator published for the address block. That block can cover users across the operator's footprint, and mobile traffic leaves through gateways that need not be anywhere near 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