Data and AI releases

548 this month · 176 companies

Cloudflare WAN, Magic Transit, Cloudflare One - Unified Routing generally available

Generally availableNot yet verified

Unified Routing is generally available for Cloudflare WAN and Magic Transit. Unified Routing improves the integration between Cloudflare One and the standard connectivity onramps supported by Cloudflare WAN. It is capable of many new features including Automatic Return Routing, BGP and custom client subnets.

Also shipped Sep 18, 2026Cloudflare in September 2026 →

Lakebase Search is generally available

Lakebase Search is now generally available. It brings scalable vector and keyword search to Lakebase projects through two Postgres extensions, so you can run semantic and exact-term search in a single database without a separate search stack: lakebase_vector adds the lakebase_ann index type for approximate nearest-neighbor vector search.

GA
Source ↗

More from Cloudflare developer platformEvery Cloudflare developer platform release →

logpush, Logs - Filter DDoS attack traffic from Logpush jobs

Logpush jobs can now exclude identified distributed denial-of-service (DDoS) attack traffic. This option reduces attack traffic in delivered logs. It supports the http_requests , firewall_events , and network_analytics_logs datasets. In the dashboard, select Exclude DDoS attack traffic under Advanced Options .

Update
Source ↗

Workflows, Workers - Delete Workflow instances individually or in batches

You can now delete one or up to 100 Workflow instances and their stored state via the Workflows API or Wrangler 4.125.0 and later. Deleting an instance frees its stored state and stops its current execution. Storage billing is based on the average daily peak. Delete one instance by calling delete() on its handle: const instance = await env. MY_WORKFLOW .

Update
Source ↗

Workers AI - Reject busy synchronous inference requests

The rejectIfBusy option lets synchronous Workers AI inference requests fail when capacity is unavailable. Use it when your application should not wait in a capacity queue. Pass the option as the third argument to the Workers AI binding: const response = await env. AI .

Update
Source ↗