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

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Fly.io status & history page.

Related: Fly.io status & history. SquidGrid is not affiliated with Fly.io.