Fly.ioAnnouncement
The Region Consolidation Project
Summary
Fly.io is consolidating its region map and deprecating 17 regions across North America, Europe, Asia-Pacific, South America, and Africa. The announcement lists 17 deprecated locations, including Madrid, Bucharest, Warsaw, Atlanta, Boston, Denver, Guadalajara, Miami, Phoenix, Querétaro, Seattle, Montreal, Bogotá, Ezeiza, Rio de Janeiro, Santiago, and Hong Kong, and names 18 consolidated regions: seven in North America, five in Europe, four in Asia-Pacific, and one each in South America and Africa. For apps migrated by Fly.io, most moves should be seamless, although applications with region-specific logic must be updated to use the new region. Manual moves generally require changing primary_region in fly.toml, scaling up in the destination with fly scale count, and scaling down in the original region. If volumes are involved, the guidance recommends stopping existing machines, forking volumes into the new region, and creating machines from those forks; support is offered for issues that arise.
Context
Fly.io is changing its region map through a consolidation and deprecation plan. The post explains which existing regions are being deprecated and recommends new regions for migration.
Approach / What changed
Apps can be migrated by Fly.io or moved manually. Manual migration involves updating primary_region in fly.toml, scaling up with fly scale count in the new region, and scaling down in the original region. Volume-backed apps may require stopping machines, forking volumes into the new region, and creating machines from the forked volumes.
Takeaways
The deprecated list contains 17 regions, while the consolidated map contains 18 regions: seven in North America, five in Europe, four in Asia-Pacific, and one each in South America and Africa.
Applications with region-specific logic need code changes to reference the consolidated region, whether Fly.io performs the migration or the application owner does it manually.
For apps using volumes, the recommended process includes stopping existing machines, forking volumes into the destination region, and creating new machines from those forks.
Source and freshness
- Source
- fly.io
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.