Flexera Status

Resolved: Technical teams have confirmed that inventory processing has returned to normal operation following the capacity, workload, and concurrency tuning changes implemented during the incident.

Backlog recovery has been completed across the previously impacted production environment, and processing throughput has remained stable following the implemented changes. Technical teams have validated recovery and confirmed that inventory processing is operating as expected.

Technical teams will continue to review the incident as part of the post-incident process and identify any additional improvements to further strengthen service resiliency and inventory processing performance.

A detailed post-incident review report will be shared in the coming days, including investigation findings, corrective actions, and longer-term improvements identified as part of the review process.

The incident is now considered resolved.

Monitoring: Additional capacity and processing optimizations have been implemented across the inventory processing workflow and are producing positive results. Backlog recovery has accelerated significantly, resulting in a substantial reduction in overall backlog levels.

Technical teams continue to closely monitor processing activity, backlog recovery progress, and overall service stability while validating the effectiveness of the implemented improvements and ensuring processing continues to normalize as expected.

Monitoring: Technical teams continue to investigate the intermittent inventory processing delays affecting some customers. Recovery efforts remain ongoing, and inventory processing continues as technical teams work through the remaining delayed inventory backlog.

To support recovery, additional capacity and processing optimizations have been implemented across the inventory processing workflow. Technical teams continue to monitor processing activity, backlog recovery, and overall service stability while validating the impact of these changes.

Investigation into the underlying cause remains ongoing. While the backlog continues to decrease, technical teams are continuing to analyze the intermittent processing behaviour observed during the incident and validate long-term service stability.

We will continue to provide updates as recovery progresses.

Monitoring: Technical teams have implemented additional capacity changes as part of ongoing recovery efforts. Following these changes, backlog recovery continues to progress and technical teams are observing a reduction in processing errors.

Technical teams continue to monitor service stability and investigate the underlying cause of the incident.

We will continue to provide updates as recovery progresses.

Monitoring: Technical teams continue to monitor recovery and validate service stability. Inventory processing remains active, and recovery efforts continue as remaining delayed inventory is processed.

Investigation into the underlying cause remains ongoing. Technical teams continue to review the factors that contributed to the incident while monitoring processing activity and overall service health.

We will provide further updates as more information becomes available.

Monitoring: Technical teams continue to observe a steady reduction in backlog levels while closely monitoring overall service stability. Investigation into the underlying cause remains in progress. We will continue to provide updates as additional information becomes available.

Monitoring: Recovery continues to progress, with inventory processing activity returning to expected levels for previously impacted customers. Technical teams are observing a continued reduction in backlog levels and are actively monitoring service stability.

Investigation into the underlying cause remains ongoing. Current analysis is focused on several potential contributing factors identified during the affected period, while technical teams continue to validate recovery and monitor for any remaining impact.

Identified: Technical teams have performed targeted service recovery actions and are observing inventory processing resume for previously affected customers, with backlog levels decreasing.

Investigation remains ongoing as technical teams continue to monitor recovery and assess the underlying cause. While progress has been observed, teams are continuing to validate service stability and monitor for any remaining impact.

We will provide further updates as more information becomes available.

Investigating: Technical teams have identified that inventory processing behavior varies across affected customers. While inventory continues to be processed for some customers, others are experiencing significantly reduced processing rates or inventory that is not progressing through normal processing workflows.

Technical teams have also identified service availability errors affecting some inventory upload attempts and are actively investigating the scope of impact and underlying cause. Analysis of affected organizations and processing activity remains ongoing. Further updates will be provided as more information becomes available.

Investigating: Incident Description: We are investigating an issue affecting inventory processing within Flexera One IT Asset Management in North America. Customers may experience delays in inventory processing and delayed availability of updated inventory data within the platform.

Priority: P2

Restoration Activity: Our technical teams are actively investigating the issue and reviewing inventory processing activity across the affected service. We are working to identify the cause of the processing delays and restore normal processing. Further updates will be provided as more information becomes available.

Resolved: Our investigation determined that an internal service responsible for monitoring and resource state management became unresponsive, which contributed to the issues reported during the incident, including instances remaining in a Resuming state longer than expected, resource state discrepancies, and under-capacity alerts.

Our technical teams performed recovery actions, including restarting the affected service, and have since observed stable service operation. Following validation and monitoring, we have confirmed that affected services have returned to normal operation.

This incident is now considered resolved. A post-incident review is ongoing, and we will continue to evaluate opportunities for improvement.

Monitoring: We are continuing to observe stable service behavior across the affected areas, and the previously reported symptoms are no longer being observed. Our technical teams are closely monitoring the environment and validating service stability across affected customer workloads.We will continue to monitor and provide a further update once monitoring activities are complete or if additional information becomes available.

Investigating: Our technical teams are observing early signs of recovery and are actively monitoring service behavior while validating the impact across affected customer workloads.

Investigation and recovery efforts remain ongoing. We will continue to provide updates as we learn more and confirm service stability.

Investigating: Incident Description:
 We are investigating an issue affecting portions of the Spot platform. Customers may experience instances remaining in a Resuming state longer than expected, under-capacity alerts, and discrepancies between resource status information displayed in Spot and AWS. In some cases, customers may observe differences between the status shown in the Spot console and the actual status reported by AWS for affected resources. Our technical teams are actively investigating the scope and impact of the issue.

Priority: P2

Restoration Activity:
 Our technical teams are actively investigating the issue and assessing its impact across affected services and customer workloads. Current efforts are focused on identifying the underlying cause, validating the full scope of customer impact, and restoring normal service behavior. Further updates will be provided as more information becomes available.

Resolved: Our investigation determined that an internal service responsible for monitoring and resource state management became unresponsive, which contributed to the issues reported during the incident, including instances remaining in a Resuming state longer than expected, resource state discrepancies, and under-capacity alerts.

Our technical teams performed recovery actions, including restarting the affected service, and have since observed stable service operation. Following validation and monitoring, we have confirmed that affected services have returned to normal operation.

This incident is now considered resolved. A post-incident review is ongoing, and we will continue to evaluate opportunities for improvement.

Monitoring: We are continuing to observe stable service behavior across the affected areas, and the previously reported symptoms are no longer being observed. Our technical teams are closely monitoring the environment and validating service stability across affected customer workloads.We will continue to monitor and provide a further update once monitoring activities are complete or if additional information becomes available.

Investigating: Our technical teams are observing early signs of recovery and are actively monitoring service behavior while validating the impact across affected customer workloads.

Investigation and recovery efforts remain ongoing. We will continue to provide updates as we learn more and confirm service stability.

Investigating: Incident Description:
 We are investigating an issue affecting portions of the Spot platform. Customers may experience instances remaining in a Resuming state longer than expected, under-capacity alerts, and discrepancies between resource status information displayed in Spot and AWS. In some cases, customers may observe differences between the status shown in the Spot console and the actual status reported by AWS for affected resources. Our technical teams are actively investigating the scope and impact of the issue.

Priority: P2

Restoration Activity:
 Our technical teams are actively investigating the issue and assessing its impact across affected services and customer workloads. Current efforts are focused on identifying the underlying cause, validating the full scope of customer impact, and restoring normal service behavior. Further updates will be provided as more information becomes available.