← Back to Fly.io History
major✓ Resolved

flyctl deploy timeouts

Fly.io•Tue, Feb 17, 2026, 01:06 PM
Status
resolved
Duration
1h 24m
Updates
2
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedTue, Feb 17, 2026, 02:30 PM
This incident has been resolved.
monitoringTue, Feb 17, 2026, 01:42 PM
A fix has been implemented and we are monitoring the results.
identifiedTue, Feb 17, 2026, 01:06 PM
We’re investigating elevated 429 errors from flaps causing deployment timeouts. Affected deploys are failing with: ✖ Failed: error waiting for release_command machine XX to finish running: timeout reached waiting for machine's state to change Your machine never reached the state "destroyed".

📊 TECHNICAL DETAILS

Internal ID
624725c4-9bdb-4168-9b3f-6310cc98063b
External ID
mzwwc2mdhgyj
🕐 Started
Tue, Feb 17, 2026, 01:06 PM
🔄 Last Updated
Tue, Feb 17, 2026, 02:30 PM
✓ Resolved
Tue, Feb 17, 2026, 02:30 PM
MAJOR
Impact Level
1h 24m
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 automatically generate one.
0 / 100 requests100 more needed