Claude in the EU: 47 region deployments, one quota wall, and how to fail over without leaving Europe

On 5 September a developer posted in r/ClaudeAI: Can't get Claude/Opus running in the EU via AWS Bedrock or Google Vertex, has anyone done this? The requirement was ordinary ("customer data can't leave the EU"). The experience was not. On Bedrock Frankfurt, "even a tiny test request threw an immediate 429 'Too many tokens per day'." On Vertex, Claude needed a service account rather than an API key, plus an enablement form asking for industry and estimated token volume, and the form appeared to be the real bottleneck.

Four days later, in r/LLMDevs, a solo developer running production apps on Bedrock described the wall from the other side: a daily Claude Opus quota of around 2.5 million tokens, "tight enough to interrupt normal usage," two quota increase requests, both rejected. The apps process private customer documents, so the fallback has to keep the privacy properties: no training on prompts, no persistent storage, and "privacy restrictions also apply when requests fall back to another provider."

These are the two halves of the same fact. Anthropic's first party API does not have an EU processing region, so every European Claude is a cloud Claude, and cloud Claude comes with per account, per region, per model quotas that a small team cannot negotiate. The fix is not a bigger quota. It is more quota pools.

47 deployments, six regions, two platforms

Here is every EU region Claude deployment in the Requesty catalog on 10 September 2026:

Read it as a quota map. Each filled cell is a distinct deployment with its own capacity and its own AWS or GCP quota. The current models (Opus 5, Opus 4.8, Opus 4.7, Sonnet 4.6, Sonnet 4.5, Haiku 4.5) each exist in four Bedrock regions plus Vertex, so five pools per model. Sonnet 5 is in four. The Fable models, the two highest ranked models on the intelligence ranking, are Vertex EU multi region only.

Prices are per million tokens and are the same in every cell for a given model: Opus 5 at $5.50 and $27.50, Sonnet 5 at $2.20 and $11.00, Sonnet 4.6 and 4.5 at $3.30 and $16.50, Haiku 4.5 at $1.10 and $5.50, Fable 5 and 5.1 at $11.00 and $55.00. That is a 10% premium over the global route, which is the hyperscaler's EU uplift, not the gateway's; the same 10% appears across every frontier vendor's EU pricing. Because the price is flat across regions, region choice is entirely about capacity and latency.

Why one region is the wrong architecture

The r/ClaudeAI poster's 429 on a first request is not a bug; it is how Bedrock onboards. Anthropic model quotas on Bedrock are set per account, per region and per model, new accounts start low, and raising them is a Service Quotas request that AWS can decline. The r/LLMDevs poster hit the same mechanism a year later in production: 2.5M Opus tokens a day, two rejections. Vertex has a parallel gate: Anthropic models require a service account and an enablement review per project, and Anthropic's own Claude on Google Cloud documentation notes that "model availability varies by region" and that "regional and multi-region endpoints include a 10% pricing premium over global endpoints."

If your production path is one region on one platform, your ceiling is whatever that one quota is, and your availability is whatever that one region's availability is. Last week's correlated outage made the second point; the two Reddit threads make the first. Neither problem is solved by asking harder for a bigger number.

The alternative is already in the table. Opus 5 exists in Frankfurt, Ireland, Paris, Stockholm and on Vertex. Those are five quota pools for the same weights at the same price, all inside the EU. A request that gets a 429 in Frankfurt can be served from Ireland in the same second, and the data has not left the Union.

A fallback policy that stays in the EU

The pattern in Requesty is a fallback policy: an ordered list of model deployments, retried in sequence on failure, exposed to your application as one model id. For EU Claude it looks like this:

policy: eu-opus-5
  1. bedrock/claude-opus-5@eu-central-1     Frankfurt
  2. bedrock/claude-opus-5@eu-west-1        Ireland
  3. bedrock/claude-opus-5@eu-north-1       Stockholm
  4. bedrock/claude-opus-5@eu-west-3        Paris
  5. vertex/claude-opus-5@eu                Vertex EU multi region

Your code calls model: "policy/eu-opus-5" against https://router.eu.requesty.ai/v1. A 429, a 5xx or a timeout on Frankfurt moves the request down the chain. Every entry is the same model at the same price, so the fallback is invisible to your users and to your finance team. If you want the last resort to be a cheaper model rather than the same one, append bedrock/claude-sonnet-5@eu-central-1; it is a different model but it is still in the EU.

Three details matter for the privacy requirement the r/LLMDevs poster set:

• The chain never leaves the EU by construction, because every entry is an EU region deployment. The failure mode to avoid is a fallback list that ends in anthropic/claude-opus-5, the global route, which would send the request to the US on exactly the day you have an incident. Restricting the Approved Models list to EU regions makes that entry impossible to add.
• The gateway leg stays in Frankfurt. The router.eu.requesty.ai endpoint processes, logs and caches in AWS eu-central-1. The EU routing documentation is careful about the two layers: EU endpoint for the gateway, EU model for inference, both required.
• Zero data retention applies to every hop. ZDR is an organisation setting, not a per provider one, so the "privacy restrictions also apply when requests fall back" requirement is met by the layer that does the falling back. Bedrock and Vertex do not train on API traffic; the DPA covers the processor obligations.

If you already have your own Bedrock or Vertex accounts and quotas, bring your own keys lets the policy use them, so the fallback chain can mix your Frankfurt quota with Requesty's Ireland capacity. The r/LLMDevs poster's second constraint, staying on AWS billing, is met the same way.

What about Fable?

The two highest ranked models in the world, Claude Fable 5.1 (53.4 on the Intelligence Index) and Fable 5 (49.7), exist in the EU only on Vertex's EU multi region endpoint. One pool, one platform. That is the current state, and it is worth stating plainly rather than papering over: an EU only organisation that wants the top of the ranking has one route to it today.

Two mitigations. First, the Fable models' natural fallback is Opus 5 (50.7, third on the ranking), which has five EU pools and costs half as much per token. A policy of vertex/claude-fable-5.1@eu then bedrock/claude-opus-5@eu-central-1 gives you the frontier when Vertex has capacity and a model 2.7 index points behind it when it does not. Second, Anthropic's cache read price cut on Fable 5.1 applies on Vertex EU as well: the catalog lists cache reads at $0.275 per million against $11.00 for input, so agentic workloads that hit the cache pay far less than the headline rate suggests.

What the two posters should do

For the r/ClaudeAI developer stuck on a 429 and an enablement form: you do not need your own Bedrock quota or your own Vertex enablement to run Claude in the EU. Point the Anthropic or OpenAI SDK at router.eu.requesty.ai, call bedrock/claude-opus-5@eu-central-1 or the fallback policy above, and the request runs in Frankfurt on Requesty's capacity. The /eu/claude page lists every current deployment with live prices.

For the r/LLMDevs developer at 2.5M tokens a day: keep your Bedrock account and add it as a BYOK key, then build a fallback policy that starts with your own Frankfurt quota and continues through Ireland, Stockholm, Paris and Vertex. Your daily ceiling becomes the sum of the pools rather than the smallest one, the privacy properties hold on every hop, and you can watch which region served each request in the logs.

The takeaway

Claude has no EU region at Anthropic, but it has 47 in the clouds, and the quota problem that stops small teams is a single region problem. Treat regions as pools, chain them in a fallback policy that is EU only by construction, enforce it with an approved models list and ZDR, and the 429 stops being an architecture decision. The /eu page has the endpoint; the EU routing docs have the copy paste.