Affected components
Deployments
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.
Looking to track Flightcontrol downtime and outages?
Pingoru polls Flightcontrol's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Flightcontrol reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Flightcontrol alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
Start monitoring Flightcontrol for free
5 free monitors · No credit card required