Fly.io incident: Depot builder failures

1. resolvedSep 15, 2026, 05:34 UTC

   This incident has been resolved.

2. monitoringSep 15, 2026, 04:51 UTC

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

3. identifiedSep 15, 2026, 04:45 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.

4. investigatingSep 15, 2026, 04:08 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.

What APIStatus.watch saw

• Sep 15, 2026, 04:10 UTCoperational → degraded
• Sep 15, 2026, 04:55 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC

How often does Fly.io have incidents?

Fly.io reported 19 incidents in the last 90 days, 11 of them major or critical. A typical incident lasted 57 min. See Fly.io's uptime and incident history