Hamilton · New Zealand
PeeringDB lists one internet exchange in Hamilton, HIX-NZ, and records no participants on it, so what the registry documents for the city sits in five colocation facilities holding 66 networks. Datacom - Kapua Data Centre (Hamilton) reports the most, 22. An address geolocating to Hamilton reflects an operator's registration, not a device's position.
Internet exchanges in Hamilton
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 |
|---|---|---|
HIX-NZ Hamilton Internet Exchange | 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 |
|---|---|---|
| Datacom - Kapua Data Centre (Hamilton) | 22 | 14 Simsey Place |
| Data Vault Hamilton Data Center | 19 | 32 The Boulevard Te Rapa Park |
| Spark Hamilton Exchange | 18 | Caro St |
| Chorus Hamilton Exchange (HN) | 6 | Caro St Hamilton Central |
| Chorus Frankton Exchange (FJN) | 1 | 103 Kent Street Frankton |
What a Hamilton IP address tells you
HIX-NZ, the Hamilton Internet Exchange, is the only exchange PeeringDB lists in the city, and it records no participants at all. What the registry documents for Hamilton sits in colocation instead, 66 networks across five facilities. Datacom - Kapua Data Centre (Hamilton) reports 22, Data Vault Hamilton Data Center 19 and Spark Hamilton Exchange 18, which is 59 of the 66 between those three buildings. Chorus Hamilton Exchange adds six and Chorus Frankton Exchange one. No carrier ASN appears anywhere in the city's entry, and the carrier data behind this page names no New Zealand mobile operator.
With no participants at HIX-NZ, an address that a database places in Hamilton says even less about a device's position than usual. An operator announces the block from a registry record holding one address for the whole allocation, and mobile traffic leaves through gateways that sit wherever the operator put them. Geolocation providers repeat the operator's published location, so a connection from anywhere in New Zealand can come back as Hamilton without ever entering one of the five facilities on record.
The origin ASN and the netname on the specific prefix are worth more than the city field to anyone checking an address. The ASN identifies the network that announced the range and the netname shows how it describes that range, including whether it carries mobile subscribers. Neither says the traffic touched Hamilton. The 66 networks across five buildings show where the registry documents presence in the city, and an exchange with no participants shows there is no local peering point on record.
Questions
Which internet exchanges are in Hamilton?
PeeringDB lists one, HIX-NZ, the Hamilton Internet Exchange, and records no participants on it. No other exchange appears for the city, so the registry documents no active local peering point, only the five colocation facilities and their 66 networks.
Do New Zealand mobile carriers peer in Hamilton?
Nothing in the record shows that. HIX-NZ has no participants and no carrier ASN attached, and the carrier data behind this page names no New Zealand mobile operator. Any peering those networks do is recorded somewhere other than Hamilton.
Does an IP that geolocates to Hamilton mean the device is there?
No. The city label follows the registration of the address block and the location the operator publishes for it. A device elsewhere in New Zealand can use an address that every geolocation database reports as Hamilton.
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