--- title: Changelogs image: https://developers.cloudflare.com/og-changelog.png --- [Skip to content](#main-content) All products Product groups AI Analytics Application performance Application security Cloudflare One Consumer services Core platform Developer platform Docs collections Media Network security Privacy Storage Products 1.1.1.1 (DNS Resolver) Access Agents AI Crawl Control AI Gateway AI Search Analytics API Shield Artifacts Audit Logs Billing Bots Browser Isolation Browser Run Cache / CDN CASB Challenges Cloudflare for SaaS Cloudflare Fundamentals Cloudflare Images Cloudflare Mesh Cloudflare Network Firewall Cloudflare One Cloudflare One Appliance Cloudflare One Client Cloudflare Tunnel Cloudflare Tunnel for SASE Cloudflare WAN Cloudflare Web Analytics Containers D1 Data Localization Suite Data Loss Prevention Digital Experience Monitoring DNS Durable Objects Email security Email Service Flagship Gateway Go SDK Hyperdrive KV Load Balancing Log Explorer Logpush Logs Magic Transit Multi-Cloud Networking Network Flow Network Interconnect Organizations Pages Pipelines Privacy Proxy Queues R2 R2 Data Catalog R2 SQL Radar Realtime Registrar Resource Tagging Risk Score Rules Sandbox SDK SDK Secrets Store Security Center Security Overview Speed SSL/TLS Stream Support Terraform Turnstile Vectorize WAF Workers Workers AI Workers Analytics Engine Workers for Platforms Workers VPC Workflows Zaraz No products found. [View RSS feeds](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/)[Subscribe to RSS](https://developers.cloudflare.com/changelog/rss/index.xml) Nov 21, 2024 [Improved non-English keyboard support](https://developers.cloudflare.com/changelog/post/2024-11-21-non-english-keyboard/) [Browser Isolation](https://developers.cloudflare.com/cloudflare-one/remote-browser-isolation/) You can now type in languages that use diacritics (like á or ç) and character-based scripts (such as Chinese, Japanese, and Korean) directly within the remote browser. The isolated browser now properly recognizes non-English keyboard input, eliminating the need to copy and paste content from a local browser or device. Nov 20, 2024 [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 11, 2024 [Bypass caching for subrequests made from Cloudflare Workers, with Request.cache](https://developers.cloudflare.com/changelog/post/2024-11-11-cache-no-store/) [Workers](https://developers.cloudflare.com/workers/) You can now use the [cache](https://developers.cloudflare.com/workers/runtime-apis/request/#options) property of the [Request](https://developers.cloudflare.com/workers/runtime-apis/request/) interface to bypass [Cloudflare's cache](https://developers.cloudflare.com/workers/reference/how-the-cache-works/) when making subrequests from [Cloudflare Workers](https://developers.cloudflare.com/workers), by setting its value to `no-store`. ```js export default { async fetch(req, env, ctx) { const request = new Request("https://cloudflare.com", { cache: "no-store", }); const response = await fetch(request); return response; }, }; ``` ```ts export default { async fetch(req, env, ctx): Promise { const request = new Request("https://cloudflare.com", { cache: 'no-store'}); const response = await fetch(request); return response; } } satisfies ExportedHandler ``` When you set the value to `no-store` on a subrequest made from a Worker, the Cloudflare Workers runtime will not check whether a match exists in the cache, and not add the response to the cache, even if the response includes directives in the `Cache-Control` HTTP header that otherwise indicate that the response is cacheable. This increases compatibility with NPM packages and JavaScript frameworks that rely on setting the [cache](https://developers.cloudflare.com/workers/runtime-apis/request/#options) property, which is a cross-platform standard part of the [Request](https://developers.cloudflare.com/workers/runtime-apis/request/) interface. Previously, if you set the `cache` property on `Request`, the Workers runtime threw an exception. If you've tried to use `@planetscale/database`, `redis-js`, `stytch-node`, `supabase`, `axiom-js` or have seen the error message `The cache field on RequestInitializerDict is not implemented in fetch` — you should try again, making sure that the [Compatibility Date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) of your Worker is set to on or after `2024-11-11`, or the [cache\_option\_enabled compatibility flag](https://developers.cloudflare.com/workers/configuration/compatibility-flags/#enable-cache-no-store-http-standard-api) is enabled for your Worker. * Learn [how the Cache works with Cloudflare Workers](https://developers.cloudflare.com/workers/reference/how-the-cache-works/) * Enable [Node.js compatibility](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) for your Cloudflare Worker * Explore [Runtime APIs](https://developers.cloudflare.com/workers/runtime-apis/) and [Bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/) available in Cloudflare Workers Nov 7, 2024 [Use Logpush for Email security user actions](https://developers.cloudflare.com/changelog/post/2024-11-07-logpush-user-actions/) [Email security](https://developers.cloudflare.com/cloudflare-one/email-security/) You can now send user action logs for Email security to an endpoint of your choice with Cloudflare Logpush. Filter logs matching specific criteria you have set or select from multiple fields you want to send. For all users, we will log the date and time, user ID, IP address, details about the message they accessed, and what actions they took. When creating a new Logpush job, remember to select **Audit logs** as the dataset and filter by: * **Field**: `"ResourceType"` * **Operator**: `"starts with"` * **Value**: `"email_security"`. ![Logpush-user-actions](https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=829,height=454,format=webp/_astro/Logpush-User-Actions.D14fWgmq.png) For more information, refer to [Enable user action logs](https://developers.cloudflare.com/cloudflare-one/insights/logs/logpush/email-security-logs/#enable-user-action-logs). This feature is available across all Email security packages: * **Enterprise** * **Enterprise + PhishGuard** Nov 7, 2024 [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 7, 2024 [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 ```json { "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 24, 2024 [Workflows is now in open beta](https://developers.cloudflare.com/changelog/post/2024-10-24-workflows-beta/) [Workers](https://developers.cloudflare.com/workers/)[Workflows](https://developers.cloudflare.com/workflows/) Workflows is now in open beta, and available to any developer a free or paid Workers plan. Workflows allow you to build multi-step applications that can automatically retry, persist state and run for minutes, hours, days, or weeks. Workflows introduces a programming model that makes it easier to build reliable, long-running tasks, observe as they progress, and programmatically trigger instances based on events across your services. #### Get started You can get started with Workflows by [following our get started guide](https://developers.cloudflare.com/workflows/get-started/guide/) and/or using `npm create cloudflare` to pull down the starter project: ```sh npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflows-starter" ``` You can open the `src/index.ts` file, extend it, and use `wrangler deploy` to deploy your first Workflow. From there, you can: * Learn the [Workflows API](https://developers.cloudflare.com/workflows/build/workers-api/) * [Trigger Workflows](https://developers.cloudflare.com/workflows/build/trigger-workflows/) via your Workers apps. * Understand the [Rules of Workflows](https://developers.cloudflare.com/workflows/build/rules-of-workflows/) and how to adopt best practices Oct 23, 2024 [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/cdn-cgi/image/onerror=redirect,width=1158,height=1305,format=webp/_astro/create-url-rewrite-rule.DIgpB8IB.png) 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). Oct 8, 2024 [New fields added to Gateway-related datasets in Cloudflare Logs](https://developers.cloudflare.com/changelog/post/2024-10-08-new-gateway-fields/) [Logs](https://developers.cloudflare.com/logs/) Cloudflare has introduced new fields to two Gateway-related datasets in Cloudflare Logs: * **Gateway HTTP**: `ApplicationIDs`, `ApplicationNames`, `CategoryIDs`, `CategoryNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `VirtualNetworkID`, and `VirtualNetworkName`. * **Gateway Network**: `ApplicationIDs`, `ApplicationNames`, `DestinationIPContinentCode`, `DestinationIPCountryCode`, `ProxyEndpoint`, `SourceIPContinentCode`, `SourceIPCountryCode`, `TransportProtocol`, `VirtualNetworkID`, and `VirtualNetworkName`. Oct 2, 2024 [Search for custom rules using rule name and/or ID](https://developers.cloudflare.com/changelog/post/2024-10-02-custom-rule-search/) [Cloudflare Network Firewall](https://developers.cloudflare.com/cloudflare-network-firewall/) The Magic Firewall dashboard now allows you to search custom rules using the rule name and/or ID. 1. Log into the [Cloudflare dashboard ↗](https://dash.cloudflare.com) and select your account. 2. Go to **Analytics & Logs** \> **Network Analytics**. 3. Select **Magic Firewall**. 4. Add a filter for **Rule ID**. ![Search for firewall rules with rule IDs](https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=1032,height=801,format=webp/_astro/search-with-rule-id.DJgzqgKk.png) Additionally, the rule ID URL link has been added to Network Analytics. Oct 1, 2024 [Eliminate long-lived credentials and enhance SSH security with Cloudflare Access for Infrastructure](https://developers.cloudflare.com/changelog/post/2024-10-01-ssh-with-access-for-infrastructure/) [Access](https://developers.cloudflare.com/cloudflare-one/access-controls/policies/) Organizations can now eliminate long-lived credentials from their SSH setup and enable strong multi-factor authentication for SSH access, similar to other Access applications, all while generating access and command logs. SSH with [Access for Infrastructure](https://developers.cloudflare.com/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/) uses short-lived SSH certificates from Cloudflare, eliminating SSH key management and reducing the security risks associated with lost or stolen keys. It also leverages a common deployment model for Cloudflare One customers: [WARP-to-Tunnel](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-device-client/). SSH with Access for Infrastructure enables you to: * **Author fine-grained policy** to control who may access your SSH servers, including specific ports, protocols, and SSH users. * **Monitor infrastructure access** with Access and SSH command logs, supporting regulatory compliance and providing visibility in case of security breach. * **Preserve your end users' workflows.** SSH with Access for Infrastructure supports native SSH clients and does not require any modifications to users’ SSH configs. ![Example of an infrastructure Access application](https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=1916,height=1714,format=webp/_astro/infrastructure-app.BhpJOgxs.png) To get started, refer to [SSH with Access for Infrastructure](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access/). Sep 24, 2024 [Try out Magic Network Monitoring](https://developers.cloudflare.com/changelog/post/2024-09-24-magic-network-monitoring/) [Network Flow](https://developers.cloudflare.com/network-flow/) The free version of Magic Network Monitoring (MNM) is now available to everyone with a Cloudflare account by default. 1. Log in to your [Cloudflare dashboard ↗](https://dash.cloudflare.com), and select your account. 2. Go to **Analytics & Logs** \> **Magic Monitoring**. ![Try out the free version of Magic Network Monitoring](https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=852,height=666,format=webp/_astro/get-started.D7KXWcs4.png) For more details, refer to the [Get started guide](https://developers.cloudflare.com/network-flow/get-started/). Sep 23, 2024 [AI Crawl Control](https://developers.cloudflare.com/changelog/post/2024-09-23-ai-audit-launch/) [AI Crawl Control](https://developers.cloudflare.com/ai-crawl-control/) Every site on Cloudflare now has access to [**AI Audit**](https://developers.cloudflare.com/ai-crawl-control/), which summarizes the crawling behavior of popular and known AI services. You can use this data to: * Understand how and how often crawlers access your site (and which content is the most popular). * Block specific AI bots accessing your site. * Use Cloudflare to enforce your `robots.txt` policy via an automatic WAF rule. ![View AI bot activity with AI Audit](https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=1494,height=746,format=webp/_astro/ai-crawl-control-overview.Dr_yGKOC.png) To get started, explore [AI audit](https://developers.cloudflare.com/ai-crawl-control/). Sep 5, 2024 [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 5, 2024 [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/cdn-cgi/image/onerror=redirect,width=800,height=424,format=webp/_astro/rules-templates.DAV0GOXF.gif) 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 [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. Jun 17, 2024 [Exchange user risk scores with Okta](https://developers.cloudflare.com/changelog/post/2024-06-17-okta-risk-exchange/) [Risk Score](https://developers.cloudflare.com/cloudflare-one/insights/risk-score/) Beyond the controls in [Zero Trust](https://developers.cloudflare.com/cloudflare-one/), you can now [exchange user risk scores](https://developers.cloudflare.com/cloudflare-one/team-and-resources/users/risk-score/#send-risk-score-to-okta) with Okta to inform SSO-level policies. First, configure Cloudflare One to send user risk scores to Okta. 1. Set up the [Okta SSO integration](https://developers.cloudflare.com/cloudflare-one/integrations/identity-providers/okta/). 2. In the [Cloudflare dashboard ↗](https://dash.cloudflare.com/), go to **Zero Trust** \> **Integrations** \> **Identity providers**. 3. In **Your identity providers**, locate your Okta integration and select **Edit**. 4. Turn on **Send risk score to Okta**. 5. Select **Save**. 6. Upon saving, Cloudflare One will display the well-known URL for your organization. Copy the value. Next, configure Okta to receive your risk scores. 1. On your Okta admin dashboard, go to **Security** \> **Device Integrations**. 2. Go to **Receive shared signals**, then select **Create stream**. 3. Name your integration. In **Set up integration with**, choose _Well-known URL_. 4. In **Well-known URL**, enter the well-known URL value provided by Cloudflare One. 5. Select **Create**. Jun 16, 2024 [Explore product updates for Cloudflare One](https://developers.cloudflare.com/changelog/post/2024-06-16-cloudflare-one/) [Access](https://developers.cloudflare.com/cloudflare-one/access-controls/policies/)[Browser Isolation](https://developers.cloudflare.com/cloudflare-one/remote-browser-isolation/)[CASB](https://developers.cloudflare.com/cloudflare-one/integrations/cloud-and-saas/)[Cloudflare Tunnel for SASE](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/)[Digital Experience Monitoring](https://developers.cloudflare.com/cloudflare-one/insights/dex/)[Data Loss Prevention](https://developers.cloudflare.com/cloudflare-one/data-loss-prevention/)[Email security](https://developers.cloudflare.com/cloudflare-one/email-security/)[Gateway](https://developers.cloudflare.com/cloudflare-one/traffic-policies/)[Multi-Cloud Networking](https://developers.cloudflare.com/multi-cloud-networking/)[Cloudflare Network Firewall](https://developers.cloudflare.com/cloudflare-network-firewall/)[Network Flow](https://developers.cloudflare.com/network-flow/)[Magic Transit](https://developers.cloudflare.com/magic-transit/)[Cloudflare WAN](https://developers.cloudflare.com/cloudflare-wan/)[Network Interconnect](https://developers.cloudflare.com/network-interconnect/)[Risk Score](https://developers.cloudflare.com/cloudflare-one/insights/risk-score/)[Cloudflare One Client](https://developers.cloudflare.com/cloudflare-one/team-and-resources/devices/cloudflare-one-client/) Welcome to your new home for product updates on [Cloudflare One](https://developers.cloudflare.com/cloudflare-one/). Our [new changelog](https://developers.cloudflare.com/changelog/) lets you read about changes in much more depth, offering in-depth examples, images, code samples, and even gifs. If you are looking for older product updates, refer to the following locations. Older product updates * [Access](https://developers.cloudflare.com/cloudflare-one/changelog/access/) * [Browser Isolation](https://developers.cloudflare.com/cloudflare-one/changelog/browser-isolation/) * [CASB](https://developers.cloudflare.com/cloudflare-one/changelog/casb/) * [Cloudflare Tunnel](https://developers.cloudflare.com/cloudflare-one/changelog/tunnel/) * [Data Loss Prevention](https://developers.cloudflare.com/cloudflare-one/changelog/dlp/) * [Digital Experience Monitoring](https://developers.cloudflare.com/cloudflare-one/changelog/dex/) * [Email security](https://developers.cloudflare.com/cloudflare-one/changelog/email-security/) * [Gateway](https://developers.cloudflare.com/cloudflare-one/changelog/gateway/) * [Multi-Cloud Networking](https://developers.cloudflare.com/multi-cloud-networking/changelog/) * [Cloudflare Network Firewall](https://developers.cloudflare.com/cloudflare-network-firewall/changelog/) * [Magic Network Monitoring](https://developers.cloudflare.com/network-flow/changelog/) * [Magic Transit](https://developers.cloudflare.com/magic-transit/changelog/) * [Magic WAN](https://developers.cloudflare.com/cloudflare-wan/changelog/) * [Network Interconnect](https://developers.cloudflare.com/network-interconnect/changelog/) * [Risk score](https://developers.cloudflare.com/cloudflare-one/changelog/risk-score/) * [Cloudflare One Client](https://developers.cloudflare.com/changelog/cloudflare-one-client/) Feb 26, 2024 [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/cdn-cgi/image/onerror=redirect,width=1101,height=1061,format=webp/_astro/2025-02-26-rum-eu.X0ZtbXWA.png) 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. ```json {"@context":"https://schema.org","@type":"BlogPosting","@id":"https://developers.cloudflare.com/changelog/45/#page","headline":"Changelogs | Cloudflare Docs","url":"https://developers.cloudflare.com/changelog/45/","inLanguage":"en","image":"https://developers.cloudflare.com/og-changelog.png","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}} ```