Flexera One – NAM – Intermittent Service Degradation

Update timeline

1. investigating May 08, 2026, 10:44 PM UTC

   Incident Description: We are investigating a service degradation affecting Flexera One customers in the NAM region. Customers may experience intermittent errors, delayed page loading, or pages remaining in a loading state when accessing certain areas of the application, including Cloud Cost Optimization functionality and Administration > Shared Settings. Some Cloud Cost Optimization customers may also experience delays in cost data processing. Priority: P2 Restoration Activity: Our technical teams are actively investigating and validating the affected areas. We are also monitoring upstream service provider disruptions that may be contributing to the issue. We will continue to monitor service behavior and work toward restoration. We will provide another update as soon as additional information is available.

2. monitoring May 09, 2026, 08:29 AM UTC

   Our technical teams are actively investigating and validating the affected areas while continuing to monitor overall service behavior. Initial findings suggest the issue may have been influenced by a service provider disruption, which has now been resolved. We are continuing to assess any residual impact and closely monitoring the platform to ensure stability. Further updates will be provided as more information becomes available.

3. resolved May 09, 2026, 09:47 AM UTC

   Our technical teams have completed validation of the affected areas and confirmed that services have been fully restored. The platform is now operating normally, and we are continuing to monitor to ensure sustained stability. This issue is considered resolved, and further details will be shared in a post-mortem report.

4. postmortem May 26, 2026, 05:38 AM UTC

   **Description:** Flexera One – Cloud Cost Optimization – NAM – Intermittent Service Degradation and Cost Data Processing Delays **Timeframe:** May 7, 2026, 11:49 PM PDT – May 8, 2026, 8:04 PM PDT **Incident Summary** On May 7, 2026, at approximately 11:49 PM PDT, an issue was identified affecting Flexera One Cloud Cost Optimization customers in the North America region. During the affected period, some customers may have experienced intermittent errors when accessing Cloud Cost Optimization functionality through the Flexera One user interface. Some customers may also have experienced delays in cost data processing. The issue was identified through internal technical observations, including increased Cloud Cost Optimization cost API request failures and data processing delays, rather than through widespread customer reports. The incident was initially investigated as a broader Flexera One service degradation because intermittent loading behavior was being reviewed across multiple areas of the platform during the same period. As a precaution, additional components were included in the initial customer communications while technical teams validated the affected areas and determined whether the reported behaviors were related to the same underlying service provider disruption. Further investigation confirmed that the service provider disruption was associated with the Cloud Cost Optimization impact described in this report. Other service behavior reviewed during the investigation was determined to be separate from the service provider disruption and was handled through separate investigation and tracking. Technical teams continued monitoring Cloud Cost Optimization service behavior while the upstream disruption was being addressed. After the service provider disruption was resolved, technical teams validated Cloud Cost Optimization functionality and confirmed that services had recovered. By May 8, 2026, at approximately 8:04 PM PDT, the incident was considered resolved. **Root Cause** The incident was caused by a disruption affecting an upstream service provider. As a result, Cloud Cost Optimization experienced intermittent cost API request failures and data processing delays in the North America region. **Remediation Actions** The following actions were taken during the incident response: 1. **Incident Investigation Initiated:** Technical teams began investigating intermittent errors and cost data processing delays affecting Cloud Cost Optimization customers in the North America region. 2. **Internal Observations Reviewed:** Technical teams reviewed internal observations, including increased Cloud Cost Optimization cost API request failures and data processing delays. 3. **Initial Scope Reviewed:** Because intermittent loading behavior was being reviewed across multiple areas of Flexera One during the same period, the incident was initially assessed as a broader platform service degradation. 4. **Customer Communications Posted:** Additional components were included in the initial customer communications as a precaution while technical teams validated the confirmed scope of impact. 5. **Service Provider Disruption Identified:** Technical teams determined that the confirmed Cloud Cost Optimization impact was associated with an upstream service provider disruption. 6. **Impact Assessment Performed:** Technical teams assessed Cloud Cost Optimization API request behavior, Flexera One user interface behavior, and cost data processing delays. 7. **Additional Service Behavior Reviewed:** Additional service behavior reported during the same period was reviewed to determine whether it was related to the same service provider disruption. This behavior was determined to be separate from the service provider disruption and was handled through separate investigation and tracking. 8. **Monitoring Continued:** Technical teams continued monitoring Cloud Cost Optimization service behavior while the upstream service provider disruption was being addressed. 9. **Recovery Validated:** After the upstream service provider disruption was resolved, technical teams validated Cloud Cost Optimization functionality and confirmed recovery before resolving the incident. **Future Preventative Measures** This incident highlighted the importance of continued validation when multiple service behaviors are reported during a broader upstream service provider disruption. Based on the investigation, the following follow-up activity has been identified: 1. **Incident Triage and Component Validation Review:** We will review how related service reports are assessed during broad upstream service provider disruptions to ensure affected components are validated and updated as additional information becomes available. This includes continuing to refine triage practices so customer communications remain aligned with the confirmed scope of impact.