Set a cloud-region hint only for the matching origin, verify that custom topology is not overriding it, and use CacheTieredFill logs to decide whether the change helped.
Update — August 12, 2026: Cloudflare’s current documentation adds the operational details that matter in production: custom tiered-cache topology takes precedence over a region hint, and the CacheTieredFill log field can show whether Tiered Cache served a request.
Smart Tiered Cache can accept a cloud-region hint for origins on AWS, Google Cloud, Azure, and Oracle Cloud. The hint gives Cloudflare geographic context when an origin IP belongs to an anycast or regional front end that obscures where the application actually runs.
This is not a generic performance toggle. It is a correction for a specific ambiguity in how the origin is reached. The right question is whether the configured IP or hostname fronts an origin in the region being declared.
Why the old signal can be misleading
Smart Tiered Cache normally uses performance and routing data to select one upper tier per origin. A lower tier asks that upper tier before the origin, so cache misses become concentrated rather than creating separate origin fetches from many data centers.
Anycast and regional-unicast cloud networks complicate that selection: a probe can reach a nearby provider edge without revealing the application’s backend region. Cloudflare documents a generic fallback when location cannot be determined; the region hint lets it choose a primary upper tier near the declared cloud region and retain a separate fallback for resilience.
Configuration is an infrastructure mapping
In the dashboard, go to Caching, Tiered Cache, then Origin Configuration. Find the origin IP or hostname, choose Set Region Hint, and select the provider and real deployment region—for example, `aws:us-east-1` or `gcp:europe-west1`. The API can list Cloudflare’s supported provider-region values before a mapping is applied, which is safer than hard-coding a guessed label in automation.
Make the mapping part of the same change record as the DNS, load-balancer, and origin move. If an application actively shifts a hostname between regions, the hint must move with it. Cloudflare also notes that a Custom Tiered Cache topology overrides region-hint mappings, so check that setting before expecting a result.
Measure the route, not just page speed
Capture a baseline for origin request volume, origin latency, cache status, error rate, and cache-miss behavior. In Cloudflare HTTP request logs, CacheTieredFill indicates that Tiered Cache was used for the request. Pair that field with the cache status and origin metrics; a faster synthetic page test alone cannot show whether the intended cache hierarchy changed.
Test from the markets that matter and during a realistic cache warm-up period. A topology change may temporarily raise MISS traffic while a new upper tier fills. If the signal does not improve, first verify the selected origin and custom-topology precedence, then remove the mapping rather than layering on unrelated cache rules.
This article explains the practical implications of the primary material below. PatchMemo does not publish vendor copy as editorial coverage and does not accept payment for positive coverage.
PatchMemo independently selects and evaluates the topics it covers. Analysis and recommendations are ours; sources are linked so readers can check the underlying claims. We clearly label sponsorships and affiliate relationships, and neither determines coverage or conclusions.
