Resolved after 1 hour 18 minutes, affecting Deployments, on February 17, 2026.
Earlier today, an issue caused elevated rate limiting and some deployment timeouts. A fix is in place and deployments are back to normal.
Affected components
Update timeline
- identified Feb 17, 2026, 01:06 PM 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".
- monitoring Feb 17, 2026, 01:42 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 17, 2026, 02:24 PM UTC
Earlier today, an issue caused elevated rate limiting and some deployment timeouts. A fix is in place and deployments are back to normal.
Your product runs on more than Fly.io
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services