Depot builder failures

What to do

• Check whether you use Fly.io Deployments. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 43m it lasted.

  Anything that failed between 2026-09-15 04:08 UTC and 2026-09-15 04:51 UTC may need a replay.

• Subscribe to Fly.io's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=fly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Fly.io 4

1. investigatingSep 15, 2026, 4:08 AM UTC

   We are investigating reports of Depot builds failing for some customers. Affected customers can deploy successfully using the --depot=false or --buildkit arguments to flyctl.

   provider

2. identifiedSep 15, 2026, 4:45 AM UTC

   We have identified an issue with deploying via Depot for users connecting through our SYD and JNB regions. Affected customers in these regions can deploy successfully using the --depot=false or --buildkit arguments to flyctl.

   provider

3. monitoringSep 15, 2026, 4:51 AM UTC

   A fix has been implemented and we are monitoring builds. Standard flyctl builds should be working again for customers in all regions.

   provider

4. resolvedSep 15, 2026, 5:34 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.