Fly.io incident

Low capacity in IAD

Resolved after 3 hours 42 minutes, affecting Deployments and IAD - Ashburn, Virginia (US), on March 27, 2026.

monitoring Mar 27, 2026, 09:09 PM UTC

With the additional capacity we've brought online, machine start failure rates in IAD have now recovered. We'll continue to monitor IAD capacity.

Started
Mar 27, 2026, 06:08 PM UTC
Resolved
Mar 27, 2026, 09:51 PM UTC
Duration
3h 42m
Detected by Pingoru
Mar 27, 2026, 06:08 PM UTC

Affected components

DeploymentsIAD - Ashburn, Virginia (US)

Update timeline

  1. investigating Mar 27, 2026, 06:08 PM UTC

    We're currently investigating capacity issues in IAD that is preventing machine starts (machine creates are currently unaffected). This may result in deploys failing to complete (even for apps outside of the IAD region). As a workaround, using legacy Fly builders explicitly located in another region (i.e., `FLY_REMOTE_BUILDER_REGION=lhr fly deploy --depot=false --recreate-builder`) may help in the meantime.

  2. investigating Mar 27, 2026, 06:47 PM UTC

    We're continuing to evaluate our options for increasing short-term capacity in the IAD region.

  3. identified Mar 27, 2026, 07:21 PM UTC

    We've brought some additional capacity online in IAD and are seeing improvements, and we're continuing to work on adding more and freeing up additional room.

  4. monitoring Mar 27, 2026, 09:09 PM UTC

    With the additional capacity we've brought online, machine start failure rates in IAD have now recovered. We'll continue to monitor IAD capacity.

  5. resolved Mar 27, 2026, 09:51 PM UTC

    This incident has been resolved.

Your product runs on more than Fly.io

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →