Live / Fly.io / Incident
Fly.io: Elevated errors creating apps and managing secrets
Fly.io · fly.ioMinor incidentResolved2026-10-15 11:33 UTC
Public — what happened
Summary
Fly.io reported a minor incident beginning at 09:30 UTC on 2026-10-15 in which some actions that create or modify data were failing or running slowly, including making new apps, adding or removing secrets, and certain app deletions. The company said users might get 500 or 503 errors through flyctl, the Machines API, or the dashboard, while apps and Machines already running, along with starting, stopping and viewing existing Machines, kept working as usual. By 09:57 UTC Fly.io said it had put a fix in place and that errors and response times were back to normal, though it did not share a cause. The incident was marked resolved at 11:33.
Timeline
- Started — 2026-10-15 09:30 UTC
- Investigating — 2026-10-15 09:30 UTC
- Monitoring — 2026-10-15 09:57 UTC
- Resolved — 2026-10-15 11:33 UTC · 2h 04m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Fly.io against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Fly.io: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Fly.io report →
More from Fly.io
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.