Description: Flexera One - Cloud Cost Optimization (CCO) - APAC, NAM & EU- Billing data missing
Timeframe: May 20, 2025, 6:43 PM PST to May 22, 2025, 8:00 PM PST
Incident Summary
On Tuesday, May 20 at 6:43 PM PST, the Cloud Cost Optimization (CCO) platform began experiencing issues that impacted some customers, primarily in the APAC region. While the platform itself remained accessible, affected users noticed missing billing and cost data, along with disruptions to related optimizations.
The issue was detected early by internal monitoring and triaged promptly. Initial investigations pointed to a recent update deployed to the analytics database import process earlier that day. Although the platform's core functionality was unaffected, the absence of accurate data rendered some features ineffective for customers.
Root Cause
The root cause of the incident was a flaw introduced in a recent update to the analytics database import process. The update led to incomplete or missing data for some customer organizations after the scheduled import jobs. Because imports occur on a delayed cycle, the issue was not immediately visible during post-deployment testing.
This uncovered a gap in testing coverage related to the lack of validations that occur after an analytics database import has been run.
Remediation Actions
· Fix Deployment: A corrective update was developed and deployed by May 20 at 9:09 PM PST to address the faulty analytics database import process.
· Manual Data Imports: Teams initiated manual analytics database imports to expedite data correction for all affected organizations.
· Regional Validation Completion: By May 21 at 1:44 AM PST, APAC and EU region data validations were completed, confirming service restoration in those regions.
· NAM Region Follow-up: The team shifted focus to the NAM region, resolving most cases by May 21 at 10:48 AM PST, with only a few remaining.
· Ongoing Monitoring: On May 21 at 3:13 PM PST, all NAM organizations were successfully processed and the incident was moved to the Monitoring phase.
· Final Resolution Confirmation: On May 22 at 8:00 AM PST, full service restore was confirmed post extended monitoring .
Remediation Actions
· Fix Deployment: A corrective update was developed and deployed by May 20 at 9:09 PM PST to address the faulty analytics database import process.
· Manual Data Imports: Teams initiated manual data imports to expedite data correction for all affected organizations.
· Regional Validation Completion: By May 21 at 1:44 AM PST, APAC and EU region data validations were completed, confirming service restoration in those areas.
· NAM Region Follow-up: The team shifted focus to the NAM region, resolving most cases by May 21 at 10:48 AM PST, with only a few remaining.
· Ongoing Monitoring: On May 21 at 3:13 PM PST, all NAM organizations were successfully processed the incident was moved to the Monitoring phase.
· Final Resolution Confirmation: On May 22 at 8:00 AM PST, full service restore was confirmed post extended monitoring .