Skip to content

Cache

Last updated View as MarkdownAgent setup

The following sections describe how to configure Cache with Regional Services and Customer Metadata Boundary to control where cached content is stored and served from.

Regional Services

To configure Regional Services for hostnames proxied (meaning traffic routes through Cloudflare) through Cloudflare and ensure that eligible assets are cached only in-region, follow these steps for the dashboard or API configuration:

  1. In the Cloudflare dashboard, go to the Records page.

    Go to Records ↗
  2. Follow these steps to create a DNS record.

  3. From the Region dropdown, select the region you would like to use on your domain.

  4. Select Save.

  1. To create records with the API, use the API POST command.
  2. Run the API POST command on the hostname to create a regional_hostnames with a specific region.

Egress to origin

Regional Services controls where user traffic is decrypted and processed within Cloudflare's network. It does not by itself guarantee the geolocation of the egress IPs used by the Cloudflare CDN when connecting to your origin server. Egress IPs to your origin are site-local IPs from the in-region data center where the request was processed.

If you need guaranteed egress IP geolocation — for example, to allowlist Cloudflare IPs on your origin from a specific country — use Dedicated CDN Egress IPs in combination with Regional Services.

Customer Metadata Boundary

Cache Analytics, Generic Global Tiered Cache and Custom Tiered Cache are compatible with Customer Metadata Boundary. With Customer Metadata Boundary set to EU, the Caching > Tiered Cache tab in the zone dashboard will not be populated.

For more information on CDN and caching, refer to the Cache documentation.

Was this helpful?