Checking a CDN cache through regional proxy exits
Check whether regional CDN caches serve the expected release using controlled proxy views, cache headers and identifiable content versions.

A regional cache can explain an outdated page
A new product banner may appear immediately in one region and linger in its old version elsewhere. The proxy can help your team observe what different network locations receive, while the CDN's configuration and cache history influence the result. Prepare a versioned asset and a page with a known release marker so the comparison can identify actual content differences.
Read the cache indicators in context
On a site you operate, capture the response's cache-control settings, any Age field and the edge or cache status field documented by your CDN. Field names and meanings can vary across products. Compare the displayed content as well as the headers. A cached response can be correct throughout its allowed freshness window even when an updated origin exists.
If the page references versioned assets, inspect the document and the image independently. A current image file may already be available while an older cached document still points visitors to the previous version. RFC 9111, HTTP caching.
Separate route tests from release decisions
Keep the same asset path, timestamp window and browser state for each market. Share a short table of requested region, observed edge, content version and freshness expectation with the release owner. For an XtremeProxy test, request only the regions in which customers reported a difference. A few controlled observations in the affected areas usually explain a release issue better than a broad, poorly documented country sweep.
The new page reaches one edge before another
An owned release changes a public footer marker from revision 41 to 42. One regional observation returns 42 and another still returns 41. Compare the origin's current version, object age, cache policy and the request's effective representation. An old cached object can be consistent with its documented freshness period. A defect exists if the release agreement requires a faster update or the wrong market variant is served. Retest after the authorized invalidation or expected expiry.
Watch for release timing and representation variants
A content delivery service can select different objects by path, language or documented request variation. Preserve the relevant request characteristics and object revision, then compare with the origin's expected response. If a rollout intentionally progresses by region, obtain the release schedule before labeling the older edge version stale.
A fresh response from one edge does not state when every edge received the change. Store the last old observation and the first new observation per tested location. The true transition lies between those times. The observation interval makes the uncertainty in a rollout report visible.
Track when the new representation first appears
A controlled edge check sees revision 41 at 11:00 and revision 42 at 11:05. State that the change was visible by 11:05 and happened between the two samples if continuous availability is otherwise supported. Avoid recording precisely five minutes of stale content without knowing when the origin released and what the edge served between checks.
A cache may return different representations of the same regional page for legitimate reasons. For an owned fixture, keep the version of the selected language and content encoding with each observation. A newly published French representation and an older English representation at the same edge do not by themselves show inconsistent regional routing. Compare like representations across locations, then repeat within a location for the specific variant customers reported. This separates a stalled variant publication from a region-wide invalidation problem.
A cache purge request and a visible site update are two different timestamps. Suppose the publishing system acknowledges a purge at 10:02, but the origin does not start serving the new revision until 10:05. An edge that refreshes in between may correctly fetch the old revision again. Put the origin’s first confirmed new response beside the purge acknowledgement before investigating propagation. This sequence can explain a persistent old object without implying that the edge ignored the purge.
Related fieldwork
An operator can close a geographic cache investigation when the approved representation reaches the relevant edge under the agreed policy. Preserve the fixed source revision and timing interval so the release team can explain what changed. Regional image asset revisions checks regional image revisions. A practical check for regional cache contamination tests a different failure, in which one market receives another market's representation. Technical references include MDN guide to resource timing. Check XtremeProxy location coverage.
Frequently asked questions
Does a cache hit mean the content is stale?
A hit can serve a perfectly current representation. Inspect the revision and relevant freshness policy. An unexpected revision with documented age and request context is stronger evidence than a cache-status label on its own.