City network · New Zealand
Wellington internet exchanges, data centers and carriers
PeeringDB's 2026-09-07 snapshot records 2 internet exchanges and 12 colocation facilities in Wellington, New Zealand. The largest exchange is WLG-IX (Wellington NZ), with 24 participant entries.
- Exchanges
- 2
- Facilities
- 12
- Snapshot
- 2026-09-07
- Country
- New Zealand (NZ)
- Internet exchanges
- 2
- Largest exchange
- WLG-IX (Wellington NZ) (24 participants)
- Exchange participant entries
- 42
- Colocation facilities
- 12
- Facility network presences
- 81
- Registry carriers peering here
- none recorded
- Snapshot
- 2026-09-07
The 2026-09-07 PeeringDB snapshot records 2 exchanges and 12 facilities in Wellington, New Zealand. Their entries sum to 42 exchange participants and 81 facility network presences; the same network can appear more than once.
Internet exchanges in Wellington
| Exchange | Participants | Registry carriers peering |
|---|---|---|
| WLG-IX (Wellington NZ) | 24 | none in the registry |
| WIX-NZWellington Internet Exchange | 18 | none in the registry |
Colocation facilities in Wellington
| Facility | Networks present | Address |
|---|---|---|
| Spark Wellington Central (Featherston) | 22 | 70 Featherston St |
| Xtreme Networks - Wellington DC | 21 | The Thorndon Centre 191 Thorndon Quay |
| Chorus Wellington Exchange (WN) | 7 | Courtney Place Exchange 24-26 Cambridge Terrace |
| Chorus Courtenay Place Exchange (CPC) | 7 | 25 Cambridge Terrace Te Aro |
| Revera Trethem | 6 | Cnr Alexander Rd and George Daniels Dr Trentham |
| Citylink Classic House | 6 | 17 Murphy Street Thorndon |
| Datacom - Abel Data Centre (Wellington) | 5 | 84 Abel Smith St |
| Plan B Tawa | 3 | 210 Main Road Tawa |
| Data Vault Wellington Data Center | 2 | 160 Lambton Quay Wellington Central |
| Caduceus Datacentre | 1 | Level 3 154 Featherston Street |
| Localhost Wellington | 1 | 15 Murphy Street Thorndon |
| Chorus Johnsonville Exchange (JV) | 0 | 21 Johnsonville Road Johnsonville |
What these records establish
This page groups the saved exchange and facility records for Wellington. 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 Wellington?
- 2 exchanges and 12 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 Wellington 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.
These records describe where networks interconnect. A Wellington IP address does not show that a device is in Wellington: mobile carriers route traffic from wide areas through shared gateways, and geolocation databases estimate from registration data.