Critical incident

Flexera System Status Dashboard: Flexera One - IT Asset Management - APAC - Service Disruption

Affected: IT Asset Management - APAC Beacon Communication, IT Asset Management - APAC Inventory Upload, IT Asset Management - APAC Login Page, IT Asset Management - APAC Batch Processing System, IT Asset Management - APAC Business Reporting, IT Asset Management - APAC SaaS Manager

Current status of Flexera System Status Dashboard: Operational — live Flexera System Status Dashboard status

Timeline

1. Oct 15, 2026, 22:37 UTC
   resolved
   Incident Description: Following the scheduled Flexera One IT Asset Management 2026R1.4 production release in the Australia region, we experienced an issue affecting Flexera One IT Asset Management services in APAC. As a result, customers were unable to access Flexera One IT Asset Management during the impact period. Priority: P1 Impact Start: October 15, 2026 at 11:34 AM PDT Impact End: October 15, 2026 at 12:32 PM PDT Restoration Activity: Our technical teams identified an issue affecting service components following the scheduled production release. Remediation was applied to the affected components to restore service availability. Following recovery, Flexera One IT Asset Management services in APAC returned to normal operation, and the issue is now considered resolved.
2. Oct 21, 2026, 23:40 UTC
   postmortem
   **Description:** Flexera One - IT Asset Management - APAC - Service Unavailability Following 2026R1.4 Release **Timeframe:** October 15, 2026, 11:34 AM PDT - October 15, 2026, 12:32 PM PDT ## Incident Summary On October 15, 2026, customers using Flexera One IT Asset Management in the APAC region experienced a service disruption that prevented access to the application. The disruption occurred following completion of the ITAM 2026R1.4 production release. Although services were initially available and operating normally after the release, the application subsequently became inaccessible. Technical teams investigated the disruption and identified failures affecting the initialization of application instances. Further investigation revealed that the production environment retained a dependency on a previous application initialization process while a transition to an updated process was underway. Although the application instances had been successfully initialized during the release, replacement instances were unable to complete the same process due to an outdated configuration. The affected replacement instances were unable to complete initialization successfully or pass the required health checks, preventing the application from returning to normal operation. Technical teams corrected the production configuration to reference the updated initialization process and performed an instance refresh. Following these changes, the affected instances initialized successfully, and ITAM service availability was restored at approximately 12:32 PM PDT. ## Root Cause The incident was caused by a remaining production dependency on a previous application initialization process during the transition to an updated process in the APAC production environment. While staging and user acceptance testing environments had already transitioned to the updated process, the APAC production environment retained a configuration that referenced the previous initialization process. During the 2026R1.4 production release, application instances were manually initialized using the updated process, allowing ITAM to initially operate normally despite the remaining production dependency. Components supporting the previous process were subsequently scaled down under the understanding that the broader transition had largely been completed. When replacement application instances were launched, the production configuration continued directing them to the previous initialization process. The affected instances were therefore unable to complete initialization successfully or pass their required health checks, resulting in the service disruption. The remaining production dependency on the previous initialization process was confirmed as the underlying cause of the incident. Correcting the production configuration to use the updated initialization process removed that dependency and allowed replacement instances to initialize successfully. ## Remediation Actions The following actions were taken during the incident response: 1. **Incident Investigation Initiated:** Technical teams investigated the application unavailability and identified failures affecting the initialization and health checks of application instances in the APAC production environment. 2. **Configuration Issue Identified:** Investigation determined that the production configuration continued referencing the previous application initialization process rather than the updated process. 3. **Production Configuration Corrected:** The production configuration was updated to reference the correct application initialization process, removing the dependency on the previous process. 4. **Application Instances Refreshed:** Technical teams performed an instance refresh following the configuration correction, allowing replacement instances to initialize successfully. 5. **Service Recovery Validated:** Technical teams confirmed that the affected instances were initializing successfully, applicatio

Updates as published by Flexera System Status Dashboard (original).