// AI Platform Drift

Cloudflare Queues adds EU, US, FedRAMP jurisdiction constraints

Cloudflare developer changelog · published 2026-10-18 22:56 UTC
WORTH KNOWING VERIFY_ONLY APISECURITY
WHAT CHANGEDCloudflare Queues now accepts a jurisdiction parameter at queue creation time, with three supported values: eu (European Union), us (United States), and fedramp (FedRAMP-Moderate data centers). The jurisdiction can only be set during creation via --jurisdiction flag in the CLI or jurisdiction field in the Create Queue API endpoint, and cannot be changed after the queue exists.
WHY IT MATTERSApplications with GDPR or FedRAMP compliance requirements can now enforce data residency at the queue level, ensuring messages are stored and processed only within the specified jurisdiction. Existing queues without a jurisdiction constraint remain unrestricted.
WHAT TO DOReview your queue inventory for data residency requirements. For queues handling EU personal data or FedRAMP-scoped workloads, create new jurisdiction-restricted queues and migrate message flows before decommissioning unrestricted queues.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Queues - Queues now supports EU, US, and FedRAMP jurisdictions
+https://developers.cloudflare.com/changelog/post/2026-09-18-queues-jurisdictions/
+Mon, 12 Oct 2026 00:00:00 GMT
+
+You can now create Cloudflare Queues with jurisdictional restrictions, ensuring that messages published to a queue are stored and processed only within a specific jurisdiction. This helps you comply with data residency requirements such as the GDPR ↗︎ or FedRAMP ↗︎.
+To create a jurisdiction-restricted queue with the Cloudflare CLI (cf), use the --jurisdiction flag:
+cf queues create --queue-name my-eu-queue --jurisdiction eu
+You can also pass a jurisdiction parameter when calling the Create Queue endpoint:
+curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/queues \
+--request POST \
+--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
+--header "Content-Type: application/json" \
+--data '{
+"queue_name": "my-eu-queue",
+"jurisdiction": "eu"
+}'
+Supported jurisdictions are eu (European Union), us (United States), and fedramp (FedRAMP-Moderate data centers). Jurisdiction can only be set when a queue is created and cannot be changed afterwards.
+For more information, refer to Queues data location.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew jurisdictional data residency feature materially changes queue deployment options and compliance posture for regulated workloads.
signalsnew feature: jurisdictional restrictions (EU, US, FedRAMP) · data residency compliance capability added · new API parameter: --jurisdiction flag and jurisdiction field · deployment/execution change: queue creation now accepts jurisdiction constraint · security/compliance: GDPR and FedRAMP compliance enablement
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)