Live / Fly.io / Incident
Fly.io: Platform Wide Rolling Host Reboots
Fly.io · fly.ioMajor incidentResolved2026-10-17 05:15 UTC
Public — what happened
Summary
Fly.io said it was restarting every host in its fleet in stages for what it called critical maintenance, starting around 16:22 UTC on 2026-10-16. While a host restarted, the Machines, volumes and Managed Postgres cluster instances on it were unavailable for roughly 15 to 20 minutes, and Fly.io warned that apps running on a single machine could see downtime. Its updates reported steady progress, reaching about 85% of hosts by 23:15 UTC, and said Managed Postgres users would likely see more primary-to-standby switchovers. The incident is now marked resolved as of 05:15 UTC on 2026-10-17.
Timeline
- Started — 2026-10-16 16:22 UTC
- Identified — 2026-10-16 16:22 UTC (18 updates)
- Monitoring — 2026-10-17 03:48 UTC
- Resolved — 2026-10-17 05:15 UTC · 12h 53m 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.