megachangelog
Feature

D1 - United States jurisdiction

D1 now supports creating databases with US jurisdiction for data residency compliance. Users can specify the us jurisdiction flag when creating databases to ensure data runs and persists within the United States.

You can create D1 databases with the us jurisdiction. These databases run and persist data within the United States.

Use this option for regional data residency requirements.

To create a database with the us jurisdiction, run:

npx wrangler@latest d1 create db-with-us-jurisdiction --jurisdiction=us

For more information, refer to D1 data location.

d1databasecompliancedata-residencyregional

Source: original entry ↗

More from Cloudflare

Follow Cloudflare to get its new changes in your feed and email digest.

Feature

Cloudflare API MCP server now serves Cloudflare skills

The Cloudflare API MCP server now integrates with the Skills over MCP extension, allowing MCP clients to discover and access Cloudflare skills. Users can add the MCP server endpoint to compatible MCP clients to access these skills.

apimcpagentsintegrationextension
Feature

WAF failed detections field now available in Rules

A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.

wafrulessecurityapidetections
Improvement

Markdown for Agents: More efficient in-process streaming conversion

Markdown for Agents now uses an in-process streaming engine at the edge to convert HTML, reducing overhead and memory use. The conversion limit increased from 2 MiB to 6 MiB, and token count headers are no longer generated.

markdownagentsperformancestreamingapi
See all Cloudflare changes →