Emergency maintenance in GRU
Fly.io reports a partial outage in GRU during emergency maintenance. Fly.io says affected hosts and the machines and MPG clusters on them are back online. The incident is resolved and lasted 14 minutes.
State
Resolved
Started
Lasted
14 min
Worst impact
Partial outage
Timeline
2 updatesMonitoring
14 min 100%
Updates
Times in UTCAs posted by Fly.io
Affected hosts and the machines and MPG clusters running on them are back online.
Affected hosts are coming back online. We are monitoring the impact.
Fly.io in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
23
Median duration
1 h 28 min
This incident
84% shorter than the median
Other Fly.io incidents
All incidentsFly.io·GitHub connections reset - sign in with GitHub again to restore GitHub deploys
Fly.io reset all connections between Fly.io accounts and GitHub. Automatic deploys on push, and launching or redeploying an app from a GitHub repository in the dashboard, failed. The incident is resolved and lasted 3 hours 37 minutes. Sign in to Fly.io with GitHub again to restore GitHub deploys.
Fly.io·LAX region outage
A subset of Apps and Managed Postgres clusters in the LAX region did not work. Fly.io reported an upstream datacenter power outage as the cause. Fly.io resolved the incident after 2891 minutes.
Fly.io·IPv6 egress issues on a subset of IAD hosts
IPv6 egress did not work on a subset of IAD hosts in Fly.io. The issue came from an upstream provider. Fly.io reported that the incident is resolved and that all affected hosts are back to normal. The incident lasted 22 minutes.
Fly.io·Emergency network maintenance on a subset of hosts in ORD
Fly.io reports that some machines in ORD were unreachable. A small subset of MPG clusters ran with reduced HA. Fly.io says the incident is resolved and the affected hosts are back online. The incident lasted about 14 minutes.
Fly.io·Elevated Machine start failures in ARN
Fly.io reported elevated Machine start failures in the ARN region. Fly.io fixed the problem and reports that the incident is resolved. The incident lasted 61 minutes.
Follow Fly.io
Your coding agent knows when Fly.io is down, and tells you when a failure is theirs, not yours. You can also get Fly.io incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fly" and tell me if Fly.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=fly/feed subscribe https://outages.live/feed.xml?providers=flyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane