Regions

Fly.io runs applications physically close to users: in datacenters around the world, on servers we run ourselves. You can deploy apps in regions worldwide, so your users in Tokyo, São Paulo, or Amsterdam connect to the nearest server through our global Anycast network.

​

Fly.io Regions

You can host your apps in any of the following regions.

• Gateway regions: “Gateway” regions also have WireGuard gateways, through which you connect to your organization’s private network.
• MPG regions: “MPG” regions can host Managed Postgres clusters.

​

Discovering your app’s region

View the list of Fly.io regions with fly platform regions. You can see which regions your app is running in with fly status. Fly Volumes and Fly Machines are tied to the region they’re created in. Learn more about Machine placement and regional capacity in this guide. When an application instance is started, the three-letter name for the region it’s running in is stored in the Machine’s FLY_REGION environment variable. This, along with other Runtime Environment information, is visible to your app running on that instance.

​

Related reading

• Scaling to multiple regions Read our guide for making your app resilient and globally distributed.
• Cost Management Find out how region choice, scaling strategy, and app architecture affect your Fly.io bill.
• Machine Placement and Regional Capacity Learn more about how the choice of region (and region capacity) affects where your Machines land.
• Dynamic Request Routing with fly‑replay Check out our guide to routing requests to specific regions or fallbacks using region codes.