Description: Flexera One - Cloud Cost Optimization (CCO) - North America - Service Degradation Affecting Certain Functionality

Timeframe: August 11, 2026, 9:51 AM PDT – August 11, 2026, 10:45 AM PDT

Incident Summary

On August 11, 2026, customers may have experienced issues accessing certain Cloud Cost Optimization (CCO) functionality in the North America region. Impacted pages could remain in a continuous loading state and fail to render correctly.

Technical teams began investigating after identifying that certain application requests were not completing successfully. The impact was limited to specific functionality rather than the entire CCO service.

During the investigation, technical teams determined that dependent application services were unable to successfully retrieve required configuration information from a supporting service component, resulting in rendering issues for affected functionality.

Corrective configuration changes were implemented and updated service components were deployed. Following deployment, technical teams validated recovery and continued monitoring the environment to confirm stable operation. All affected functionality subsequently returned to normal operation.

Root Cause

During a recent service migration, a supporting application component was deployed with an incorrect resource configuration. As processing demand increased, the affected service components exhausted available resources and became unavailable.

As a result, dependent application services were unable to successfully retrieve required configuration information needed to process certain requests. This resulted in rendering issues affecting specific Cloud Cost Optimization (CCO) functionality.

Remediation Actions

The following actions were taken during the incident response:

1. Incident Investigation Initiated: Technical teams investigated reports of affected CCO functionality remaining in a continuous loading state and failing to render correctly.
2. Service Dependency Analysis Performed: Technical teams identified that dependent application services were unable to successfully retrieve required configuration information from a supporting service component.
3. Configuration Issue Identified: Investigation determined that a supporting application component had been deployed with an incorrect resource configuration following a recent service migration.
4. Corrective Configuration Changes Applied: Technical teams implemented configuration changes to restore the intended operating parameters for the affected service components.
5. Service Recovery Validation Performed: Updated service components were deployed, affected functionality was validated, and the environment was monitored to confirm stable operation before incident closure.

Future Preventative Measures

Following this incident, technical teams reviewed the migration and deployment process associated with the affected service component.

1. Configuration Validation Enhancements: An additional validation step has been added to verify that service configurations are appropriate for forecasted processing requirements following migration activities. This additional review is intended to help identify configuration discrepancies before they can affect production workloads.