Fly.io experienced a ~1-hour incident where Depot builders in the IAD region failed or timed out when starting builds via `fly deploy`, affecting Deployments and Remote Builds. A fix was implemented and monitored before the incident was fully resolved. Workarounds included using `fly deploy --depot=false` or switching the builder region to DFW or ORD via the Fly dashboard.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
This incident has been resolved.
A fix has been implemented and we are seeing improvements in builder performance, latency, and error rates. We are continuing to monitor for a full recovery.
Customers still seeing issues can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`.
We have identified an issue causing delays or failures when starting depoting builders located in the IAD region. Customers with builders in IAD may see delays or timeouts starting builds during `fly deploy`. We are working on a fix.
In the meantime customers can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`. You can also change your builder region away from IAD via the `settings` tab of your Fly dashboard. We recommend DFW or ORD as alternate builder regions at this time.
Please note, your builder region can differ from the region your machines are in.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with