Knowledge BaseGetting StartedChoosing the right region for your workload

Choosing the right region for your workload

Getting Started 3 min read Updated March 2026

Region choice drives user-perceived latency. Pick closest-to-your-users, not closest-to-you.

Available regions

  • nyc1 — New York, USA (East-coast US / EU-latency-tolerant)
  • sfo1 — San Jose, USA (West-coast US / LATAM)
  • fra1 — Frankfurt, Germany (Central EU)
  • lon1 — London, UK (UK + West EU)
  • sgp1 — Singapore (SEA, India, ANZ)
  • tyo1 — Tokyo, Japan (Japan, Korea, China-edge)
  • dxb1 — Dubai, UAE (MENA, South Asia)
  • syd1 — Sydney, Australia (ANZ)

Decision rules

  • > 70% users in one region? Put compute there, CDN handles the rest.
  • Global audience? Multi-region with anycast DNS or CDN at the edge.
  • Regulatory: EU users → Frankfurt or London (GDPR). Healthcare USA → NY or SJ.

Was this article helpful?

Still stuck?

Our team answers tickets 24/7. Median first response: 15 minutes.

Orvoxa — White-Label Reseller Hosting Platform