Is Flexera down?

Incident Description: Our teams earlier detected an intermittent issue that affected a subset of customers using Flexera One IT Asset Management in the EU environment. Affected customers may have intermittently experienced missing ITAM menu items, blank or pink error screens, or difficulty loading ITAM pages, while other Flexera One modules remained accessible. Priority: P2 Impact Start: September 10, 2026 , 2:00 AM PDT Impact End: September 10, 2026 , 6:00 AM PDT Resolution: The issue self-resolved, and affected customers regained access to ITAM functionality. Our technical teams monitored the environment and confirmed that error levels decreased and the service returned to a stable state. Next Actions: Our teams will continue to investigate the underlying root cause for the issue and further details will be shared via a post mortem report.

Incident Description: We are investigating an issue affecting Flexera One IT Asset Management in the APAC region. During a scheduled upgrade to version 2026R1.3 in the Australian Production environment, an issue was encountered that prevented the maintenance activity from being completed within the planned maintenance window. As a result, customers may be unable to access Flexera One IT Asset Management services in the APAC region. Priority: P1 Restoration Activity: Our technical teams are actively investigating the issue and reviewing the upgrade activity within the affected environment. We are working to identify the cause of the issue and implement a resolution to restore service availability as quickly as possible. Further updates will be provided as more information becomes available.

The issue has been identified and a fix has been implemented. The upgrade process has resumed and is currently progressing through the remaining deployment activities. Our technical teams are closely monitoring the environment to ensure the upgrade completes successfully and service availability is restored. Further updates will be provided as significant progress is made.

The upgrade to version 2026R1.3 has been successfully completed. Our technical teams are now performing post-deployment validation activities to verify service availability, functionality, and overall platform stability . We are closely monitoring the environment as these validation checks are completed and will provide a further update once validation has concluded.

Post-deployment validation activities have concluded, and service availability and platform stability have been confirmed. Access to Flexera One IT Asset Management services in the APAC region has been fully restored.

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.

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.

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.

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.

**Description:** Spot Ocean - Resource State Discrepancies and Under-Capacity Alerts **Timeframe:** August 25, 2026, 6:15 PM PDT – August 25, 2026, 10:22 PM PDT **Incident Summary** On Tuesday, August 25, 2026, at 6:15 PM PDT, Ocean customers began experiencing service degradation affecting resource state visibility and management operations. During the incident, customers may have observed 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, resource state information displayed within Spot did not accurately reflect the actual state of resources in AWS. Technical teams investigated the issue and identified degradation within a central Ocean service responsible for processing resource monitoring and management requests. As a result, monitoring and management operations slowed or stopped, resulting in broader service degradation across Ocean. The affected service was restarted, restoring normal request processing and service functionality. Following validation and monitoring activities, service stability was confirmed and the incident was resolved. **Root Cause** Investigation determined that a service responsible for processing resource monitoring and management requests experienced prolonged delays while communicating with a dependent service. As those delays accumulated, the service became unable to effectively process new requests. Although the service continued appearing operational, it was no longer able to process requests normally. This resulted in delayed resource state updates and contributed to the customer-facing symptoms observed during the incident, including resource state discrepancies, under-capacity alerts, and instances remaining in a Resuming state longer than expected. **Remediation Actions** The following actions were taken during the incident response: 1. **Incident Investigation Initiated:** Technical teams responded to production alerts and customer reports to assess the scope and impact of the issue. 2. **Service Degradation Identified: I**nvestigation determined that the affected service was no longer able to effectively process new monitoring and resource management requests. 3. **Service Recovery Performed:** The affected service components were restarted, restoring normal request processing and service functionality. 4. **Post-Recovery Validation Completed:** Technical teams monitored service behavior and validated stability before declaring the incident resolved. **Future Preventative Measures** Technical teams have initiated follow-up work to reduce the likelihood of similar issues occurring in the future. 1. **Monitor Service Reliability Improvements:** Technical teams have identified an existing service behavior that contributed to this incident and are implementing improvements to enhance overall service reliability. 2. **Service Design and Configuration Review:** Technical teams are reviewing the service design, configuration, and request processing behavior involved in this incident to identify additional opportunities to improve resiliency. 3. **Additional Investigation and Corrective Actions:** Technical teams are continuing to assess the findings identified during the investigation and will implement any additional corrective actions determined to be relevant to this incident.

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.

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.

