Flexera Status

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, application health checks were passing, and ITAM services had returned to normal operation.

Future Preventative Measures

Following the incident, a retrospective was conducted to review the application initialization process, remaining production dependencies, release-validation procedures, and opportunities to improve incident detection and response.

The following corrective actions and improvement activities have been completed or are underway:

1. Production Configuration Correction: The APAC production environment has been updated to use the correct application initialization process, replacing the previous configuration.
2. Legacy Dependency Validation: A follow-up action has been established to add a validation step before legacy platform components are scaled down or decommissioned, ensuring that production services have fully transitioned and no remaining dependencies exist on the previous platform.
3. Release and Application Health-Check Review: Existing application health checks, release-validation procedures, and post-release sanity-test coverage are being reviewed against the failure observed during this incident. The review will determine whether any coverage gaps exist and whether additional monitoring, validation, or other improvements are required.
4. Instance Scaling Investigation: We will continue to investigate what triggered the original application instances to scale following the release and determine whether any additional corrective or preventative action is required.
5. Customer Communication Improvements: We identified an opportunity for more timely customer communication during this incident. Our established incident escalation and communication practices are designed to ensure proactive customer notification when unplanned service impact is identified. The learning from this incident has been incorporated into our ongoing incident response practices to help ensure these procedures are applied consistently and that timely, proactive updates are provided to customers during service disruptions.

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.

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, application health checks were passing, and ITAM services had returned to normal operation.

Future Preventative Measures

Following the incident, a retrospective was conducted to review the application initialization process, remaining production dependencies, release-validation procedures, and opportunities to improve incident detection and response.

The following corrective actions and improvement activities have been completed or are underway:

1. Production Configuration Correction: The APAC production environment has been updated to use the correct application initialization process, replacing the previous configuration.
2. Legacy Dependency Validation: A follow-up action has been established to add a validation step before legacy platform components are scaled down or decommissioned, ensuring that production services have fully transitioned and no remaining dependencies exist on the previous platform.
3. Release and Application Health-Check Review: Existing application health checks, release-validation procedures, and post-release sanity-test coverage are being reviewed against the failure observed during this incident. The review will determine whether any coverage gaps exist and whether additional monitoring, validation, or other improvements are required.
4. Instance Scaling Investigation: We will continue to investigate what triggered the original application instances to scale following the release and determine whether any additional corrective or preventative action is required.
5. Customer Communication Improvements: We identified an opportunity for more timely customer communication during this incident. Our established incident escalation and communication practices are designed to ensure proactive customer notification when unplanned service impact is identified. The learning from this incident has been incorporated into our ongoing incident response practices to help ensure these procedures are applied consistently and that timely, proactive updates are provided to customers during service disruptions.

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.

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, application health checks were passing, and ITAM services had returned to normal operation.

Future Preventative Measures

Following the incident, a retrospective was conducted to review the application initialization process, remaining production dependencies, release-validation procedures, and opportunities to improve incident detection and response.

The following corrective actions and improvement activities have been completed or are underway:

1. Production Configuration Correction: The APAC production environment has been updated to use the correct application initialization process, replacing the previous configuration.
2. Legacy Dependency Validation: A follow-up action has been established to add a validation step before legacy platform components are scaled down or decommissioned, ensuring that production services have fully transitioned and no remaining dependencies exist on the previous platform.
3. Release and Application Health-Check Review: Existing application health checks, release-validation procedures, and post-release sanity-test coverage are being reviewed against the failure observed during this incident. The review will determine whether any coverage gaps exist and whether additional monitoring, validation, or other improvements are required.
4. Instance Scaling Investigation: We will continue to investigate what triggered the original application instances to scale following the release and determine whether any additional corrective or preventative action is required.
5. Customer Communication Improvements: We identified an opportunity for more timely customer communication during this incident. Our established incident escalation and communication practices are designed to ensure proactive customer notification when unplanned service impact is identified. The learning from this incident has been incorporated into our ongoing incident response practices to help ensure these procedures are applied consistently and that timely, proactive updates are provided to customers during service disruptions.

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.

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, application health checks were passing, and ITAM services had returned to normal operation.

Future Preventative Measures

Following the incident, a retrospective was conducted to review the application initialization process, remaining production dependencies, release-validation procedures, and opportunities to improve incident detection and response.

The following corrective actions and improvement activities have been completed or are underway:

