Changelog

Subscribe to RSS

2025-11-25

Audit Logs for Cache Purge Events

You can now review detailed audit logs for cache purge events, giving you visibility into what purge requests were sent, what they contained, and by whom. Audit your purge requests via the Dashboard or API for all purge methods:

• Purge everything
• List of prefixes
• List of tags
• List of hosts
• List of files

Example

The detailed audit payload is visible within the Cloudflare Dashboard (under Manage Account > Audit Logs) and via the API. Below is an example of the Audit Logs v2 payload structure:

{
  "action": {
    "result": "success",
    "type": "create"
  },
  "actor": {
    "id": "1234567890abcdef",
    "email": "user@example.com",
    "type": "user"
  },
  "resource": {
    "product": "purge_cache",
    "request": {
      "files": [
        "https://example.com/images/logo.png",
        "https://example.com/css/styles.css"
      ]
    }
  },
  "zone": {
    "id": "023e105f4ecef8ad9ca31a8372d0c353",
    "name": "example.com"
  }
}

Get started

To get started, refer to the Audit Logs documentation.

2025-11-07

Inspect Cache Keys with Cloudflare Trace

You can now see the exact cache key generated for any request directly in Cloudflare Trace. This visibility helps you troubleshoot cache hits and misses, and verify that your Custom Cache Keys — configured via Cache Rules or Page Rules — are working as intended.

Previously, diagnosing caching behavior required inferring the key from configuration settings. Now, you can confirm that your custom logic for headers, query strings, and device types is correctly applied.

Access Trace via the dashboard or API, either manually for ad-hoc debugging or automated as part of your quality-of-service monitoring.

Example scenario

If you have a Cache Rule that segments content based on a specific cookie (for example, user_region), run a Trace with that cookie present to confirm the user_region value appears in the resulting cache key.

The Trace response includes the cache key in the cache object:

{
  "step_name": "request",
  "type": "cache",
  "matched": true,
  "public_name": "Cache Parameters",
  "cache": {
    "key": {
      "zone_id": "023e105f4ecef8ad9ca31a8372d0c353",
      "scheme": "https",
      "host": "example.com",
      "uri": "/images/hero.jpg"
    },
    "key_string": "023e105f4ecef8ad9ca31a8372d0c353::::https://example.com/images/hero.jpg:::::"
  }
}

Get started

To learn more, refer to the Trace documentation and our guide on Custom Cache Keys.

2025-08-29

Smart Tiered Cache Fallback to Generic

Smart Tiered Cache now falls back to Generic Tiered Cache when the origin location cannot be determined, improving cache precision for your content.

Previously, when Smart Tiered Cache was unable to select the optimal upper tier (such as when origins are masked by Anycast IPs), latency could be negatively impacted. This fallback now uses Generic Tiered Cache instead, providing better performance and cache efficiency.

How it works

When Smart Tiered Cache falls back to Generic Tiered Cache:

1. Multiple upper-tiers: Uses all of Cloudflare's global data centers as a network of upper-tiers instead of a single optimal location.
2. Distributed cache requests: Lower-tier data centers can query any available upper-tier for cached content.
3. Improved global coverage: Provides better cache hit ratios across geographically distributed visitors.
4. Automatic fallback: Seamlessly transitions when origin location cannot be determined, such as with Anycast-masked origins.

Benefits

• Preserves high performance during fallback: Smart Tiered Cache now maintains strong cache efficiency even when optimal upper tier selection is not possible.
• Minimizes latency impact: Automatically uses Generic Tiered Cache topology to keep performance high when origin location cannot be determined.
• Seamless experience: No configuration changes or intervention required when fallback occurs.
• Improved resilience: Smart Tiered Cache remains effective across diverse origin infrastructure, including Anycast-masked origins.

Get started

This improvement is automatically applied to all zones using Smart Tiered Cache. No action is required on your part.

2025-04-04

Workers Fetch API can override Cache Rules

You can now programmatically override Cache Rules using the cf object in the fetch() command. This feature gives you fine-grained control over caching behavior on a per-request basis, allowing Workers to customize cache settings dynamically based on request properties, user context, or business logic.

How it works

Using the cf object in fetch(), you can override specific Cache Rules settings by:

1. Setting custom cache options: Pass cache properties in the cf object as the second argument to fetch() to override default Cache Rules.
2. Dynamic cache control: Apply different caching strategies based on request headers, cookies, or other runtime conditions.
3. Per-request customization: Bypass or modify Cache Rules for individual requests while maintaining default behavior for others.
4. Programmatic cache management: Implement complex caching logic that adapts to your application's needs.

What can be configured

Workers can override the following Cache Rules settings through the cf object:

• cacheEverything: Treat all content as static and cache all file types beyond the default cached content.
• cacheTtl: Set custom time-to-live values in seconds for cached content at the edge, regardless of origin headers.
• cacheTtlByStatus: Set different TTLs based on the response status code (for example, { "200-299": 86400, 404: 1, "500-599": 0 }).
• cacheKey: Customize cache keys to control which requests are treated as the same for caching purposes (Enterprise only).
• cacheTags: Append additional cache tags for targeted cache purging operations.

Benefits

• Enhanced flexibility: Customize cache behavior without modifying zone-level Cache Rules.
• Dynamic optimization: Adjust caching strategies in real-time based on request context.
• Simplified configuration: Reduce the number of Cache Rules needed by handling edge cases programmatically.
• Improved performance: Fine-tune cache behavior for specific use cases to maximize hit rates.

Get started

To get started, refer to the Workers Fetch API documentation and the cf object properties documentation.

2025-04-03

All cache purge methods now available for all plans

You can now access all Cloudflare cache purge methods — no matter which plan you’re on. Whether you need to update a single asset or instantly invalidate large portions of your site’s content, you now have the same powerful tools previously reserved for Enterprise customers.

Anyone on Cloudflare can now:

1. Purge Everything: Clears all cached content associated with a website.
2. Purge by Prefix: Targets URLs sharing a common prefix.
3. Purge by Hostname: Invalidates content by specific hostnames.
4. Purge by URL (single-file purge): Precisely targets individual URLs.
5. Purge by Tag: Uses Cache-Tag response headers to invalidate grouped assets, offering flexibility for complex cache management scenarios.

Want to learn how each purge method works, when to use them, or what limits apply to your plan? Dive into our purge cache documentation and API reference ↗ for all the details.

2025-02-12

Configurable multiplexing HTTP/2 to Origin

You can now configure HTTP/2 multiplexing settings for origin connections on Enterprise plans. This feature allows you to optimize how Cloudflare manages concurrent requests over HTTP/2 connections to your origin servers, improving cache efficiency and reducing connection overhead.

How it works

HTTP/2 multiplexing allows multiple requests to be sent over a single TCP connection. With this configuration option, you can:

1. Control concurrent streams: Adjust the maximum number of concurrent streams per connection.
2. Optimize connection reuse: Fine-tune connection pooling behavior for your origin infrastructure.
3. Reduce connection overhead: Minimize the number of TCP connections required between Cloudflare and your origin.
4. Improve cache performance: Better connection management can enhance cache fetch efficiency.

Benefits

• Customizable performance: Tailor multiplexing settings to your origin's capabilities.
• Reduced latency: Fewer connection handshakes improve response times.
• Lower origin load: More efficient connection usage reduces server resource consumption.
• Enhanced scalability: Better connection management supports higher traffic volumes.

Get started

Enterprise customers can configure HTTP/2 multiplexing settings in the Cloudflare Dashboard ↗ or through our API.

Important consideration

This setting needs to be tuned carefully for your origin infrastructure. Setting the concurrent stream limit too high can negatively impact performance by saturating the shared TCP connection and overwhelming server processing capacity, leading to increased latency for individual requests.

2025-02-04

Fight CSAM More Easily Than Ever

You can now implement our child safety tooling, the CSAM Scanning Tool, more easily. Instead of requiring external reporting credentials, you only need a verified email address for notifications to onboard. This change makes the tool more accessible to a wider range of customers.

How It Works

When enabled, the tool automatically hashes images for enabled websites as they enter the Cloudflare cache ↗. These hashes are then checked against a database of known abusive images.

• Potential match detected?
  • The content URL is blocked, and
  • Cloudflare will notify you about the found matches via the provided email address.

Updated Service-Specific Terms

We have also made updates to our Service-Specific Terms ↗ to reflect these changes.

2025-01-08

Smart Tiered Cache optimizes Load Balancing Pools

You can now achieve higher cache hit rates and reduce origin load when using Load Balancing with Smart Tiered Cache. Cloudflare automatically selects a single, optimal tiered data center for all origins in your Load Balancing Pool.

How it works

When you use Load Balancing with Smart Tiered Cache, Cloudflare analyzes performance metrics across your pool's origins and automatically selects the optimal Upper Tier data center for the entire pool. This means:

• Consistent cache location: All origins in the pool share the same Upper Tier cache.
• Higher HIT rates: Requests for the same content hit the cache more frequently.
• Reduced origin requests: Fewer requests reach your origin servers.
• Improved performance: Faster response times for cache HITs.

Example workflow

Load Balancing Pool: api-pool
├── Origin 1: api-1.example.com
├── Origin 2: api-2.example.com
└── Origin 3: api-3.example.com
    ↓
Selected Upper Tier: [Optimal data center based on pool performance]

Get started

To get started, enable Smart Tiered Cache on your zone and configure your Load Balancing Pool.

2024-11-20

Smart Tiered Cache automatically optimizes R2 caching

