Interpreting traffic from New Zealand
New Zealand's distance from major hosting regions means NZ users are often served from Australian or other nearby CDN edges, so edge-PoP geography and user country can diverge. This page explains how to read an 'NZ' country value as a coarse edge estimate.
Distance and CDN PoP geography
New Zealand sits far from most major cloud regions, so content is often delivered from Australian or other nearby CDN edges. If you read the serving PoP's location rather than the user-network country, you may misattribute NZ users to Australia.
Use the user-network country value for the NZ audience, and treat the CDN PoP location as a delivery detail, not a geography signal.
Reading NZ as a coarse estimate
Even with the correct user-network country, the edge resolves to New Zealand at the country level, not to a city or region. Submarine-cable routing and regional peering can also blur edges with Australia.
Use NZ for country-level trends, keep it distinct from AU, and avoid claiming sub-country precision.
- NZ often served from Australian CDN edges
- PoP location is not the user's country
- Country resolves at the edge; region detail is coarse
How it appears in analytics and logs
An 'NZ' country value should reflect where the user's network resolved, but CDN delivery for NZ frequently uses Australian or other regional edges, so do not confuse the serving PoP with the user country.
Diagnostic use case
Read a New Zealand country segment for coarse trends while remembering that NZ users may be served by Australian CDN edges, so PoP location is not the user's country.
What WebmasterID can help detect
WebmasterID records a coarse New Zealand country signal where the edge provides one, and keeps the user-country estimate distinct from the CDN PoP that served the request.
Common mistakes
- Misattributing NZ users to Australia from the serving PoP.
- Reading CDN-edge country as user country for NZ delivery.
- Claiming city or region precision from the NZ estimate.
Privacy and accuracy notes
WebmasterID treats a New Zealand country signal as a coarse, privacy-safe estimate derived at the edge — never an exact location and never from raw client IPs stored in your analytics.
Related pages
- CDN edge country vs user country: why they differ
Many stacks derive a visitor's country from a CDN or edge header. That header reflects the network path and the edge's best estimate — not a verified user location. This page explains how edge geo headers are produced, why edge country and user country can diverge, and how to present country data honestly.
- Interpreting traffic from Australia
Australia sits many hours ahead of Europe and the Americas, so its traffic peaks land at unusual times in your reports, and its high mobile share softens the country signal. This page explains how to read an 'AU' value as a coarse estimate and why timezone offset matters when interpreting when Australian traffic arrives.
- Privacy-first analytics
Coarse, privacy-safe country signals without raw-IP lookups.
Sources and verification notes
- MDN — HTTP headersEdge geo distinguishes the serving PoP from the user's network country.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.