Live / Fly.io / Incident
Fly.io: Elevated issues with the Machines API
Fly.io · fly.ioMinor incidentResolved2026-10-29 21:28 UTC
Public — what happened
Summary
Fly.io said it was looking into degraded performance of its Machines API starting at 20:40 UTC on 2026-10-29, and labeled the incident minor. Nine minutes later the company said it had found the problem and was working on a fix, and it posted a further update at 21:19 UTC saying that work was continuing. The incident was marked resolved at 21:28 UTC. Fly.io did not say in its updates who was affected or what the problem was.
Timeline
- Started — 2026-10-29 20:40 UTC
- Investigating — 2026-10-29 20:40 UTC
- Identified — 2026-10-29 20:49 UTC (2 updates)
- Resolved — 2026-10-29 21:28 UTC · 48 min 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 45, 2026, our weekly internet health report.