major✓ Resolved

flyctl deploy timeouts

Fly.io•2026-02-17 13:06 UTC

Status

resolved

Duration

1h 24m

Updates

Coverage

0 articles

INCIDENT TIMELINE

✓ Resolved2026-02-17 14:30 UTC

This incident has been resolved.

monitoring2026-02-17 13:42 UTC

A fix has been implemented and we are monitoring the results.

identified2026-02-17 13:06 UTC

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

🕐 First reported

2026-02-17 13:06 UTC

🔄 Last Updated

2026-02-17 14:30 UTC

✓ Resolved

2026-02-17 14:30 UTC

MAJOR

Impact Level

1h 24m

Total Duration

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