Flightcontrol incident

Deploys hanging at waiting for Depot Builder

Minor Resolved View vendor source →

Flightcontrol experienced a minor incident on February 20, 2026 affecting Deployments, lasting 4h 35m. The incident has been resolved; the full update timeline is below.

Started
Feb 20, 2026, 04:14 PM UTC
Resolved
Feb 20, 2026, 08:49 PM UTC
Duration
4h 35m
Detected by Pingoru
Feb 20, 2026, 04:14 PM UTC

Affected components

Deployments

Update timeline

  1. monitoring Feb 20, 2026, 04:14 PM UTC

    We have seen elevated latency provisioning Depot builders during deployments over the past hour. This caused some deploys to hang or timeout at the "Waiting for Depot Builder" step in this period. Latency has improved and builder provision times are back to normal. We're continuing to monitor to ensure latency remains normal.

  2. identified Feb 20, 2026, 04:39 PM UTC

    We are again seeing elevated latency provisioning depot builders on new deploys. Users may see deploys using Depot builders hang or timeout at the "Waiting for Depot Builder" step. We are working on a fix. We are switching all deploys to use the default Fly builders in the meantime. If desired users can manually switch back to depot builders using `fly deploy --depot=true` but may continue to see latency issues at this time.

  3. identified Feb 20, 2026, 05:59 PM UTC

    A fix is being rolled out. Fly builders continue to be the default while this is deployed

  4. monitoring Feb 20, 2026, 07:38 PM UTC

    The fix has been rolled out and we are seeing deploys using depot builder succeeding normally. We continue to monitor to ensure full recovery. Depot builders have been reenabled as the default option for new deploys

  5. resolved Feb 20, 2026, 08:49 PM UTC

    This incident has been resolved.