Fly.io incident

Deploys defaulting to Fly-hosted Builders

Minor Resolved View vendor source →

Fly.io experienced a minor incident on June 25, 2026 affecting Deployments, lasting 1h 56m. The incident has been resolved; the full update timeline is below.

Started
Jun 25, 2026, 01:41 PM UTC
Resolved
Jun 25, 2026, 03:38 PM UTC
Duration
1h 56m
Detected by Pingoru
Jun 25, 2026, 01:41 PM UTC

Affected components

Deployments

Update timeline

  1. investigating Jun 25, 2026, 01:41 PM UTC

    We are investigating delays provisioning Depot backed builders for deploys. We have switched the default `fly deploy` strategy to use fly hosted builders at this time. Users can still trigger a depot based deploy with `fly deploy --depot=true`

  2. monitoring Jun 25, 2026, 03:08 PM UTC

    We are seeing improvements in Depot builder provision times and are switching the default deploy strategy back to them. We will continue to monitor builder performance closely. Users with a preference can trigger a Fly builder based deploy with `fly deploy --depot=false` or use `fly deploy --depot=true` to force a depot-based deployment.

  3. resolved Jun 25, 2026, 03:38 PM UTC

    This incident has been resolved.