Skip to content
OutageDeck

Incident detail

Deploys defaulting to Fly-hosted Builders

Resolved incidentMinor1 affected service

Timeline window

to

Outage alerts

Get alerted the next time Fly.io breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Fly.io alerts work

Timeline

Incident updates

Every update Fly.io posted, oldest to newest, exactly as it appeared on their official status page.

  1. 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`

  2. 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.

  3. Resolved

    This incident has been resolved.

Keep exploring

More from Fly.io

Neighboring incidents on Fly.io's timeline and the rest of their record on OutageDeck.

← Older incident

Elevated control plane latency

Newer incident →

IPv6 Connectivity Issues in EWR

All Fly.io incidentsFly.io live status