---
title: Application performance Changelog
image: https://developers.cloudflare.com/cf-twitter-card.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://developers.cloudflare.com/changelog/llms.txt  
> Use this file to discover all available pages before exploring further.

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://developers.cloudflare.com/changelog/rss/index.xml) [ View RSS feeds ](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/) 

Application performance

![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_26AMqX.svg) 

Jan 08, 2025
1. ### [Smart Tiered Cache optimizes Load Balancing Pools](https://developers.cloudflare.com/changelog/post/2025-01-08-smart-tiered-cache-for-load-balancing/)  
[ Cache / CDN ](https://developers.cloudflare.com/cache/)  
You can now achieve higher cache hit rates and reduce origin load when using [Load Balancing](https://developers.cloudflare.com/load-balancing/) with [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/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](https://developers.cloudflare.com/load-balancing/) with [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/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](https://developers.cloudflare.com/cache/how-to/tiered-cache/) on your zone and configure your [Load Balancing Pool](https://developers.cloudflare.com/load-balancing/).

Dec 11, 2024
1. ### [Terraform Support for Snippets](https://developers.cloudflare.com/changelog/post/2024-12-11-terraform-snippets/)  
[ Rules ](https://developers.cloudflare.com/rules/)  
Now, you can manage [Cloudflare Snippets](https://developers.cloudflare.com/rules/snippets/) with [Terraform](https://developers.cloudflare.com/terraform/). Use infrastructure-as-code to deploy and update Snippet code and rules without manual changes in the dashboard.  
Example Terraform configuration:  
```  
resource "cloudflare_snippet" "my_snippet" {  
  zone_id  = "<ZONE_ID>"  
  name = "my_test_snippet_1"  
  main_module = "file1.js"  
  files {  
    name = "file1.js"  
    content = file("file1.js")  
  }  
}  
resource "cloudflare_snippet_rules" "cookie_snippet_rule" {  
  zone_id  = "<ZONE_ID>"  
  rules {  
    enabled = true  
    expression = "http.cookie eq \"a=b\""  
    description = "Trigger snippet on specific cookie"  
    snippet_name = "my_test_snippet_1"  
  }  
  depends_on = [cloudflare_snippet.my_snippet]  
}  
```  
Learn more in the [Configure Snippets using Terraform](https://developers.cloudflare.com/rules/snippets/create-terraform/) documentation.

Nov 22, 2024
1. ### [Cloud Connector Now Supports R2](https://developers.cloudflare.com/changelog/post/2024-11-22-cloud-connector-r2/)  
[ Rules ](https://developers.cloudflare.com/rules/)  
Now, you can use [Cloud Connector](https://developers.cloudflare.com/rules/cloud-connector/) to route traffic to your [R2 buckets](https://developers.cloudflare.com/r2/) based on URLs, headers, geolocation, and more.  
Example setup:  
Terminal window  
```  
curl --request PUT \  
"https://api.cloudflare.com/client/v4/zones/{zone_id}/cloud_connector/rules" \  
--header "Authorization: Bearer <API_TOKEN>" \  
--header "Content-Type: application/json" \  
--data '[  
  {  
    "expression": "http.request.uri.path wildcard \"/images/*\"",  
    "provider": "cloudflare_r2",  
    "description": "Connect to R2 bucket containing images",  
    "parameters": {  
      "host": "mybucketcustomdomain.example.com"  
    }  
  }  
]'  
```  
Get started using [Cloud Connector](https://developers.cloudflare.com/rules/cloud-connector/) documentation.

Nov 20, 2024
1. ### [Smart Tiered Cache automatically optimizes R2 caching](https://developers.cloudflare.com/changelog/post/2024-11-20-smart-tiered-cache-for-r2/)  
[ Cache / CDN ](https://developers.cloudflare.com/cache/)  
You can now reduce latency and lower R2 egress costs automatically when using [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/) with [R2](https://developers.cloudflare.com/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](https://developers.cloudflare.com/cache/how-to/tiered-cache/) for zones using [R2](https://developers.cloudflare.com/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](https://developers.cloudflare.com/cache/how-to/tiered-cache/) on your zone using R2 as an origin.

Nov 07, 2024
1. ### [Stage and test cache configurations safely](https://developers.cloudflare.com/changelog/post/2024-11-07-cache-versioning/)  
[ Cache / CDN ](https://developers.cloudflare.com/cache/)  
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](https://developers.cloudflare.com/version-management/), 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](https://developers.cloudflare.com/version-management/).  
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.

Nov 07, 2024
1. ### [Shard cache using custom cache key values](https://developers.cloudflare.com/changelog/post/2024-11-07-shard-cache-by-cache-key/)  
[ Cache / CDN ](https://developers.cloudflare.com/cache/)  
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](https://developers.cloudflare.com/cache/how-to/cache-keys/).  
#### How it works  
When configuring [custom cache keys](https://developers.cloudflare.com/cache/how-to/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](https://developers.cloudflare.com/cache/how-to/cache-keys/).  
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.

Oct 23, 2024
1. ### [Simplified UI for URL Rewrites](https://developers.cloudflare.com/changelog/post/2024-10-23-url-rewrites-wildcard/)  
[ Rules ](https://developers.cloudflare.com/rules/)  
It’s now easy to create **wildcard-based [URL Rewrites](https://developers.cloudflare.com/rules/transform/url-rewrite/)**. No need for complex functions—just define your patterns and go.  
![Rules Overview Interface](https://developers.cloudflare.com/_astro/create-url-rewrite-rule.DIgpB8IB_ZNTjfK.webp)  
What’s improved:  
   * **Full wildcard support** – Create rewrite patterns using intuitive interface.  
   * **Simplified rule creation** – No need for complex functions.  
Try it via [creating a Rewrite URL rule in the dashboard](https://developers.cloudflare.com/rules/transform/url-rewrite/create-dashboard/#wildcard-pattern-parameters).

Sep 05, 2024
1. ### [One-click Cache Rules templates now available](https://developers.cloudflare.com/changelog/post/2024-09-05-cache-rules-templates/)  
[ Cache / CDN ](https://developers.cloudflare.com/cache/)  
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** ↗](https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules) in the dashboard. For more information, refer to the [Cache Rules documentation](https://developers.cloudflare.com/cache/how-to/cache-rules/).

Sep 05, 2024
1. ### [New Rules Templates for One-Click Rule Creation](https://developers.cloudflare.com/changelog/post/2024-09-05-rules-templates/)  
[ Rules ](https://developers.cloudflare.com/rules/)  
Now, you can create **common rule configurations** in just **one click** using Rules Templates.  
![Rules Templates](https://developers.cloudflare.com/_astro/rules-templates.DAV0GOXF_Z2wOoyL.webp)  
What you can do:  
   * **Pick a pre-built rule** – Choose from a library of templates.  
   * **One-click setup** – Deploy best practices instantly.  
   * **Customize as needed** – Adjust templates to fit your setup.  
Template cards are now also available directly in the rule builder for each product.  
Need more ideas? Check out the [Examples gallery](https://developers.cloudflare.com/rules/examples/) in our documentation.

Jul 19, 2024
1. ### [Regionalized Generic Tiered Cache for higher hit ratios](https://developers.cloudflare.com/changelog/post/2024-07-19-regionalized-generic-tiered-cache/)  
[ Cache / CDN ](https://developers.cloudflare.com/cache/)  
You can now achieve higher cache hit ratios with [Generic Global Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/#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](https://developers.cloudflare.com/cache/how-to/tiered-cache/#generic-global-tiered-cache) on your zone.

Feb 26, 2024
1. ### [Easily Exclude EU Visitors from RUM](https://developers.cloudflare.com/changelog/post/2025-02-25-rum-exclude-eu/)  
[ Cloudflare Web Analytics ](https://developers.cloudflare.com/web-analytics/)  
You can now easily enable Real User Monitoring (RUM) monitoring for your hostnames, while safely dropping requests from visitors in the European Union to comply with GDPR and CCPA.  
![RUM Enablement UI](https://developers.cloudflare.com/_astro/2025-02-26-rum-eu.X0ZtbXWA_eanJk.webp)  
Our Web Analytics product has always been centered on giving you insights into your users' experience that you need to provide the best quality experience, without sacrificing user privacy in the process.  
To help with that aim, you can now selectively enable RUM monitoring for your hostname and exclude EU visitor data in a single click. If you opt for this option, we will drop all metrics collected by our EU data centers automatically.  
You can learn more about what metrics are reported by Web Analytics and how it is collected [in the Web Analytics documentation](https://developers.cloudflare.com/web-analytics/data-metrics/). You can enable Web Analytics on any hostname by going to the [Web Analytics ↗](https://dash.cloudflare.com/?to=/:account/web-analytics/sites) section of the dashboard, selecting "Manage Site" for the hostname you want to monitor, and choosing the appropriate enablement option.

[Search all changelog entries](https://developers.cloudflare.com/search/?contentType=Changelog+entry) 