Technical teams have performed targeted service recovery actions and are observing inventory processing resume for previously affected customers. Inventory is now being processed successfully for some organizations that were experiencing delays, and backlog levels are 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.

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.

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.

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.

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.

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.

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.

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.

**Description:** Flexera One - IT Asset Management - North America - Inventory Processing Delays **Timeframe:** August 24, 2026, at 5:33 AM PDT to August 27, 2026, at 9:30 AM PDT **Incident Summary** On Monday, August 24, 2026, at 5:33 AM PDT, reports surfaced of delayed inventory processing affecting some Flexera One IT Asset Management customers in the North America region. Customer inventory files continued to be uploaded, but some files were not progressing through downstream processing as expected. This resulted in growing processing backlogs and delayed availability of updated inventory data for affected customers. The issue affected inventory processing rather than access to the IT Asset Management platform Investigation identified that the issue followed a platform upgrade in the North America environment. During the upgrade activity, inventory upload requests experienced an elevated number of service unavailable responses, connection resets, and other connection-related failures. These conditions caused a cascade of failures within an inventory processing component. Although most inventory processing streams recovered automatically after the affected service components restarted, some streams remained stalled with inventory files queued for processing. Technical teams restarted the affected service components, which restored processing for the impacted workflows, although the accumulated inventory backlog initially cleared more slowly than expected. Processing capacity was increased, and workload, concurrency, and throughput settings were adjusted to improve processing performance. Service health checks were also updated as part of the stabilization activity. These actions increased processing throughput and enabled the accumulated backlogs to be worked through. On Thursday, August 27, 2026, at 9:30 AM PDT, the incident was considered resolved after the implemented measures restored stable inventory processing and the remaining production backlogs continued to decrease. Technical teams continued monitoring processing performance and backlog recovery following resolution. Subsequent validation confirmed that production inventory backlogs had cleared, with only isolated non-production testing backlogs remaining. **Root Cause** **Primary Root Cause:** Following a platform upgrade in the North America environment, inventory processing workflows experienced elevated service unavailable responses, connection interruptions, and related processing failures. While most processing activity recovered automatically, a subset of inventory processing workflows did not fully recover, resulting in inventory files remaining queued and unprocessed. This led to inventory processing backlogs and delayed inventory updates for affected customers. **Contributing Factors:** • Some inventory processing workflows remained stalled following the initial service disruption, preventing queued inventory data from being processed and contributing to backlog growth. • Existing monitoring capabilities did not provide visibility into this specific processing condition, resulting in abnormal backlog growth being identified through investigation rather than automated alerting. **Remediation Actions** The following actions were taken during the incident response: 1. Incident Investigation Initiated: Technical teams investigated reports of delayed inventory processing, reviewed processing behavior, and validated the scope of impact affecting inventory processing workflows in the North America environment. 2. Service Recovery Actions Performed: Affected service components were restarted to restore inventory processing activity and recover impacted processing workflows. 3. Processing Capacity Increased: Additional processing capacity was introduced to improve throughput, reduce processing backlogs, and support backlog recovery across affected inventory processing workflows. 4. Processing Optimizations Applied: Technical teams adjusted throughput, workload, and concurrency settings to improve inventory processing performance and accelerate backlog reduction. 5. Stability and Recovery Validation Performed: Processing throughput, backlog reduction, service health, and application stability were continuously monitored to verify successful recovery and confirm that inventory processing had returned to normal operating levels. **Future Preventative Measures** Following this incident, technical teams continue to assess the conditions that contributed to the inventory processing disruption and are implementing improvements to strengthen inventory processing reliability, detection, and recovery capabilities. 1. Validation and Monitoring Following Platform Changes: Technical teams are reviewing validation and monitoring activities associated with platform changes to improve the early identification of unexpected inventory processing behavior following maintenance and upgrade activities. 2. Enhanced Inventory Processing Monitoring and Alerting: Additional monitoring and alerting will be implemented to provide earlier visibility into abnormal inventory backlog growth and inventory processing disruptions. 3. Inventory Processing Recovery Improvements: Improvements will be implemented to strengthen inventory processing recovery behavior and reduce the likelihood of processing workflows remaining stalled following unexpected service interruptions.

