Resolved after 1 hour 56 minutes, affecting Deployments, on June 25, 2026.
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.
Affected components
Update timeline
- 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`
- 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.
- resolved Jun 25, 2026, 03:38 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.
Amazon Web Services