You can now reduce latency and lower R2 egress costs automatically when using Smart Tiered Cache with R2. Cloudflare intelligently selects a tiered data center close to your R2 bucket location, creating an efficient caching topology without additional configuration.

How it works

When you enable Smart Tiered Cache for zones using R2 as an origin, Cloudflare automatically:

1. Identifies your R2 bucket location: Determines the geographical region where your R2 bucket is stored.
2. Selects an optimal Upper Tier: Chooses a data center close to your bucket as the common Upper Tier cache.
3. Routes requests efficiently: All cache misses in edge locations route through this Upper Tier before reaching R2.

Benefits

• Automatic optimization: No manual configuration required.
• Lower egress costs: Fewer requests to R2 reduce egress charges.
• Improved hit ratio: Common Upper Tier increases cache efficiency.
• Reduced latency: Upper Tier proximity to R2 minimizes fetch times.

Get started

To get started, enable Smart Tiered Cache on your zone using R2 as an origin.

2024-11-07

Stage and test cache configurations safely

You can now stage and test cache configurations before deploying them to production. Versioned environments let you safely validate cache rules, purge operations, and configuration changes without affecting live traffic.

How it works

With versioned environments, you can:

1. Create staging versions of your cache configuration.
2. Test cache rules in a non-production environment.
3. Purge staged content independently from production.
4. Validate changes before promoting to production.

This capability integrates with Cloudflare's broader versioning system, allowing you to manage cache configurations alongside other zone settings.

Benefits

• Risk-free testing: Validate configuration changes without impacting production.
• Independent purging: Clear staging cache without affecting live content.
• Deployment confidence: Catch issues before they reach end users.
• Team collaboration: Multiple team members can work on different versions.

Get started

To get started, refer to the version management documentation.

Important limitation

Cache Reserve is only supported for your production environment. Staged environments can use standard cache functionality, but Cache Reserve persistence is limited to production deployments.

2024-11-07

Shard cache using custom cache key values

Enterprise customers can now optimize cache hit ratios for content that varies by device, language, or referrer by sharding cache using up to ten values from previously restricted headers with custom cache keys.

How it works

When configuring custom cache keys, you can now include values from these headers to create distinct cache entries:

• accept* headers (for example, accept, accept-encoding, accept-language): Serve different cached versions based on content negotiation.
• referer header: Cache content differently based on the referring page or site.
• user-agent header: Maintain separate caches for different browsers, devices, or bots.

When to use cache sharding

• Content varies significantly by device type (mobile vs desktop).
• Different language or encoding preferences require distinct responses.
• Referrer-specific content optimization is needed.

Example configuration

{
  "cache_key": {
    "custom_key": {
      "header": {
        "include": ["accept-language", "user-agent"],
        "check_presence": ["referer"]
      }
    }
  }
}

This configuration creates separate cache entries based on the accept-language and user-agent headers, while also considering whether the referer header is present.

Get started

To get started, refer to the custom cache keys documentation.

Note

While cache sharding can improve hit ratios for specific use cases, overly sharding your cache can reduce overall cache efficiency and negatively impact performance. Carefully evaluate whether sharding benefits your specific traffic patterns.

2024-09-05

One-click Cache Rules templates now available

You can now create optimized cache rules instantly with one-click templates, eliminating the complexity of manual rule configuration.

How it works

1. Navigate to Rules > Templates in your Cloudflare dashboard.
2. Select a template for your use case.
3. Click to apply the template with sensible defaults.
4. Customize as needed for your specific requirements.

Available cache templates

• Cache everything: Adjust the cache level for all requests.
• Bypass cache for everything: Bypass cache for all requests.
• Cache default file extensions: Replicate Page Rules caching behavior by making only default extensions eligible for cache.
• Bypass cache on cookie: Bypass cache for requests containing specific cookies.
• Set edge cache time: Cache responses with status code between 200 and 599 on the Cloudflare edge.
• Set browser cache time: Adjust how long a browser should cache a resource.

Get started

To get started, go to Rules > Templates ↗ in the dashboard. For more information, refer to the Cache Rules documentation.

2024-07-19

Regionalized Generic Tiered Cache for higher hit ratios

You can now achieve higher cache hit ratios with Generic Global Tiered Cache. Regional content hashing routes content consistently to the same upper-tier data centers, eliminating redundant caching and reducing origin load.

How it works

Regional content hashing groups data centers by region and uses consistent hashing to route content to designated upper-tier caches:

• Same content always routes to the same upper-tier data center within a region.
• Eliminates redundant copies across multiple upper-tier caches.
• Increases the likelihood of cache HITs for the same content.

Example

A popular image requested from multiple edge locations in a region:

• Before: Cached at 3-4 different upper-tier data centers
• After: Cached at 1 designated upper-tier data center
• Result: 3-4x fewer cache MISSes, reducing origin load and improving performance

Get started

To get started, enable Generic Global Tiered Cache on your zone.