Region filter
Choose a cloud region
Rule out the regions your residency rule or latency target excludes, then check services and the failure boundary in what remains. Price ranking comes after all four.
Region requirements
EU Central passes this starting filter. Measure the real provider and dependency path against the 100 ms target.
EU West passes this starting filter. Measure the real provider and dependency path against the 100 ms target.
US East is outside the European Union residency requirement.
Asia Pacific is outside the European Union residency requirement.
Turn on JavaScript to change these filters. The result below is for the default inputs: European Union residency, users in central Europe, and a 100 ms round trip, with the reason each region passes or fails.
How this tool works
Region requirements
Residency before price
The default assumes EU data residency, users in central Europe, and a 100 ms application round trip.
How the answer is worked out
Formula: a region band is a starting candidate when your residency rule allows it and its rough round trip to your users is within your target. Service availability and the failure boundary are checked after this, by you.
Assumptions: rough starting round trips of about 20 ms within a region's own area, about 120 ms across the Atlantic, and about 180 ms from any one band to users worldwide. They are a screen, not a measurement; measured latency is required.
Unknowns: account capacity, service-by-service availability, and real-user latency.
Freshness: regional decision rules reviewed 2026-07-25.
Answer for your inputs
For an EU-resident workload serving users in central Europe within 100 ms, start with EU Central and EU West. Measure latency from actual users before choosing, then confirm every managed service you need exists in the same region.
Set to: EU residency · users in central Europe · 100 ms round trip
What changes the answer
What changes the answer
- 01Residency is a hard filter when law or contract requires it.
- 02Latency is measured from users and dependencies, not inferred from a map alone.
- 03A compute region is insufficient if the database or object store must cross regions.
- 04Multi-region recovery changes transfer, storage, and operations cost.
Bill and sources
Every line below is computed from the controls above, so the address bar, this panel and the ranking always show the same result.
For an EU-resident workload serving users in central Europe within 100 ms, start with EU Central and EU West. Measure latency from actual users before choosing, then confirm every managed service you need exists in the same region.
Formula
Starting candidate = residency allows the region ∧ rough round trip to your users ≤ your target; then service set passes ∧ failure boundary passes, checked by you
Assumptions
- Set to: EU residency · users in central Europe · 100 ms round trip
- Rough starting round trips: about 20 ms within a region's own area, about 120 ms across the Atlantic, about 180 ms from one band to users worldwide
- One primary region
- Published provider region list
Explicit unknowns
- Real user latency
- Account-specific capacity
- Service-by-service regional availability