Data and AI releases

548 this month · 176 companies

Bots - New Account Abuse Protection Dashboard

UpdateNot yet verified

Account Abuse Protection customers in Early Access can now investigate login and sign up activity in a dedicated dashboard under Security > Account Abuse Protection . Population overview: See total login and sign up events, unique accounts, IPs and devices, top countries and ASNs, and leaked credential check results.

SecurityBIObservability

Also shipped Nov 2, 2026Cloudflare in November 2026 →

More from Cloudflare developer platformEvery Cloudflare developer platform release →

Flagship - Evaluate Flagship flags locally

Flagship bindings now evaluate flags against a local flag store during local development, instead of calling your remote app. You can develop offline and test flag changes without affecting production. This applies to wrangler dev , the Cloudflare Vite plugin , the Vitest integration , and cf dev .

Update
Source ↗

Workers will use the new module registry by default on November 17

Starting November 17, 2026, JavaScript Workers with a compatibility date of 2026-11-17 or later will use the new module registry by default. You will no longer need the new_module_registry flag for these dates. Python Workers keep using the legacy registry. The module registry finds and loads JavaScript modules in your Worker.

Update
Source ↗

Workers - Request.signal will be enabled by default in Workers on November 17

Starting November 17, 2026, Workers with a compatibility date of 2026-11-17 or later will receive client disconnection events through request.signal by default. Use these events to stop unnecessary work when a client leaves. You will no longer need the enable_request_signal compatibility flag for these dates. We introduced this feature in May 2025 .

Update
Source ↗

AI Gateway - New AI Gateways require authentication

New AI Gateways now require authentication to prevent unauthorized requests. Once authentication is on, you cannot turn it off through the dashboard or API. When you create a new AI Gateway through the API, authentication is on by default. You can leave out the authentication field or set it to true . If you set it to false , the API returns HTTP 400 .

Update
Source ↗