Flightcontrol incident

Capacity isssues in iad and dfw

Resolved after 5 hours 27 minutes, affecting Management Plane - IAD and Remote Builds and 1 more, on February 26, 2026.

monitoring Feb 26, 2026, 08:19 PM UTC

We're continuing to monitor after having added more capacity to our DFW and IAD regions. Deploys or machine starts using existing volumes in these regions may still hit a capacity issue. Users should use `fly volume fork --vm-memory ` to fork the volume to a host with more capacity, then retry the deploy or start command using the new volume.

Started
Feb 26, 2026, 05:00 PM UTC
Resolved
Feb 26, 2026, 10:28 PM UTC
Duration
5h 27m
Detected by Pingoru
Feb 26, 2026, 05:00 PM UTC

Affected components

Management Plane - IADRemote BuildsDFW - Dallas, Texas (US)IAD - Ashburn, Virginia (US)

Update timeline

  1. identified Feb 26, 2026, 05:00 PM UTC

    We have identified the problem and are working on a fix.

  2. identified Feb 26, 2026, 05:05 PM UTC

    New machine creates in these regions might fail temporarily, and Depot builders may be unavailable. If you are having issues with Depot builders, consider moving them to a different region, or try `--depot=false`.

  3. identified Feb 26, 2026, 05:18 PM UTC

    We've identified some newly created Managed Postgres clusters are failing to come up healthy in these regions.

  4. identified Feb 26, 2026, 06:57 PM UTC

    We have added additional capacity in DFW and IAD regions and are monitoring the impact. New machine creates and deploys without volumes are seeing improved success rates. Deploys using depot builders in those regions are also improving, with much quicker builder start times. Deploys or machine starts using existing volumes in these regions may still hit a capacity issue. Users should use `fly volume fork --vm-memory ` to fork the volume to a host with more capacity, then retry the deploy or start command using the new volume.

  5. monitoring Feb 26, 2026, 08:19 PM UTC

    We're continuing to monitor after having added more capacity to our DFW and IAD regions. Deploys or machine starts using existing volumes in these regions may still hit a capacity issue. Users should use `fly volume fork --vm-memory ` to fork the volume to a host with more capacity, then retry the deploy or start command using the new volume.

  6. resolved Feb 26, 2026, 10:28 PM UTC

    This incident has been resolved.

Your product runs on more than Flightcontrol

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 →