--- title: Changelogs 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/) All products ![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_26AMqX.svg) Feb 03, 2025 1. ### [Terraform v5 Provider is now generally available](https://developers.cloudflare.com/changelog/post/2025-02-03-terraform-v5-provider/) [ Cloudflare Fundamentals ](https://developers.cloudflare.com/fundamentals/)[ Terraform ](https://developers.cloudflare.com/terraform/) ![Screenshot of Terraform defining a Zone](https://developers.cloudflare.com/_astro/2024-02-03-terraform-v5-screenshot.mW8OaFoS_Z2pw8Bq.webp) Cloudflare's v5 Terraform Provider is now generally available. With this release, Terraform resources are now automatically generated based on OpenAPI Schemas. This change brings alignment across our SDKs, API documentation, and now Terraform Provider. The new provider boosts coverage by increasing support for API properties to 100%, adding 25% more resources, and more than 200 additional data sources. Going forward, this will also reduce the barriers to bringing more resources into Terraform across the broader Cloudflare API. This is a small, but important step to making more of our platform manageable through GitOps, making it easier for you to manage Cloudflare just like you do your other infrastructure. The Cloudflare Terraform Provider v5 is a ground-up rewrite of the provider and introduces breaking changes for some resource types. Please refer to the [upgrade guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade) for best practices, or the [blog post on automatically generating Cloudflare's Terraform Provider ↗](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more information about the approach. For more info * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) * [Documentation on using Terraform with Cloudflare ↗](https://developers.cloudflare.com/terraform/) Feb 03, 2025 1. ### [Revamped Workers Metrics](https://developers.cloudflare.com/changelog/post/2025-02-03-workers-metrics-revamp/) [ Workers ](https://developers.cloudflare.com/workers/) We've revamped the [Workers Metrics dashboard ↗](https://dash.cloudflare.com/?to=/:account/workers/services/view/:worker/production/metrics/). ![Workers Metrics dashboard](https://developers.cloudflare.com/_astro/workers-metrics.IxYk9yF0_Z1h2eg9.webp) Now you can easily compare metrics across Worker versions, understand the current state of a [gradual deployment](https://developers.cloudflare.com/workers/configuration/versions-and-deployments/gradual-deployments/), and review key Workers metrics in a single view. This new interface enables you to: * Drag-and-select using a graphical timepicker for precise metric selection. ![Workers Metrics graphical timepicker](https://developers.cloudflare.com/_astro/metrics-graphical-timepicker.tzLlEF5U_Z102O4.webp) * Use histograms to visualize cumulative metrics, allowing you to bucket and compare rates over time. * Focus on Worker versions by directly interacting with the version numbers in the legend. ![Workers Metrics legend selector](https://developers.cloudflare.com/_astro/metrics-legend-selector.B2GY90Hn_27rpVV.webp) * Monitor and compare active gradual deployments. * Track error rates across versions with grouping both by version and by invocation status. * Measure how [Smart Placement](https://developers.cloudflare.com/workers/configuration/placement/) improves request duration. Learn more about [metrics](https://developers.cloudflare.com/workers/observability/metrics-and-analytics). Feb 02, 2025 1. ### [Removed unused meta fields from DNS records](https://developers.cloudflare.com/changelog/post/2025-02-02-removed-meta-fields/) [ DNS ](https://developers.cloudflare.com/dns/) Cloudflare is removing five fields from the `meta` object of DNS records. These fields have been unused for more than a year and are no longer set on new records. This change may take up to four weeks to fully roll out. The affected fields are: * the `auto_added` boolean * the `managed_by_apps` boolean and corresponding `apps_install_id` * the `managed_by_argo_tunnel` boolean and corresponding `argo_tunnel_id` An example record returned from the API would now look like the following: Updated API Response ``` { "result": { "id": "", "zone_id": "", "zone_name": "example.com", "name": "www.example.com", "type": "A", "content": "192.0.2.1", "proxiable": true, "proxied": false, "ttl": 1, "locked": false, "meta": { "auto_added": false, "managed_by_apps": false, "managed_by_argo_tunnel": false, "source": "primary" }, "comment": null, "tags": [], "created_on": "2025-03-17T20:37:05.368097Z", "modified_on": "2025-03-17T20:37:05.368097Z" }, "success": true, "errors": [], "messages": []} ``` For more guidance, refer to [Manage DNS records](https://developers.cloudflare.com/dns/manage-dns-records/). Jan 31, 2025 1. ### [Workers for Platforms now supports Static Assets](https://developers.cloudflare.com/changelog/post/2025-01-31-workers-platforms-static-assets/) [ Workers for Platforms ](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/) Workers for Platforms customers can now attach static assets (HTML, CSS, JavaScript, images) directly to User Workers, removing the need to host separate infrastructure to serve the assets. This allows your platform to serve entire front-end applications from Cloudflare's global edge, utilizing caching for fast load times, while supporting dynamic logic within the same Worker. Cloudflare automatically scales its infrastructure to handle high traffic volumes, enabling you to focus on building features without managing servers. #### What you can build **Static Sites:** Host and serve HTML, CSS, JavaScript, and media files directly from Cloudflare's network, ensuring fast loading times worldwide. This is ideal for blogs, landing pages, and documentation sites because static assets can be efficiently cached and delivered closer to the user, reducing latency and enhancing the overall user experience. **Full-Stack Applications:** Combine asset hosting with Cloudflare Workers to power dynamic, interactive applications. If you're an e-commerce platform, you can serve your customers' product pages and run inventory checks from within the same Worker. * [ JavaScript ](#tab-panel-4913) * [ TypeScript ](#tab-panel-4914) index.js ``` export default { async fetch(request, env) { const url = new URL(request.url); // Check real-time inventory if (url.pathname === "/api/inventory/check") { const product = url.searchParams.get("product"); const inventory = await env.INVENTORY_KV.get(product); return new Response(inventory); } // Serve static assets (HTML, CSS, images) return env.ASSETS.fetch(request); },}; ``` index.ts ``` export default { async fetch(request, env) { const url = new URL(request.url); // Check real-time inventory if (url.pathname === '/api/inventory/check') { const product = url.searchParams.get('product'); const inventory = await env.INVENTORY_KV.get(product); return new Response(inventory); } // Serve static assets (HTML, CSS, images) return env.ASSETS.fetch(request); }}; ``` **Get Started:**Upload static assets using the Workers for Platforms API or Wrangler. For more information, visit our [Workers for Platforms documentation. ↗](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/static-assets/) Jan 31, 2025 1. ### [Transform HTML quickly with streaming content](https://developers.cloudflare.com/changelog/post/2025-01-31-html-rewriter-streaming/) [ Workers ](https://developers.cloudflare.com/workers/) You can now transform HTML elements with streamed content using [HTMLRewriter](https://developers.cloudflare.com/workers/runtime-apis/html-rewriter). Methods like `replace`, `append`, and `prepend` now accept [Response](https://developers.cloudflare.com/workers/runtime-apis/response/) and [ReadableStream](https://developers.cloudflare.com/workers/runtime-apis/streams/readablestream/)values as [Content](https://developers.cloudflare.com/workers/runtime-apis/html-rewriter/#global-types). This can be helpful in a variety of situations. For instance, you may have a Worker in front of an origin, and want to replace an element with content from a different source. Prior to this change, you would have to load all of the content from the upstream URL and convert it into a string before replacing the element. This slowed down overall response times. Now, you can pass the `Response` object directly into the `replace` method, and HTMLRewriter will immediately start replacing the content as it is streamed in. This makes responses faster. * [ JavaScript ](#tab-panel-4915) * [ TypeScript ](#tab-panel-4916) index.js ``` class ElementRewriter { async element(element) { // able to replace elements while streaming content // the fetched body is not buffered into memory as part // of the replace let res = await fetch("https://upstream-content-provider.example"); element.replace(res); }} export default { async fetch(request, env, ctx) { let response = await fetch("https://site-to-replace.com"); return new HTMLRewriter() .on("[data-to-replace]", new ElementRewriter()) .transform(response); },}; ``` index.ts ``` class ElementRewriter { async element(element: any) { // able to replace elements while streaming content // the fetched body is not buffered into memory as part // of the replace let res = await fetch('https://upstream-content-provider.example'); element.replace(res); }} export default { async fetch(request, env, ctx): Promise { let response = await fetch('https://site-to-replace.com'); return new HTMLRewriter().on('[data-to-replace]', new ElementRewriter()).transform(response); },} satisfies ExportedHandler; ``` For more information, see the [HTMLRewriter documentation](https://developers.cloudflare.com/workers/runtime-apis/html-rewriter). Jan 30, 2025 1. ### [AI Gateway Introduces New Worker Binding Methods](https://developers.cloudflare.com/changelog/post/2025-01-26-worker-binding-methods/) [ AI Gateway ](https://developers.cloudflare.com/ai-gateway/) We have released new [Workers bindings API methods](https://developers.cloudflare.com/ai-gateway/usage/worker-binding-methods/), allowing you to connect Workers applications to AI Gateway directly. These methods simplify how Workers calls AI services behind your AI Gateway configurations, removing the need to use the REST API and manually authenticate. To add an AI binding to your Worker, include the following in your [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/): ![Add an AI binding to your Worker.](https://developers.cloudflare.com/_astro/add-binding.BoYTiyon_ZjdDNx.webp) With the new AI Gateway binding methods, you can now: * Send feedback and update metadata with `patchLog`. * Retrieve detailed log information using `getLog`. * Execute [universal requests](https://developers.cloudflare.com/ai-gateway/usage/universal/) to any AI Gateway provider with `run`. For example, to send feedback and update metadata using `patchLog`: ![Send feedback and update metadata using patchLog:](https://developers.cloudflare.com/_astro/send-feedback.BGRzKmd9_NDVos.webp) Jan 30, 2025 1. ### [Increased Browser Rendering limits!](https://developers.cloudflare.com/changelog/post/2025-01-30-browser-rendering-more-instances/) [ Workers ](https://developers.cloudflare.com/workers/)[ Browser Run ](https://developers.cloudflare.com/browser-run/) [Browser Rendering](https://developers.cloudflare.com/browser-run/) now supports 10 concurrent browser instances per account _and_ 10 new instances per minute, up from the previous limits of 2. This allows you to launch more browser tasks from [Cloudflare Workers](https://developers.cloudflare.com/workers). To manage concurrent browser sessions, you can use [Queues](https://developers.cloudflare.com/queues/) or [Workflows](https://developers.cloudflare.com/workflows/): * [ JavaScript ](#tab-panel-4921) * [ TypeScript ](#tab-panel-4922) index.js ``` export default { async queue(batch, env) { for (const message of batch.messages) { const browser = await puppeteer.launch(env.BROWSER); const page = await browser.newPage(); try { await page.goto(message.url, { waitUntil: message.waitUntil, }); // Process page... } finally { await browser.close(); } } },}; ``` index.ts ``` interface QueueMessage { url: string; waitUntil: number;} export interface Env { BROWSER_QUEUE: Queue; BROWSER: Fetcher;} export default { async queue(batch: MessageBatch, env: Env): Promise { for (const message of batch.messages) { const browser = await puppeteer.launch(env.BROWSER); const page = await browser.newPage(); try { await page.goto(message.url, { waitUntil: message.waitUntil, }); // Process page... } finally { await browser.close(); } } },}; ``` Jan 30, 2025 1. ### [Expanded language support for Stream AI Generated Captions](https://developers.cloudflare.com/changelog/post/2025-01-30-stream-generated-captions-new-languages/) [ Stream ](https://developers.cloudflare.com/stream/) Stream's [generated captions](https://developers.cloudflare.com/stream/edit-videos/adding-captions/#generate-a-caption)leverage Workers AI to automatically transcribe audio and provide captions to the player experience. We have added support for these languages: * `cs` \- Czech * `nl` \- Dutch * `fr` \- French * `de` \- German * `it` \- Italian * `ja` \- Japanese * `ko` \- Korean * `pl` \- Polish * `pt` \- Portuguese * `ru` \- Russian * `es` \- Spanish For more information, learn about [adding captions to videos](https://developers.cloudflare.com/stream/edit-videos/adding-captions/). Jan 29, 2025 1. ### [New Snippets Code Editor](https://developers.cloudflare.com/changelog/post/2025-01-29-snippets-code-editor/) [ Rules ](https://developers.cloudflare.com/rules/) The new [Snippets](https://developers.cloudflare.com/rules/snippets/) code editor lets you edit Snippet code and rule in one place, making it easier to test and deploy changes without switching between pages. ![New Snippets code editor](https://developers.cloudflare.com/_astro/snippets-new-editor.CaoIu2_-_Z2rsmyM.webp) What’s new: * **Single-page editing for code and rule** – No need to jump between screens. * **Auto-complete & syntax highlighting** – Get suggestions and avoid mistakes. * **Code formatting & refactoring** – Write cleaner, more readable code. Try it now in [Rules > Snippets ↗](https://dash.cloudflare.com/?to=/:account/:zone/rules/snippets). Jan 28, 2025 1. ### [Automatic configuration for private databases on Hyperdrive](https://developers.cloudflare.com/changelog/post/2025-01-28-hyperdrive-automated-private-database-configuration/) [ Hyperdrive ](https://developers.cloudflare.com/hyperdrive/) Hyperdrive now automatically configures your Cloudflare Tunnel to connect to your private database. ![Automatic configuration of Cloudflare Access and Service Token in the Cloudflare dashboard for Hyperdrive.](https://developers.cloudflare.com/_astro/hyperdrive-private-database-automatic-configuration.BT4_KLwW_2nAXi4.webp) When creating a Hyperdrive configuration for a private database, you only need to provide your database credentials and set up a Cloudflare Tunnel within the private network where your database is accessible. Hyperdrive will automatically create the Cloudflare Access, Service Token, and Policies needed to secure and restrict your Cloudflare Tunnel to the Hyperdrive configuration. To create a Hyperdrive for a private database, you can follow the [Hyperdrive documentation](https://developers.cloudflare.com/hyperdrive/configuration/connect-to-private-database/). You can still manually create the Cloudflare Access, Service Token, and Policies if you prefer. This feature is available from the Cloudflare dashboard. Jan 28, 2025 1. ### [Workers KV namespace limits increased to 1000](https://developers.cloudflare.com/changelog/post/2025-01-27-kv-increased-namespaces-limits/) [ KV ](https://developers.cloudflare.com/kv/) You can now have up to 1000 Workers KV namespaces per account. Workers KV namespace limits were increased from 200 to 1000 for all accounts. Higher limits for Workers KV namespaces enable better organization of key-value data, such as by category, tenant, or environment. Consult the [Workers KV limits documentation](https://developers.cloudflare.com/kv/platform/limits/) for the rest of the limits. This increased limit is available for both the Free and Paid [Workers plans](https://developers.cloudflare.com/workers/platform/pricing/). Jan 28, 2025 1. ### [Support for Node.js DNS, Net, and Timer APIs in Workers](https://developers.cloudflare.com/changelog/post/2025-01-28-nodejs-compat-improvements/) [ Workers ](https://developers.cloudflare.com/workers/) When using a Worker with the [nodejs\_compat](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) compatibility flag enabled, you can now use the following Node.js APIs: * [node:net](https://developers.cloudflare.com/workers/runtime-apis/nodejs/net/) * [node:dns](https://developers.cloudflare.com/workers/runtime-apis/nodejs/dns/) * [node:timers](https://developers.cloudflare.com/workers/runtime-apis/nodejs/timers/) #### node:net You can use [node:net ↗](https://nodejs.org/api/net.html) to create a direct connection to servers via a TCP sockets with [net.Socket ↗](https://nodejs.org/api/net.html#class-netsocket). * [ JavaScript ](#tab-panel-4919) * [ TypeScript ](#tab-panel-4920) index.js ``` import net from "node:net"; const exampleIP = "127.0.0.1"; export default { async fetch(req) { const socket = new net.Socket(); socket.connect(4000, exampleIP, function () { console.log("Connected"); }); socket.write("Hello, Server!"); socket.end(); return new Response("Wrote to server", { status: 200 }); },}; ``` index.ts ``` import net from "node:net"; const exampleIP = "127.0.0.1"; export default { async fetch(req): Promise { const socket = new net.Socket(); socket.connect(4000, exampleIP, function () { console.log("Connected"); }); socket.write("Hello, Server!"); socket.end(); return new Response("Wrote to server", { status: 200 }); },} satisfies ExportedHandler; ``` Additionally, you can now use other APIs including [net.BlockList ↗](https://nodejs.org/api/net.html#class-netblocklist) and [net.SocketAddress ↗](https://nodejs.org/api/net.html#class-netsocketaddress). Note that [net.Server ↗](https://nodejs.org/api/net.html#class-netserver) is not supported. #### node:dns You can use [node:dns ↗](https://nodejs.org/api/dns.html) for name resolution via [DNS over HTTPS](https://developers.cloudflare.com/1.1.1.1/encryption/dns-over-https/) using [Cloudflare DNS ↗](https://www.cloudflare.com/application-services/products/dns/) at 1.1.1.1. * [ JavaScript ](#tab-panel-4911) * [ TypeScript ](#tab-panel-4912) index.js ``` import dns from "node:dns"; let response = await dns.promises.resolve4("cloudflare.com", "NS"); ``` index.ts ``` import dns from 'node:dns'; let response = await dns.promises.resolve4('cloudflare.com', 'NS'); ``` All `node:dns` functions are available, except `lookup`, `lookupService`, and `resolve` which throw "Not implemented" errors when called. #### node:timers You can use [node:timers ↗](https://nodejs.org/api/timers.html) to schedule functions to be called at some future period of time. This includes [setTimeout ↗](https://nodejs.org/api/timers.html#settimeoutcallback-delay-args) for calling a function after a delay, [setInterval ↗](https://nodejs.org/api/timers.html#setintervalcallback-delay-args) for calling a function repeatedly, and [setImmediate ↗](https://nodejs.org/api/timers.html#setimmediatecallback-args) for calling a function in the next iteration of the event loop. * [ JavaScript ](#tab-panel-4917) * [ TypeScript ](#tab-panel-4918) index.js ``` import timers from "node:timers"; console.log("first");timers.setTimeout(() => { console.log("last");}, 10); timers.setTimeout(() => { console.log("next");}); ``` index.ts ``` import timers from "node:timers"; console.log("first");timers.setTimeout(() => { console.log("last");}, 10); timers.setTimeout(() => { console.log("next");}); ``` Jan 21, 2025 1. ### [WAF Release - 2025-01-21](https://developers.cloudflare.com/changelog/post/2025-01-21-waf-release/) [ WAF ](https://developers.cloudflare.com/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | -------------------------- | ----------- | -------------- | ---------------------------- | --------------- | ---------- | -------------------------------- | | Cloudflare Managed Ruleset | ...b090ba9a | 100303 | Command Injection - Nslookup | Log | Block | This was released as ...b8d152f4 | | Cloudflare Managed Ruleset | ...49e6b538 | 100534 | Web Shell Activity | Log | Block | This was released as ...82fe4e7f | Jan 20, 2025 1. ### [Detect source code leaks with Data Loss Prevention](https://developers.cloudflare.com/changelog/post/2025-01-03-source-code-confidence-level/) [ Data Loss Prevention ](https://developers.cloudflare.com/cloudflare-one/data-loss-prevention/) You can now detect source code leaks with Data Loss Prevention (DLP) with predefined checks against common programming languages. The following programming languages are validated with natural language processing (NLP). * C * C++ * C# * Go * Haskell * Java * JavaScript * Lua * Python * R * Rust * Swift DLP also supports confidence level for [source code profiles](https://developers.cloudflare.com/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles/#source-code). For more details, refer to [DLP profiles](https://developers.cloudflare.com/cloudflare-one/data-loss-prevention/dlp-profiles/). Jan 15, 2025 1. ### [Export SSH command logs with Access for Infrastructure using Logpush](https://developers.cloudflare.com/changelog/post/2025-01-15-ssh-logs-and-logpush/) [ Access ](https://developers.cloudflare.com/cloudflare-one/access-controls/policies/) Availability Only available on Enterprise plans. Cloudflare now allows you to send SSH command logs to storage destinations configured in [Logpush](https://developers.cloudflare.com/logs/logpush/), including third-party destinations. Once exported, analyze and audit the data as best fits your organization! For a list of available data fields, refer to the [SSH logs dataset](https://developers.cloudflare.com/logs/logpush/logpush-job/datasets/account/ssh%5Flogs/). To set up a Logpush job, refer to [Logpush integration](https://developers.cloudflare.com/cloudflare-one/insights/logs/logpush/). Jan 15, 2025 1. ### [Increased Workflows limits and improved instance queueing.](https://developers.cloudflare.com/changelog/post/2025-01-15-workflows-more-steps/) [ Workflows ](https://developers.cloudflare.com/workflows/) [Workflows](https://developers.cloudflare.com/workflows/) (beta) now allows you to define up to 1024 [steps](https://developers.cloudflare.com/workflows/build/workers-api/#workflowstep). `sleep` steps do not count against this limit. We've also added: * `instanceId` as property to the [WorkflowEvent](https://developers.cloudflare.com/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance * Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state. * Support for [pause and resume](https://developers.cloudflare.com/workflows/build/workers-api/#pause) for Workflow instances in a queued state. We're continuing to work on increases to the number of concurrent Workflow instances, steps, and support for a new `waitForEvent` API over the coming weeks. Jan 13, 2025 1. ### [WAF Release - 2025-01-13](https://developers.cloudflare.com/changelog/post/2025-01-13-waf-release/) [ WAF ](https://developers.cloudflare.com/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | -------------------------- | ----------- | -------------- | --------------------------------------------------------------------------------------------- | --------------- | ---------- | ------------- | | Cloudflare Managed Ruleset | ...f49e5840 | 100704 | Cleo Harmony - Auth Bypass - CVE:CVE-2024-55956, CVE:CVE-2024-55953 | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...a6d43bc2 | 100705 | Sentry - SSRF | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...ce6311bb | 100706 | Apache Struts - Remote Code Execution - CVE:CVE-2024-53677 | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...2233da1f | 100707 | FortiWLM - Remote Code Execution - CVE:CVE-2023-48782, CVE:CVE-2023-34993, CVE:CVE-2023-34990 | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...e31d972a | 100007C\_BETA | Command Injection - Common Attack Commands | | Disabled | | Jan 09, 2025 1. ### [New Rules Overview Interface](https://developers.cloudflare.com/changelog/post/2025-01-09-rules-overview/) [ Rules ](https://developers.cloudflare.com/rules/) **Rules Overview** gives you a single page to manage all your [Cloudflare Rules](https://developers.cloudflare.com/rules/). What you can do: * **See all your rules in one place** – No more clicking around. * **Find rules faster** – Search by name. * **Understand execution order** – See how rules run in sequence. * **Debug easily** – Use [Trace](https://developers.cloudflare.com/rules/trace-request/) without switching tabs. Check it out in [Rules > Overview ↗](https://dash.cloudflare.com/?to=/:account/:zone/rules/overview). 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/). Jan 07, 2025 1. ### [40-60% Faster D1 Worker API Requests](https://developers.cloudflare.com/changelog/post/2025-01-07-d1-faster-query/) [ D1 ](https://developers.cloudflare.com/d1/) Users making [D1](https://developers.cloudflare.com/d1/) requests via the [Workers API](https://developers.cloudflare.com/d1/worker-api/) can see up to a 60% end-to-end latency improvement due to the removal of redundant network round trips needed for each request to a D1 database. ![D1 Worker API latency](https://developers.cloudflare.com/_astro/faster-d1-worker-api.4S7VSUdP_1LmJ72.webp) _p50, p90, and p95 request latency aggregated across entire D1 service. These latencies are a reference point and should not be viewed as your exact workload improvement._ This performance improvement benefits all D1 Worker API traffic, especially cross-region requests where network latency is an outsized latency factor. For example, a user in Europe talking to a database in North America. D1 [location hints](https://developers.cloudflare.com/d1/configuration/data-location/#provide-a-location-hint) can be used to influence the geographic location of a database. For more details on how D1 removed redundant round trips, see the D1 specific release note [entry](https://developers.cloudflare.com/d1/platform/release-notes/#2025-01-07). Jan 06, 2025 1. ### [WAF Release - 2025-01-06](https://developers.cloudflare.com/changelog/post/2025-01-06-waf-release/) [ WAF ](https://developers.cloudflare.com/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | ------------------- | ----------- | -------------- | --------------------------------------------------------------------------------------------------------- | --------------- | ---------- | ------------- | | Cloudflare Specials | ...9da08beb | 100678 | Pandora FMS - Remote Code Execution - CVE:CVE-2024-11320 | Log | Block | New Detection | | Cloudflare Specials | ...ecdf3d02 | 100679 | Palo Alto Networks - Remote Code Execution - CVE:CVE-2024-0012, CVE:CVE-2024-9474 | Log | Block | New Detection | | Cloudflare Specials | ...a40f2a35 | 100680 | Ivanti - Command Injection - CVE:CVE-2024-37397 | Log | Block | New Detection | | Cloudflare Specials | ...58ae3c89 | 100681 | Really Simple Security - Auth Bypass - CVE:CVE-2024-10924 | Log | Block | New Detection | | Cloudflare Specials | ...e37f2da6 | 100682 | Magento - XXE - CVE:CVE-2024-34102 | Log | Block | New Detection | | Cloudflare Specials | ...5054c752 | 100683 | CyberPanel - Remote Code Execution - CVE:CVE-2024-51567 | Log | Block | New Detection | | Cloudflare Specials | ...dfe93d7b | 100684 | Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38094, CVE:CVE-2024-38024, CVE:CVE-2024-38023 | Log | Block | New Detection | | Cloudflare Specials | ...1454c856 | 100685 | CyberPanel - Remote Code Execution - CVE:CVE-2024-51568 | Log | Block | New Detection | | Cloudflare Specials | ...e92362e5 | 100686 | Seeyon - Remote Code Execution | Log | Block | New Detection | | Cloudflare Specials | ...b9f1c9f8 | 100687 | WordPress - Remote Code Execution - CVE:CVE-2024-10781, CVE:CVE-2024-10542 | Log | Block | New Detection | | Cloudflare Specials | ...0d7ca374 | 100688 | ProjectSend - Remote Code Execution - CVE:CVE-2024-11680 | Log | Block | New Detection | | Cloudflare Specials | ...a5260b70 | 100689 | Palo Alto GlobalProtect - Remote Code Execution - CVE:CVE-2024-5921 | Log | Block | New Detection | | Cloudflare Specials | ...d007118b | 100690 | Ivanti - Remote Code Execution - CVE:CVE-2024-37404 | Log | Block | New Detection | | Cloudflare Specials | ...c3e49f64 | 100691 | Array Networks - Remote Code Execution - CVE:CVE-2023-28461 | Log | Block | New Detection | | Cloudflare Specials | ...fcc6f5bb | 100692 | CyberPanel - Remote Code Execution - CVE:CVE-2024-51378 | Log | Block | New Detection | | Cloudflare Specials | ...b615335e | 100693 | Symfony Profiler - Auth Bypass - CVE:CVE-2024-50340 | Log | Block | New Detection | | Cloudflare Specials | ...09d08c8a | 100694 | Citrix Virtual Apps - Remote Code Execution - CVE:CVE-2024-8069 | Log | Block | New Detection | | Cloudflare Specials | ...8aafb2f5 | 100695 | MSMQ Service - Remote Code Execution - CVE:CVE-2023-21554 | Log | Block | New Detection | | Cloudflare Specials | ...11b7a8c7 | 100696 | Nginxui - Remote Code Execution - CVE:CVE-2024-49368 | Log | Block | New Detection | | Cloudflare Specials | ...45954c7e | 100697 | Apache ShardingSphere - Remote Code Execution - CVE:CVE-2022-22733 | Log | Block | New Detection | | Cloudflare Specials | ...f5311209 | 100698 | Mitel MiCollab - Auth Bypass - CVE:CVE-2024-41713 | Log | Block | New Detection | | Cloudflare Specials | ...b3e5e46e | 100699 | Apache Solr - Auth Bypass - CVE:CVE-2024-45216 | Log | Block | New Detection | Jan 02, 2025 1. ### [AI Gateway adds DeepSeek as a Provider](https://developers.cloudflare.com/changelog/post/2025-01-07-aig-provider-deepseek/) [ AI Gateway ](https://developers.cloudflare.com/ai-gateway/) [**AI Gateway**](https://developers.cloudflare.com/ai-gateway/) now supports [**DeepSeek**](https://developers.cloudflare.com/ai-gateway/usage/providers/deepseek/), including their cutting-edge DeepSeek-V3 model. With this addition, you have even more flexibility to manage and optimize your AI workloads using AI Gateway. Whether you're leveraging DeepSeek or other providers, like OpenAI, Anthropic, or [Workers AI](https://developers.cloudflare.com/workers-ai/), AI Gateway empowers you to: * **Monitor**: Gain actionable insights with analytics and logs. * **Control**: Implement caching, rate limiting, and fallbacks. * **Optimize**: Improve performance with feedback and evaluations. ![AI Gateway adds DeepSeek as a provider](https://developers.cloudflare.com/_astro/deepseek.hirkr3rv_CgMEY.webp) To get started, simply update the base URL of your DeepSeek API calls to route through AI Gateway. Here's how you can send a request using cURL: Example fetch request ``` curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek/chat/completions \ --header 'content-type: application/json' \ --header 'Authorization: Bearer DEEPSEEK_TOKEN' \ --data '{ "model": "deepseek-chat", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ]}' ``` For detailed setup instructions, see our [DeepSeek provider documentation](https://developers.cloudflare.com/ai-gateway/usage/providers/deepseek/). Dec 29, 2024 1. ### [Faster Workers Builds with Build Caching and Watch Paths](https://developers.cloudflare.com/changelog/post/2024-12-29-faster-builds/) [ Workers ](https://developers.cloudflare.com/workers/) ![Build caching settings](https://developers.cloudflare.com/_astro/workers-build-caching.DWEh3Tj1_Z1HXvDQ.webp)![Build watch path settings](https://developers.cloudflare.com/_astro/workers-build-watch-paths.ClqD-iNq_ZUCGHo.webp) [**Workers Builds**](https://developers.cloudflare.com/workers/ci-cd/builds/), the integrated CI/CD system for Workers (currently in beta), now lets you cache artifacts across builds, speeding up build jobs by eliminating repeated work, such as downloading dependencies at the start of each build. * **[Build Caching](https://developers.cloudflare.com/workers/ci-cd/builds/build-caching/)**: Cache dependencies and build outputs between builds with a shared project-wide cache, ensuring faster builds for the entire team. * **[Build Watch Paths](https://developers.cloudflare.com/workers/ci-cd/builds/build-watch-paths/)**: Define paths to include or exclude from the build process, ideal for [monorepos](https://developers.cloudflare.com/workers/ci-cd/builds/advanced-setups/#monorepos) to target only the files that need to be rebuilt per Workers project. To get started, select your Worker on the [Cloudflare dashboard ↗](https://dash.cloudflare.com) then go to **Settings** \> **Builds**, and connect a GitHub or GitLab repository. Once connected, you'll see options to configure Build Caching and Build Watch Paths. Dec 19, 2024 1. ### [Escalate user submissions](https://developers.cloudflare.com/changelog/post/2024-12-19-escalate-user-submissions/) [ Email security ](https://developers.cloudflare.com/cloudflare-one/email-security/) After you triage your users' submissions (that are machine reviewed), you can now escalate them to our team for reclassification (which are instead human reviewed). User submissions from the submission alias, PhishNet, and our API can all be escalated. ![Escalate](https://developers.cloudflare.com/_astro/Escalate.CwXPIyM3_ZxuRN6.webp) From **Reclassifications**, go to **User submissions**. Select the three dots next to any of the user submissions, then select **Escalate** to create a team request for reclassification. The Cloudflare dashboard will then show you the submissions on the **Team Submissions** tab. Refer to [User submissions](https://developers.cloudflare.com/cloudflare-one/email-security/submissions/user-submissions/) to learn more about this feature. This feature is available across these Email security packages: * **Advantage** * **Enterprise** * **Enterprise + PhishGuard** Dec 19, 2024 1. ### [Increased transparency for phishing email submissions](https://developers.cloudflare.com/changelog/post/2024-12-19-reclassification-tab/) [ Email security ](https://developers.cloudflare.com/cloudflare-one/email-security/) You now have more transparency about team and user submissions for phishing emails through a **Reclassification** tab in the Zero Trust dashboard. Reclassifications happen when users or admins [submit a phish](https://developers.cloudflare.com/cloudflare-one/email-security/settings/phish-submissions/) to Email security. Cloudflare reviews and - in some cases - reclassifies these emails based on improvements to our machine learning models. This new tab increases your visibility into this process, allowing you to view what submissions you have made and what the outcomes of those submissions are. ![Use the Reclassification area to review submitted phishing emails](https://developers.cloudflare.com/_astro/reclassifications-tab.yDgtjG51_Z1TVbIE.webp) ```json {"@context":"https://schema.org","@type":"BlogPosting","@id":"https://developers.cloudflare.com/changelog/39/#page","headline":"Changelogs | Cloudflare Docs","url":"https://developers.cloudflare.com/changelog/39/","inLanguage":"en","image":"https://developers.cloudflare.com/cf-twitter-card.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/"}} ```