Incident Description: We are currently investigating an issue affecting access to Flexera One IT Asset Management (ITAM) in the APAC region. The impacted customers may experience difficulties accessing the platform or may encounter errors after authentication. Priority: P1 Restoration Activity: Our technical have been engaged and are actively investigating the issue to identify the underlying cause and restore normal service as quickly as possible.

Our investigation has identified a configuration issue as the likely cause of the impact. Teams are actively working to implement and validate corrective measures to restore normal service operation. Further updates will be provided as the investigation progresses.

As the investigation has progressed, our teams have identified indications that the issue is not isolated to IT Asset Management and may have broader impact across the Flexera One platform in APAC. Remediation efforts are underway against the identified cause, and teams are focused on restoring full service stability. Additional updates will be provided as more information becomes available.

We are continuing to work on a fix for this issue.

A fix has been implemented, and access to the Flexera One platform has been restored. Our teams are conducting additional validation activities and continue to closely monitor service health and performance to confirm stability and ensure all services remain fully operational.

Following extended monitoring and verification activities, our teams have confirmed that services remain stable and no further impact has been observed. The incident has been resolved, and all affected services are fully operational.

**Description:** Flexera One - IT Asset management - APAC - Access disruption **Timeframe:** August 18, 2026, 2:10 AM PDT to August 18, 2026, 4:26:03 AM PDT ‌ **Incident Summary** ‌ On Tuesday, August 18, 2026, at 2:10 AM PDT , Flexera identified an issue affecting the Flexera One APAC Production environment that prevented customers from accessing Flexera One services. During the impact window, customers experienced login failures, session refresh failures, and issues retrieving user-related application data, resulting in widespread service access unavailability across the platform. Initial investigation indicated that the impact was limited to IT Asset Management. Further analysis determined that the issue involved a shared platform service supporting authentication and authorization across Flexera One, resulting in a broader impact across the APAC environment. Our technical teams identified an incorrect infrastructure scheduling configuration that prevented a critical platform service from operating as intended. The configuration was corrected, restoring the affected services. Following remediation, health checks returned successfully, application login and navigation functionality recovered, and teams completed post-restoration validation. The environment was subsequently confirmed healthy and placed under continued monitoring to ensure ongoing stability. ‌ **Root Cause** ‌ The incident was caused by an incorrect infrastructure scheduling configuration within a critical shared identity and access service. The configuration prevented the service from being scheduled onto the intended infrastructure, resulting in service unavailability and failures affecting authentication and authorization requests. ‌ **Remediation Actions** ‌ Our teams performed the below actions to restore the services to normalcy: * Configuration Correction: Corrected the infrastructure scheduling configuration affecting the impacted platform service. * Service Restoration: Restored the affected platform services and confirmed successful health checks. * Post-Restoration Validation: Performed automated health checks and platform validation to confirm application login, navigation, and related functionality had recovered. * Continued Monitoring: The environment was monitored following restoration to confirm ongoing platform stability. ‌ **Future Preventative Measures** ‌ * Pre-Deployment Validation: Implement additional validation checks for infrastructure scheduling and placement configurations. * Deployment Safeguards and Resiliency Controls: Review and strengthen deployment safeguards, configuration governance, and resiliency controls to prevent configuration mismatches from impacting service availability. * Expanded Post-Change Verification: Review and enhance the post-deployment and post-maintenance validation processes to ensure critical platform services are functioning correctly following infrastructure changes.