City network · New Zealand

Hamilton internet exchanges, data centers and carriers

PeeringDB's 2026-09-07 snapshot records 1 internet exchange and 5 colocation facilities in Hamilton, New Zealand. The largest exchange is HIX-NZ, with 0 participant entries.

Exchanges
1
Facilities
5
Snapshot
2026-09-07
Country
New Zealand (NZ)
Internet exchanges
1
Largest exchange
HIX-NZ (0 participants)
Exchange participant entries
none recorded
Colocation facilities
5
Facility network presences
66
Registry carriers peering here
none recorded
Snapshot
2026-09-07

The 2026-09-07 PeeringDB snapshot records 1 exchanges and 5 facilities in Hamilton, New Zealand. Their entries sum to 0 exchange participants and 66 facility network presences; the same network can appear more than once.

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.
Internet exchanges in Hamilton
ExchangeParticipantsRegistry carriers peering
HIX-NZHamilton Internet Exchange0none in the registry

Colocation facilities in Hamilton

Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which records reported presence rather than available capacity.
Colocation facilities in Hamilton
FacilityNetworks presentAddress
Datacom - Kapua Data Centre (Hamilton)2214 Simsey Place
Data Vault Hamilton Data Center1932 The Boulevard Te Rapa Park
Spark Hamilton Exchange18Caro St
Chorus Hamilton Exchange (HN)6Caro St Hamilton Central
Chorus Frankton Exchange (FJN)1103 Kent Street Frankton

What these records establish

This page groups the saved exchange and facility records for Hamilton. 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 Hamilton?
1 exchanges and 5 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 Hamilton 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.

  1. [1]https://www.peeringdb.com/
  2. [2]https://support.maxmind.com/knowledge-base/articles/maxmind-geolocation-accuracy
  3. [3]https://www.proxies.sx/carriers

These records describe where networks interconnect. A Hamilton IP address does not show that a device is in Hamilton: mobile carriers route traffic from wide areas through shared gateways, and geolocation databases estimate from registration data.