1. Production Configuration Correction: The APAC production environment has been updated to use the correct application initialization process, replacing the previous configuration.
2. Legacy Dependency Validation: A follow-up action has been established to add a validation step before legacy platform components are scaled down or decommissioned, ensuring that production services have fully transitioned and no remaining dependencies exist on the previous platform.
3. Release and Application Health-Check Review: Existing application health checks, release-validation procedures, and post-release sanity-test coverage are being reviewed against the failure observed during this incident. The review will determine whether any coverage gaps exist and whether additional monitoring, validation, or other improvements are required.
4. Instance Scaling Investigation: We will continue to investigate what triggered the original application instances to scale following the release and determine whether any additional corrective or preventative action is required.
5. Customer Communication Improvements: We identified an opportunity for more timely customer communication during this incident. Our established incident escalation and communication practices are designed to ensure proactive customer notification when unplanned service impact is identified. The learning from this incident has been incorporated into our ongoing incident response practices to help ensure these procedures are applied consistently and that timely, proactive updates are provided to customers during service disruptions.

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.

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, application health checks were passing, and ITAM services had returned to normal operation.

Future Preventative Measures

Following the incident, a retrospective was conducted to review the application initialization process, remaining production dependencies, release-validation procedures, and opportunities to improve incident detection and response.

The following corrective actions and improvement activities have been completed or are underway:

1. Production Configuration Correction: The APAC production environment has been updated to use the correct application initialization process, replacing the previous configuration.
2. Legacy Dependency Validation: A follow-up action has been established to add a validation step before legacy platform components are scaled down or decommissioned, ensuring that production services have fully transitioned and no remaining dependencies exist on the previous platform.
3. Release and Application Health-Check Review: Existing application health checks, release-validation procedures, and post-release sanity-test coverage are being reviewed against the failure observed during this incident. The review will determine whether any coverage gaps exist and whether additional monitoring, validation, or other improvements are required.
4. Instance Scaling Investigation: We will continue to investigate what triggered the original application instances to scale following the release and determine whether any additional corrective or preventative action is required.
5. Customer Communication Improvements: We identified an opportunity for more timely customer communication during this incident. Our established incident escalation and communication practices are designed to ensure proactive customer notification when unplanned service impact is identified. The learning from this incident has been incorporated into our ongoing incident response practices to help ensure these procedures are applied consistently and that timely, proactive updates are provided to customers during service disruptions.

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.

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, application health checks were passing, and ITAM services had returned to normal operation.

Future Preventative Measures

Following the incident, a retrospective was conducted to review the application initialization process, remaining production dependencies, release-validation procedures, and opportunities to improve incident detection and response.

The following corrective actions and improvement activities have been completed or are underway:

1. Production Configuration Correction: The APAC production environment has been updated to use the correct application initialization process, replacing the previous configuration.
2. Legacy Dependency Validation: A follow-up action has been established to add a validation step before legacy platform components are scaled down or decommissioned, ensuring that production services have fully transitioned and no remaining dependencies exist on the previous platform.
3. Release and Application Health-Check Review: Existing application health checks, release-validation procedures, and post-release sanity-test coverage are being reviewed against the failure observed during this incident. The review will determine whether any coverage gaps exist and whether additional monitoring, validation, or other improvements are required.
4. Instance Scaling Investigation: We will continue to investigate what triggered the original application instances to scale following the release and determine whether any additional corrective or preventative action is required.
5. Customer Communication Improvements: We identified an opportunity for more timely customer communication during this incident. Our established incident escalation and communication practices are designed to ensure proactive customer notification when unplanned service impact is identified. The learning from this incident has been incorporated into our ongoing incident response practices to help ensure these procedures are applied consistently and that timely, proactive updates are provided to customers during service disruptions.

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.

Resolved: Following the recovery actions previously implemented, our technical teams completed additional validation and monitoring. Users and Computer Details functionality has remained stable with no further issues observed. Normal operation has been confirmed, and this incident is now considered resolved.

Monitoring: Our technical teams identified timeout errors affecting service components supporting the impacted functionality and performed targeted service restarts. Following these recovery actions, Users and Computer Details functionality is responding successfully during validation. We are continuing to monitor service behavior and perform final validation to confirm sustained stability.

Investigating: Incident Description: We are investigating an issue affecting Snow Atlas SAM Core functionality in the UK South region. Some customers may experience issues accessing Users functionality and may encounter errors when accessing Computer Details.

Priority: P2

Restoration Activity: Our technical teams are actively investigating the issue and assessing the scope of impact. We are working to identify the underlying cause and restore the affected functionality. Further updates will be provided as more information becomes available.