Live / Fly.io / Incident
Fly.io: Slow image pulls delaying Machine starts in IAD
Fly.io · fly.ioMinor incidentResolved2026-10-30 21:52 UTC
Public — what happened
Summary
Fly.io said that some Machines in its IAD region were slow to pull images, so new or updated Machines took longer than normal to start. The company said this could cause deployments to time out, though Machines did start successfully after the delay. It began investigating at 20:24 UTC on 2026-10-30 and suggested using another region or a longer deploy wait time as workarounds. The incident was marked resolved at 21:52, and the text provided did not state a cause.
Timeline
- Started — 2026-10-30 20:24 UTC
- Investigating — 2026-10-30 20:24 UTC
- Resolved — 2026-10-30 21:52 UTC · 1h 28m 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.