Live / Incidents / Flexera
Flexera: Spot Ocean for AWS - Service Disruption
Flexera · flexera.comImpact: majorResolved2026-09-24 22:16 UTC
Public — what happened
Summary
Further investigation determined that a recent change affecting instance provisioning behavior contributed to the issue. Technical teams completed a rollback of the change and validated recovery. Following the rollback, error levels returned to normal and new instance provisioning resumed successfully.
Throughout the incident, existing instances and workloads remained operational. The impact was limited to new instance launches and cluster scale-up operations.
The issue is now considered resolved. A detailed post-mortem report will be shared following completion of the root cause analysis and post-incident review, documenting the full sequence of events, contributing factors, lessons learn
Timeline
- Started — 2026-09-24 21:43 UTC
- Last update — 2026-09-24 22:16 UTC
- Resolved — 2026-09-24 22:16 UTC
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 →