Skip to content
Where To DeployDrawn at2 vCPU · 4 GB · 100 GB egressCompare

Region filter

Cloud region eligibility

A region qualifies only when it satisfies hard constraints. Price ranking happens after residency, latency, service, and failure-domain requirements pass.

Standing answer

For an EU-resident workload serving central Europe, start with EU Central and EU West candidates. Measure latency from actual users before choosing between them, then confirm every required managed service exists in the same region.

Eligibility filter

Residency before price

The default assumes EU data residency, users in central Europe, and a 100 ms application round trip.

Qualifying starting setEU Central and EU West
EU CentralQualifies

EU Central passes this starting filter. Measure the real provider and dependency path against the 100 ms target.

EU WestQualifies

EU West passes this starting filter. Measure the real provider and dependency path against the 100 ms target.

US EastDoes not qualify

US East is outside the European Union residency requirement.

Asia PacificDoes not qualify

Asia Pacific is outside the European Union residency requirement.

These three filters are switched off, not merely dimmed. Nothing here can recompute without JavaScript, so they are disabled in the HTML and cannot be changed by a pointer or by a keyboard. The eligibility result below is the complete answer forEuropean Union residency, users in central Europe, and a 100 ms target round trip, already in this page, including the reason each region passes or fails.

Receipt

Formula: residency passes ∧ service set passes ∧ latency target passes ∧ failure boundary passes

Assumptions: provider region labels are only a candidate filter; measured latency is required.

Unknowns: account capacity, service-by-service availability, and real-user latency.

Freshness: regional decision rules reviewed 2026-07-25.

Decision test

What changes the answer

  1. 01Residency is a hard filter when law or contract requires it.
  2. 02Latency is measured from users and dependencies, not inferred from a map alone.
  3. 03A compute region is insufficient if the database or object store must cross regions.
  4. 04Multi-region recovery changes transfer, storage, and operations cost.

Shareable result receipt

Fixed for this page: the same formula, assumptions and sources every visitor sees.

For an EU-resident workload serving central Europe, start with EU Central and EU West candidates. Measure latency from actual users before choosing between them, then confirm every required managed service exists in the same region.

Formula

Qualifying region = residency passes ∧ service set passes ∧ latency target passes ∧ failure boundary passes

Assumptions

  • Central European user midpoint
  • One primary region
  • Published provider region list

Explicit unknowns

  • Real user latency
  • Account-specific capacity
  • Service-by-service regional availability

Sources and freshness