outages.live
Live
Fly.ioIncident · 2026-10-30 20:24 UTC

Slow image pulls delaying Machine starts in IAD

ResolvedOfficial update

Image pull times in IAD have returned to normal.

The latest update from Fly.io.

State

Resolved

Started

1 d ago

2026-10-30 20:24 UTC

Lasted

1 h 28 min

until 2026-10-30 21:52 UTC

Worst impact

Degraded

Timeline

4 updates
20:2420:4621:0821:3021:52
DegradedUpdate postedTimes in UTC

Investigating

43 min 49%

Identified

15 min 17%

Monitoring

30 min 34%

Updates

Times in UTC

As posted by Fly.io

Resolved2026-10-30 21:52 UTC

Image pull times in IAD have returned to normal.

Monitoring2026-10-30 21:23 UTC

We have implemented a fix and are monitoring results.

Identified2026-10-30 21:07 UTC

We have identified the cause of the issue and are working on a fix.

Investigating2026-10-30 20:24 UTC

We are investigating slow image pulls within Fly Machines in IAD. Newly created or updated Machines are taking longer to start, which may cause deployments to time out. Machines start successfully after the delay. Consider creating Machines in alternate regions, if possible, or running `fly deploy --wait-timeout 10m` to give Machines up to 10 minutes to prepare images and start.

Fly.io in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

19

Days with an incident

15

Median duration

1 h 38 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 h 53 min
median 1 h 38 min
90 days agoToday

Other Fly.io incidents

All incidents

Fly.io·Elevated issues with the Machines API

The incident has been resolved.

Resolvedresolved 2 d ago

Fly.io·Creating WireGuard peers in ARN is currently broken

The ARN WireGuard gateways are up

Resolvedresolved 3 d ago

Fly.io·Degraded networking to AWS IPs

This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.

Resolvedresolved 5 d ago

Fly.io·Packet loss in IAD

The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.

Resolvedresolved 6 d ago

Fly.io·MPGv2 IAD control plane is read-only

Control plane operations in IAD, including resizing and changing plans, are working normally again.

Resolvedresolved 7 d ago

Follow Fly.io

Your coding agent knows when Fly.io is down, and tells you when a failure is theirs, not yours. You can also get Fly.io incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fly" and tell me if Fly.io has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=fly
Slack
/feed subscribe https://outages.cc/feed.xml?providers=fly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane