← Back to Fly.io History
minor✓ Resolved
Deploys defaulting to Fly-hosted Builders
Status
resolved
Duration
1h 58m
Updates
2
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
monitoring
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.
investigating
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`
📊 TECHNICAL DETAILS
Internal ID
3bad9910-c9e2-48cd-b339-03182412666c
External ID
ltkp5s03xr58
🕐 First reported
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
1h 58m
Total Duration
2
Status Updates
Affected Components
Deployments
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed