Flexera incident
Flexera One - IT Asset Management - APAC - Missing Menu Items
Flexera experienced a major incident on July 12, 2026 affecting IT Asset Management - APAC Business Reporting, lasting 3h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 12, 2026, 11:51 PM UTC
Incident Description: We are experiencing an issue affecting Flexera One IT Asset Management (ITAM) customers in the APAC region. Customers may notice that certain navigation and menu items within the ITAM interface are not visible, resulting in limited access to some functionality. Priority: P2 Restoration Activity: Our technical teams are actively investigating this issue and working to restore full functionality. We will continue to provide updates as more information becomes available.
- identified Jul 13, 2026, 12:28 AM UTC
Our investigation has identified elevated resource utilization affecting the functionality associated with the reported issue. Mitigation actions are currently underway, including increasing system capacity to support recovery efforts. We are actively monitoring the environment and validating platform behavior as these changes are implemented. Work remains ongoing to restore full functionality for affected customers, and we will share additional updates as progress is made.
- identified Jul 13, 2026, 01:52 AM UTC
Our investigation has identified a potential configuration issue associated with the affected functionality. As part of ongoing mitigation efforts, configuration changes have been reverted, and previously initiated capacity increases have now been completed. We are actively monitoring the environment and validating platform behavior as these changes take effect. Work remains ongoing to restore full functionality for affected customers, and we will provide further updates as progress is made.
- resolved Jul 13, 2026, 03:44 AM UTC
Following extended monitoring, we have confirmed that service performance has remained stable and is operating as expected. This issue is now resolved.