Elevated errors creating apps and managing secrets
Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.
The latest update from Fly.io.
State
Resolved
Started
17 d ago
2026-10-15 09:30 UTC
Lasted
2 h 4 min
until 2026-10-15 11:33 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
27 min 22%
Monitoring
1 h 36 min 78%
Updates
Times in UTCAs posted by Fly.io
Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.
We’ve applied a fix for the elevated errors affecting app creation and secrets management. Error rates and response times have returned to normal. We’re continuing to monitor to confirm the issue is fully resolved.
We’re seeing elevated error rates and slow responses for some operations that create or change data. Creating new apps, setting or removing secrets, and some app deletions are affected. You may see 500 or 503 errors from `flyctl`, the Machines API, or the dashboard. Apps and Machines that are already running are not affected. Starting, stopping and reading existing Machines are working normally. We’re investigating and will post another update within 30 minutes.
Fly.io in the last 90 days
Full historyIncidents in 90 days
19
Days with an incident
15
Median duration
1 h 38 min
This incident
1.3× the median
Other Fly.io incidents
All incidentsFly.io·Slow image pulls delaying Machine starts in IAD
Image pull times in IAD have returned to normal.
Fly.io·Elevated issues with the Machines API
The incident has been resolved.
Fly.io·Creating WireGuard peers in ARN is currently broken
The ARN WireGuard gateways are up
Fly.io·Degraded networking to AWS IPs
This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.
Fly.io·Packet loss in IAD
The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.
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.cc/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.cc/feed.xml?providers=fly/feed subscribe https://outages.cc/feed.xml?providers=flyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane