Live / Fly.io / Incident
Fly.io: Elevated Machine start failures in ARN
Fly.io · fly.ioMinor incidentResolved2026-11-02 13:35 UTC
Public — what happened
Summary
Fly.io said it was looking into a higher-than-normal number of failures when starting Machines in its ARN region, and it rated the incident as minor. The company reported that it began at 12:34 UTC on 2026-11-02. It suggested that affected users could work around the problem by cloning the affected Machine to create a replacement. The incident is now marked resolved as of 13:35, though the text provided does not state a cause.
Timeline
- Started — 2026-11-02 12:34 UTC
- Investigating — 2026-11-02 12:34 UTC
- Resolved — 2026-11-02 13:35 UTC · 1h 01m 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 46, 2026, our weekly internet health report.