Flexera incident
Flexera One- IT Asset management- APAC & EU - Slowness and degraded performance
Flexera experienced a major incident on July 17, 2026 affecting IT Asset Management - EU Inventory Upload and IT Asset Management - APAC Inventory Upload, lasting 1d 11h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jul 17, 2026, 08:24 AM UTC
Incident Description: We have identified an issue affecting inventory processing in Flexera One IT Asset Management following the deployment of the 2026 R1.1 release in our APAC and Europe environments. As a result, a subset of customers may experience degraded performance when accessing certain areas of the user interface and while performing system-related tasks. Priority: P3 Restoration Activity: Our technical teams have identified the issue as a software defect introduced with the 2026 R1.1 release. Mitigation measures have been implemented to reduce customer impact, and teams are actively working to fully restore service performance. We will continue to provide updates as progress is made.
- identified Jul 17, 2026, 03:58 PM UTC
We continue to make progress in addressing the performance issues affecting a subset of customers in the APAC and Europe production environments. The identified fixes have now been deployed, and we are actively monitoring the environment as customer processing activities continue. Our teams are validating the effectiveness of these changes and assessing overall platform performance. We will provide additional updates as more information becomes available.
- monitoring Jul 18, 2026, 08:10 AM UTC
Our teams continue to validate the recently deployed hotfixes, and initial results look positive. We are closely monitoring affected processing activities to confirm the effectiveness of the fix and ensure platform stability. Validation is ongoing, and we will continue to monitor performance before confirming full resolution. We will provide another update as more information becomes available.
- resolved Jul 18, 2026, 07:29 PM UTC
Following deployment of the identified fixes, previously impacted processing activities are now completing successfully, and we are no longer seeing recurrence of the issues observed following the recent release. Based on the results observed after deployment of the fixes, this incident is now resolved. We will publish a full RCA in the coming days that will include a detailed summary of the issue, root cause, and preventative measures being implemented to help prevent recurrence.
- postmortem Jul 30, 2026, 05:47 PM UTC
**Description:** Flexera One – IT Asset Management – APAC & EU – Slowness and Degraded Performance **Timeframe:** July 13, 2026, 1:00 PM PDT – July 18, 2026, 7:10 AM PDT **Incident Summary** On July 13, 2026, at approximately 1:00 PM PDT, an issue began affecting Flexera One IT Asset Management customers in the APAC and Europe production environments following deployment of the 2026 R1.1 release. During the affected period, some customers experienced intermittent application slowness, delayed processing, reconcile failures, and degraded performance when accessing certain areas of the application or performing inventory-related activities. As customer reports increased, technical teams began investigating common patterns across the reported symptoms to determine the underlying cause. The investigation identified a defect introduced as part of the Flexera One IT Asset Management 2026 R1.1 release. Under certain conditions, the defect resulted in significantly higher database processing activity during inventory-related operations. As inventory data was processed, the increased workload contributed to processing delays, timeout conditions, and degraded application performance for some customers. Technical teams developed and deployed hotfixes to address the issue in the affected production environments. Following deployment, teams performed validation activities and monitored impacted processing workflows to confirm recovery. By July 18, 2026, at approximately 7:10 AM PDT, validation confirmed successful processing of previously impacted workloads and that the failure patterns associated with the issue were no longer occurring. The incident was considered resolved and technical teams continued monitoring to confirm service stability. **Root Cause** The incident was caused by a defect introduced in the Flexera One IT Asset Management 2026 R1.1 release affecting inventory-related processing operations. Under certain conditions, the defect caused significantly more database processing activity than intended during inventory-related processing operations. This increased workload resulted in elevated resource consumption, processing delays, and timeout conditions. These conditions contributed to intermittent application slowness, delayed processing, reconcile failures, and degraded performance affecting some IT Asset Management functionality. **Remediation Actions** 1. Incident Investigation Initiated: Technical teams began investigating reports of application slowness, processing delays, and reliability issues affecting APAC and Europe production environments. 2. Impact Assessment Performed: Teams reviewed customer-reported symptoms, system performance data, and processing behavior to determine the scope and nature of the issue. 3. Cause Identified: Investigation determined that a defect introduced in the 2026 R1.1 release was generating excessive processing activity during inventory-related operations. 4. Hotfixes Developed and Deployed: Technical teams developed and deployed hotfixes to correct the affected processing behavior in the APAC and Europe production environments. 5. Recovery Validated: Teams validated the effectiveness of the hotfixes through monitoring and successful execution of previously impacted processing activities. 6. Post-Restoration Monitoring Performed: Additional monitoring confirmed that the previously observed failures and performance degradation were no longer occurring and that service stability had been restored. **Future Preventative Measures** Based on the investigation, the following follow-up activity has been identified: • Processing Logic Improvements: Technical teams implemented corrections to the affected processing logic to eliminate the inefficient behavior that contributed to increased resource consumption and performance degradation.