Fly.io: Slow image pulls delaying Machine starts in IAD
Affected components: IAD - Ashburn, Virginia (US)Deployments
Timeline of updates
- investigating
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.
- identified
We have identified the cause of the issue and are working on a fix.
- monitoring
We have implemented a fix and are monitoring results.
- resolved
Image pull times in IAD have returned to normal.
Changes Rewindex caught on this incident
- Incident updated: Slow image pulls delaying Machine starts in IAD
- Incident updated: Slow image pulls delaying Machine starts in IAD
- Incident updated: Slow image pulls delaying Machine starts in IAD
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0ead7678a284d27e…Version 2 captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
43185ebf4c83ae66…Version 3 captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
741b94fc500e95ab…Version 4 captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c3dfcc41dbfc8614…
Impact, status and times are the vendor’s own, as last archived. View on status.flyio.net (opens in new tab).