Flexera One – IT Visibility & CLM – Reporting Unavailable Across All Regions

Update timeline

1. investigating Dec 17, 2025, 02:14 PM UTC

   Incident Description: We have identified a service disruption impacting Flexera One IT Visibility (ITV) and Cloud License Management (CLM) across all regions. Customers may experience difficulty accessing certain reports at this time. Priority: P2 Restoration Activity: Our technical teams are actively investigating the issue and working to restore reporting availability. Progress is being closely monitored, and further updates will be provided as additional information becomes available.

2. identified Dec 17, 2025, 04:33 PM UTC

   We have identified that this issue is related to a recent change affecting reporting functionality for Flexera One IT Visibility (ITV) and Cloud License Management (CLM). Our teams are actively implementing corrective updates across regions to restore access to reports. Recovery is progressing region by region, and customers may begin to see reports restored as updates complete. We will continue to monitor progress closely and provide further updates as restoration continues.

3. identified Dec 17, 2025, 07:49 PM UTC

   Corrective actions have been implemented for NA and APAC, and reporting functionality is showing signs of recovery in these regions as validation continues. Work is still underway in the EU region, and teams remain actively focused on implementing remaining measures and confirming full restoration. We will continue to monitor closely and provide further updates as recovery progresses.

4. identified Dec 17, 2025, 08:12 PM UTC

   Reporting functionality has been restored for customers in NAM and APAC following completion and validation of recent updates. Work is still ongoing in EU, where reporting access continues to be addressed. Our teams remain actively engaged and focused on completing restoration in EU. We will continue to monitor closely and provide further updates as EU recovery progresses.

5. identified Dec 17, 2025, 10:31 PM UTC

   NAM and APAC remain operational following completion and validation of recent updates. Work is still ongoing in EU due to regional configuration differences. Additional updates are in progress, and validation will resume once those changes complete.

6. resolved Dec 18, 2025, 03:47 AM UTC

   Reporting functionality has been fully restored across all regions, and validation has confirmed stable operation. This issue was related to a recent change affecting reporting, which has now been fully addressed. Our teams have completed the required updates and verified successful recovery.

7. postmortem Jan 06, 2026, 02:01 AM UTC

   **Description:** Flexera One IT Visibility and Cloud License Management – Power BI Reporting Unavailable Across All Regions **Timeframe:** December 17, 2025, 5:54 AM PST – 6:46 PM PST **Incident Summary** On Wednesday, December 17, 2025, at 5:54 AM PST, we received reports of customers experiencing issues accessing out-of-the-box Power BI reports within Flexera One IT Visibility \(ITV\) and Cloud License Management \(CLM\). During this period, affected reports failed to load in production environments, preventing customers from accessing reporting insights. Other ITV and CLM functionality remained accessible during this time. The issue occurred following a production deployment related to reporting updates. As part of this change, multiple components required for report availability were updated. Customer impact was not anticipated at the time of deployment, and the resulting behavior caused reporting to become unavailable across all regions. Technical teams engaged immediately and coordinated recovery efforts across regions. Restoration progressed incrementally as deployment and validation activities completed. North America \(NAM\) and Asia-Pacific \(APAC\) were restored first after consistent successful behavior was confirmed. The Europe \(EU\) region required additional time due to configuration differences and the need to complete remaining deployment and validation steps. By December 17, 2025, at 6:46 PM PST, reporting functionality was fully restored across NAM, APAC, and EU. Post-restoration checks confirmed stable behavior, and no further customer impact was observed. **Root Cause** **Primary Root Cause** The disruption was caused by a production deployment related to Power BI reporting that required multiple components to be updated together for reports to remain available. At the time the deployment was executed, customer impact was not anticipated. As a result, reporting functionality became unavailable across production environments until the required deployment and validation steps were completed. **Contributing Factors** • The deployment involved coordinated updates across several components that needed to be applied together to restore reporting functionality. • Restoration and validation had to be completed carefully and consistently across all regions to avoid introducing further inconsistencies. • Regional configuration differences, particularly in the EU environment, required additional deployment steps and validation, which extended the overall recovery timeline. • A rollback or partial reversion was considered but not pursued, as completing the deployment end to end was assessed to be the safest and most reliable path to full restoration. **Remediation Actions** 1. Coordinated Deployment Completion: The reporting-related deployment was completed across all production regions to ensure consistency and restore report availability. 2. Region-by-Region Restoration and Validation: Reporting functionality was restored incrementally by region. North America and Asia-Pacific were validated first after consistent successful behavior was observed, followed by additional deployment and validation steps in Europe. 3. Functional Verification: Access to out-of-the-box Power BI reports was tested across multiple environments to confirm that reports were loading correctly and behaving as expected. 4. Extended Monitoring and Validation: Following extended monitoring and additional validation activities, full restoration of reporting functionality was confirmed at 6:46 PM PST. **Future Preventative Measures** This incident reinforced the importance of careful coordination when deploying changes that involve multiple dependent components. While customer impact was not anticipated in this case, the experience highlighted opportunities to further strengthen how similar updates are identified, planned, and executed to ensure predictable outcomes for customers. Based on this, the following measures are being applied: 1. Stronger Coordination for Multi-Component Updates: Updates that require front-end, back-end, and reporting components to be deployed together will be more closely coordinated to ensure readiness across regions and reduce the risk of unintended customer impact. 2. Execution Planning and Communication Readiness: Similar changes will continue to be planned with appropriate timing considerations, including execution within defined maintenance windows when applicable, and with communication readiness in place so customer notifications can be issued through StatusPage if impact is identified during planning or execution.