Live / Flexera / Incident
Flexera: Spot - AWS - Service Disruption
Flexera · flexera.comCritical outageResolved2026-10-29 23:38 UTC
Public — what happened
Summary
Flexera reported a critical disruption starting at 21:37 UTC on 2026-10-29 that affected Spot's handling of AWS-related tasks. The company said customers could see failures or delays when ending instances, scaling, managing capacity, or creating Elastigroups, and that some ECS clusters did not appear during import. Flexera said its teams found connectivity timeouts and responded by adding resources and changing health-check settings, after which responsiveness improved and key functions such as Elastigroup creation and scaling were confirmed working. The incident was marked resolved at 23:38 UTC.
Affected
Spot UI, Spot API
Timeline
- Started — 2026-10-29 21:37 UTC
- Investigating — 2026-10-29 21:37 UTC (3 updates)
- Resolved — 2026-10-29 23:38 UTC · 2h 01m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Flexera against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Flexera: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Flexera report →
More from Flexera
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.