Capacity issues in GRU region
DegradedWe have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal.
Fly.io is up and running. Fly.io runs apps on virtual machines close to users around the world.
Worked out from the incidents Fly.io reported, so it is an estimate and not a measurement.
Last incident: “Capacity issues in GRU region”, today.
We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal.
The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance is now fully reachable.
All host restarts have been completed and the platform is operating normally. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see further updates on the personalized status page viewable at
Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.
Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes
Fly.io’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Fly.io reported was “Capacity issues in GRU region”, today (2026-10-20 16:54 UTC). Its last full outage started 4 days ago.
Fly.io reports 25 components on its status page, including Customer Applications, Dashboard, Machines API, AMS - Amsterdam, Netherlands, ARN - Stockholm, Sweden. Each is checked again whenever this page refreshes.
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
Deploys go through remote builders and the Machines API, both separate from running machines and the Anycast edge. A stuck deploy does not interrupt traffic.
Each edge region (IAD, FRA, NRT…) is its own component. Run `fly status` on your app to see which regions its machines run in.
If the status above is operational but Fly.io still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.