A point of presence (PoP) is a physical site, usually inside a data center or internet exchange, where a CDN, DNS provider or network operator runs servers that answer requests for nearby users. A large CDN operates dozens to hundreds of PoPs spread across many cities.
Why it matters
Distance adds latency. A visitor in Mumbai fetching a file from a server in Virginia pays for every round trip across the planet, and TLS plus HTTP multiply those trips. A nearby PoP terminates the connection locally and serves cached content directly, so only cache misses travel to your origin.
PoPs also absorb traffic spikes and attacks. A request flood is spread across many sites rather than landing on one server, and an unhealthy PoP can be drained while others keep serving.
Example
Many CDNs expose the serving PoP in a response header or a trace endpoint. The header name and format vary by provider, so check yours:
$ curl -sI https://example.com | grep -i -E "server|cf-ray|x-served-by|via"
cf-ray: 8a1b2c3d4e5f6a7b-BOMIn this style of header, the trailing code is an airport-like location identifier for the PoP that answered. Run the same command from another region and the code changes.
Common mistakes
- Assuming a PoP in your country will always serve your users. Routing follows network paths, not maps, so a user can be sent to a distant PoP.
- Testing performance from one location only and missing a slow region.
- Confusing a PoP with the origin. A PoP can be healthy while your origin is down, and cached pages may still load.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.