Flexera- Spot- US east- 1- Service Degradation (Instance Launch Failures)

Description: Flexera- Spot- US east- 1a- Database connection and low request issues

Timeframe: May 7, 2026, 4:25 PM PST to May 8, 2026, 7:04 PM PST

‌

Incident Summary

‌

On May 7, 2026, Flexera identified a service degradation impacting Spot services in the US East 1a region. During the impact duration, customers experienced difficulties launching instances. In addition, some backend services experienced reduced request handling capacity and intermittent database connectivity issues, resulting in degraded provisioning behavior and delayed scaling operations.

Initial investigation determined that the issue coincided with a broader disruption affecting an external cloud infrastructure provider. The external disruption introduced elevated latency and intermittent service instability across dependent infrastructure components, which contributed to degraded provisioning and backend service performance within the Spot platform.

During the investigation, engineering teams also identified a database issue caused by the service provider outage that posed a potential performance risk under degraded infrastructure conditions. The issue was mitigated early in the response process, and system stability improved following remediation actions.

Throughout the incident, technical teams continuously monitored service health, validated provisioning behavior, and assessed mitigation options to minimize customer impact while the external provider disruption remained active. Over several hours following mitigation, Spot services remained stable with no recurrence of customer-facing issues observed.

After an extended monitoring period confirmed continued stability, the incident was considered resolved following confirmation that the underlying external provider disruption had been fully remediated on May 8, 2026, at 7:04 PM PST.

‌

Root Cause

‌

The issue was primarily caused by a disruption affecting an external cloud infrastructure provider supporting services in the US East 1a region. The disruption resulted in increased latency, intermittent connectivity issues, and degraded infrastructure performance, which impacted Spot instance provisioning operations and related backend services.

Contributing Factors:

• Elevated latency and intermittent failures across dependent infrastructure services increased provisioning delays and request instability.
• A database performance issue, triggered by the underlying service provider disruption, introduced additional load under degraded infrastructure conditions and increased the risk of intermittent service instability.
• The prolonged nature of the external provider disruption extended the duration of customer impact and required continuous monitoring and mitigation activities.

‌

Remediation Actions

‌

The following remediation steps were implemented to restore service functionality:

• Investigated and monitored infrastructure and provisioning service behavior across impacted Spot components.
• Identified and mitigated a database performance degradation contributing to elevated performance risk.
• Validated provisioning stability and backend service recovery following mitigation efforts.
• Performed extended monitoring to ensure sustained service stability and confirm the absence of recurring customer impact.

‌

Future Preventative Measures

‌

• Alerting Reliability Improvements: Improve alert delivery validation and monitoring to ensure critical database alerts are consistently propagated across all operational notification channels, including collaboration and incident management platforms.
• Regional Resilience Evaluation: Evaluate additional regional resilience and failover capabilities to reduce the impact scope of regional infrastructure disruptions. Any future implementation will be subject to cost-impact analysis and internal approval processes.
• Third-Party Provider Escalation Process: Enhance operational procedures for third-party infrastructure incidents by establishing earlier escalation and engagement processes with external cloud service providers during active service disruptions.