Geo signals and CDN PoP selection
A CDN chooses which point of presence (PoP) serves a request based on network proximity and routing — typically via anycast and DNS — not on the visitor's political country. The serving PoP can be in a neighbouring country, which decouples 'where it was served' from 'where the visitor is'. This page explains how PoP selection works, why it complicates geo reading, and how to keep interpretation coarse and privacy-safe.
How a CDN picks a point of presence
CDNs steer each request to a nearby PoP using techniques like anycast routing and geo-aware DNS. 'Nearby' means network-topologically close — fewest hops, best peering, lowest latency — which usually but not always tracks physical distance.
Because routing follows the network, a visitor can be served by a PoP in a neighbouring country, or a country whose network peering is better than their own. The PoP is chosen for performance, not to match a political boundary.
Why PoP location is not audience geo
If you read the serving PoP's country as the visitor's country, you will misattribute traffic, especially near borders and on networks that peer through a hub elsewhere. The PoP answers 'which edge served this', not 'where is the person'.
Keep the two signals separate: use the visitor's coarse country estimate for audience reporting and the PoP for infrastructure and performance analysis. Both are approximate; neither is an exact location.
- PoP selection follows network proximity (anycast/DNS), not borders
- A visitor may be served by a PoP in a different country
- Read audience geo from the visitor estimate, not the serving PoP
How it appears in analytics and logs
The PoP that served a request reflects network topology and routing, not the visitor's political country. A visitor near a border, or on a network that peers elsewhere, may be served by a PoP in a different country, so PoP location is an infrastructure fact, not an audience-geo fact.
Diagnostic use case
Understand why the CDN PoP that served a request is not a reliable signal of the visitor's country, so you read edge audience geo from the visitor estimate rather than from the serving location.
What WebmasterID can help detect
WebmasterID separates bots from humans and records coarse country signals server-side, so you can distinguish the serving PoP (an infrastructure detail) from the visitor's coarse country estimate when reading edge geo.
Common mistakes
- Reading the serving PoP's country as the visitor's country.
- Assuming PoP proximity always matches physical distance.
- Mixing infrastructure PoP geo into audience country reporting.
Privacy and accuracy notes
PoP selection is about routing efficiency and uses coarse network proximity, not exact visitor location. WebmasterID keeps any visitor country signal coarse and privacy-safe, never deriving exact location from PoP choice or raw IPs.
Related pages
- Anycast CDN routing and geo
Anycast CDNs route a request to a nearby edge node by network topology, which is not the same as the user's country. This page explains how anycast routing works, why the serving edge node is not a location signal, and how routing-path effects can influence apparent geo.
- 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.
- Data-centre region vs audience country
Countries that host major cloud regions — such as the US, Germany, Ireland, Singapore, and others — over-represent machine traffic because servers, crawlers, and CDNs live there. This page explains why data-centre geography distorts country shares and how to read audience country once hosted infrastructure is separated.
- Website observability
See edge and request signals separated from human analytics.
Sources and verification notes
- RFC 4786 — Operation of Anycast ServicesAnycast routes to the topologically nearest node, not a political country.
- MDN — Content delivery network (CDN) overview
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.