Flexera System Incident History

Our teams have completed post-deployment validation and confirmed that service performance has returned to expected levels. Continued monitoring has shown stable platform operation with no further impact observed. Based on these results, this issue is now considered resolved.

The hotfix has been successfully deployed, and engineering teams are currently validating its effectiveness. Teams are continuing to monitor platform behaviour and review telemetry to confirm the issue resolution.

Our teams continue to work on implementing a hotfix to address the issue . During deployment, the hotfix encountered database conditions that are preventing it from completing successfully. Our technical teams are actively working to resolve this and are evaluating targeted mitigation actions to allow the hotfix to complete. Once the hotfix has been successfully applied, teams will validate service performance and continue monitoring to confirm recovery. We will provide another update as more information becomes available.

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 US production environment. As a result, some customers may experience degraded performance and intermittent reliability issues when accessing certain areas of the user interface and performing system-related tasks. Priority: P3 Restoration Activity: Our investigation has determined that the issue is related to a software defect introduced with the 2026 R1.1 release. While the defect had been previously identified and mitigation procedures were incorporated into the deployment process, the automated remediation encountered unexpected execution issues . As a result, technical teams have implemented alternative mitigation measures to reduce customer impact and stabilise system performance. We continue to actively monitor the environment and apply corrective actions to address the underlying defect and restore normal service operation.

Corrective actions have now been applied to a larger number of affected organisations, and initial validation indicates that reports are loading successfully. We are currently validating all affected organisations to confirm that report functionality and service performance have been fully restored. In parallel, teams continue to implement broader remediation measures across the environment and are closely monitoring the service to ensure stability while work towards full resolution continues.

Our investigation has identified a potential configuration-related issue within the affected environment. As part of our validation efforts, corrective actions were applied to a subset of impacted organisations, and reports are now loading successfully. Our teams are currently focused on implementing a broader remediation across all affected organisations and are conducting a detailed review to understand why the configuration changes did not propagate as expected. We continue to validate the remediation and closely monitor service performance while working towards full resolution.

Incident Description: We are investigating an issue affecting IT Visibility in the Europe region where multiple Power BI reports are failing to load . Customers in the affected region may be unable to view impacted reports within the application. Current investigation indicates the issue is limited to the Europe region, with no impact observed in other regions at this time. Priority: P2 Restoration Activity: Our technical teams are actively investigating the issue to identify the underlying cause and restore report functionality. We are continuing to assess the scope of impact, monitor service health, and implement corrective actions as appropriate. We will provide further updates as more information becomes available.

**Description:** Spot Ocean – AWS – Ocean ECS Console Performance Degradation **Timeframe:** July 6, 2026, 05:45 AM PDT to July 6, 2026, 07:53 AM PDT ‌ **Incident Summary** ‌ On Monday, July 6, 2026, at 05:45 AM PDT , our teams identified a performance degradation affecting Spot Ocean ECS for AWS customers. During the impact window, customers experienced increased latency when accessing the Ocean ECS console, and some AWS-related operations were delayed or did not complete successfully. Technical teams immediately initiated an investigation to identify the source of the issue. As an AWS service disruption was occurring concurrently in the AWS us-east-1 region, the investigation initially considered both the external AWS event and a recently completed production deployment as potential contributing factors. Through detailed analysis, teams determined that the primary cause of the customer impact was instability introduced by the recent Gateway deployment. The resulting degradation in Gateway performance affected request processing and responsiveness within Spot Ocean ECS. While the concurrent AWS service disruption added complexity to the investigation, it was confirmed not to be the primary driver of the customer-facing impact. To restore service, teams rolled back the deployment to the previous stable version. Following the rollback, platform performance returned to expected levels and customer workflows resumed normal operation. An extended period of monitoring confirmed sustained service stability before the event was formally resolved. ‌ **Root Cause** ‌ The incident was caused by instability introduced in a Gateway deployment .The deployment resulted in degraded performance within the Gateway service, reducing its ability to efficiently process customer requests. This caused increased response times and intermittent failures for Spot Ocean ECS console operations and AWS-related workflows. Rolling back to the previous stable Gateway version restored normal platform performance and resolved the customer impact. Contributing Factors * A concurrent AWS service disruption in the us-east-1 region occurred during the same timeframe. While it was not the cause of the incident, it complicated the initial investigation and delayed identification of the underlying Gateway issue. * The Gateway rollback required additional time due to the scale of the production deployment, extending the overall recovery process. * Operations involving resource creation and updates experienced greater impact than read-only activities because of the degraded Gateway responsiveness. ‌ **Remediation Actions** ‌ * Technical teams investigated the degradation and identified a recent Gateway deployment as the primary source of the issue. * The affected Gateway deployment was rolled back to last know stable version, restoring service stability. * Platform performance and customer-facing workflows were validated following the rollback. * Technical teams completed an extended monitoring period to confirm stable service operation before closing the incident. ‌ **Future Preventative Measures** ‌ * Improved Deployment Safeguards - Engineering teams will strengthen deployment controls and validation processes to reduce the likelihood of similar deployment-related issues affecting production environments. * Enhanced Platform Monitoring - Additional monitoring and alerting will be implemented to provide earlier detection of abnormal Gateway behavior, including service responsiveness, resource utilization, and application stability. * Improved Recovery Procedures - Rollback procedures will be enhanced and regularly validated to reduce recovery time and improve operational efficiency during deployment-related incidents. * Proactive Service Health Validation - Synthetic health checks will be expanded to continuously validate critical Ocean ECS user workflows, enabling earlier identification of customer-facing performance degradation. * Enhanced Dependency Monitoring - Engineering teams will continue improving visibility into external cloud service events and platform dependencies to enable faster differentiation between internal platform issues and third-party service disruptions during future investigations.

We have continued to monitor the environment for an extended period and services have remained stable, with no further issues observed. This incident has been resolved.

Our investigation identified that the degradation was related to an AWS service health event impacting the us-east-1 region. AWS has since reported that the issue has been resolved, and we are now seeing signs of recovery on our side, including improved Spot Ocean ECS console performance and successful completion of related AWS workflows. The production environment appears stable at this time. Our teams will continue monitoring for a short validation period to ensure performance remains stable before marking the incident resolved.

Incident Description: We are currently investigating degraded performance affecting Spot Ocean ECS for AWS customers. Customers may experience significant slowness or delays when accessing the console or using certain Ocean ECS functionality. Priority: P2 Restoration Activity: Our technical teams are actively investigating and working to restore normal functionality. We will provide further updates as more information becomes available.

AWS resolved their service disruption on 18 July at 6:57 AM PDT. Following successful validation by our technical teams, we have confirmed that service functionality has been restored .

We continue to monitor the AWS service event and remain engaged with AWS as they complete their recovery activities. Validation completed to date has not identified any impact to Spot billing or cost analysis data. We are continuing to monitor the situation and complete any remaining validation activities before determining closure of this incident.

We remain actively engaged with AWS and continue to closely monitor the situation. AWS has identified the root cause and implemented mitigation measures to address the underlying issue that resulted in incorrect estimated cost and usage data being displayed. AWS has begun backfilling data to restore accurate cost and usage information for all customers and full recovery is expected by 18 July 2026, 12:00 PM PDT.

Our investigation and validation efforts to date have not identified any impact to Spot billing or cost analysis data. The billing and pricing data reviewed remains consistent with expected values. While initial validation results are positive, we are continuing additional validation activities as further data becomes available to confirm these findings. We remain engaged with AWS and will continue to monitor the situation closely. We will share additional updates as our validation activities continue.

We continue to closely monitor the service provider outage and its impact on affected services. Further updates will be provided as new information becomes available.

We are continuing to investigate this issue.

Incident Description: We have identified an issue impacting billing and cost visibility for AWS customers in all regions. As a result of an active service provider disruption, customers may observe inaccurate, incomplete, or delayed estimated cost and usage information within the Billing and Cost Management Console. This issue is limited to AWS-based services and does not affect customers using other cloud platforms. Priority: P2 Restoration Activity: Our technical teams have confirmed that the issue is related to an active AWS service event affecting all regions. We are actively monitoring the situation and working closely with AWS updates to assess customer impact. Service restoration is dependent on AWS resolving the underlying issue, and we will continue to provide updates as additional information becomes available.

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.

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.

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.

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.

**Description:** Flexera One – APAC – Intermittent Access Issues **Timeframe:** July 3, 2026, 11:20 AM PDT – July 3, 2026, 11:50 AM PDT **Incident Summary** On July 3, 2026, at approximately 11:20 AM PDT, an issue was identified affecting a subset of Flexera One services in the APAC production environment. During the incident window, some customers may have experienced intermittent access issues or failures when accessing certain areas of the Flexera One platform. The impact was intermittent in nature, as redundant service capacity remained available and continued serving traffic during the incident. Other Flexera One regions, including NAM and EU, were not impacted. Technical teams began investigating immediately and reviewed the affected services and supporting platform components within the APAC environment. The investigation identified that a recent change made within the APAC environment was contributing to the intermittent service failures being observed. As part of the recovery effort, the change was reverted and service behavior was monitored to validate recovery. Following the rollback, service stability was restored and customers were able to access affected functionality normally. By approximately 11:50 AM PDT, services were operating as expected and the incident was considered resolved. ‌ **Root Cause** The incident was caused by a configuration change within the APAC environment that unintentionally affected communication between a subset of platform services and a backend platform component. During the investigation, technical teams determined that the change resulted in certain platform services being unable to communicate properly with the affected component. This led to intermittent failures affecting a subset of Flexera One services in the APAC region. While the issue was occurring, one or more pods supporting the affected services remained available and continued serving traffic. As a result, customers experienced intermittent access issues rather than a complete service outage. ‌ **Remediation Actions** The following actions were taken during the incident response: • Incident Investigation Initiated: Technical teams began investigating intermittent access issues affecting a subset of Flexera One services in the APAC region. • Platform Review Completed: Technical teams reviewed the affected services and supporting platform components within the APAC environment to identify the source of the issue. • Recent Change Identified: Investigation identified a recently implemented change that correlated with the observed service degradation. • Change Reverted: The identified change was reverted as part of the mitigation effort to restore normal service behavior. • Service Recovery Validated: Technical teams monitored service behavior following the rollback and confirmed that affected functionality was operating normally. • Platform Stability Monitoring Continued: Additional monitoring was performed after restoration activities to verify continued service stability before the incident was closed. ‌ **Future Preventative Measures** This incident highlighted the importance of validating platform changes to ensure unintended impacts are identified before they affect service availability. Based on the investigation, the following follow-up activities are being pursued: • Configuration Validation Improvements: Review and enhance validation processes for infrastructure and platform configuration changes to help identify unintended impacts before changes are implemented in production environments. • Post-Deployment Verification Enhancements: Review post-deployment verification procedures to ensure critical service dependencies remain accessible and functioning as expected following configuration changes.

Incident Description: We identified an issue affecting a subset of Flexera One services in the APAC region, which may have resulted in intermittent access issues or failures for some users. The impact was intermittent, and other regions were not impacted. The issue has been resolved, and affected services are operating normally. Priority: P2 Restoration Activity: Our technical teams investigated the issue and reverted a recent change to restore service. We validated that the affected services are functioning normally and continued monitoring to ensure platform stability. This incident has been resolved.

**Description:** Flexera One- IT Asset management- APAC & EU - NDI Inventory Import Failures **Timeframe:** June 18, 2026, 09:00 AM PDT to June 25, 2026, 02:42 AM PDT ‌ **Incident Summary** ‌ On Wednesday, June 24, 2026, 11:35 PM PDT, following the deployment of the Flexera One IT Asset Management 2026 R1 release to the Australia and Europe Production environments, our teams identified an issue affecting the processing of NDI inventory files. As a result, a significant number of inventory files failed during processing and were not reflected in customer inventory data, causing inventory information displayed in Flexera One ITAM to become outdated for affected customers. Technical teams immediately initiated an investigation and determined that the issue occurred within the inventory processing workflow introduced with the 2026 R1 release. Failed inventory files accumulated following repeated processing failures, preventing successful completion of inventory updates and contributing to increased processing load on the affected services. To restore service, technical teams implemented corrective actions by refreshing the affected application services across impacted environments. Following the restoration activities, inventory processing resumed successfully, and new inventory uploads were processed as expected. Continued monitoring confirmed stable platform behavior, and the incident was declared resolved after sustained validation. ‌ **Root Cause** ‌ The issue was caused by a defect introduced with the Flexera One IT Asset Management 2026 R1 release that affected the processing of NDI inventory files. Under specific conditions, inventory files could not be processed successfully due to an issue within the authentication and processing workflow, causing the files to be rejected before processing could complete. As failed files accumulated, processing capacity was increasingly consumed by repeated failures, preventing successful inventory processing and delaying inventory updates for affected customers. Contributing Factors * Failed inventory files accumulated within the processing workflow, increasing resource utilization on affected inventory services. * The increased processing load reduced the capacity available for new inventory processing requests. * The issue affected production environments running the 2026 R1 release; North America Production was not impacted because the release had not yet been deployed. ‌ **Remediation Actions** ‌ * Technical teams identified the affected inventory processing workflow and implemented corrective actions to restore service. * Application services were refreshed across the impacted production environments, restoring normal inventory processing. * Processing of new inventory files resumed successfully following the service restoration. * The environment remained under enhanced monitoring to validate processing performance and confirm sustained recovery. ‌ **Future Preventative Measures** ‌ * Improved Release Validation - Release validation procedures will be enhanced to include additional end-to-end testing of inventory processing workflows following major platform releases. * Enhanced Processing Monitoring - Monitoring and alerting will be reviewed and expanded to provide earlier detection of abnormal inventory processing failures and excessive file accumulation within processing queues. * Operational Resiliency - Additional safeguards will be implemented within the inventory processing workflow to improve recovery from processing failures and minimize customer impact should similar conditions occur in the future. * Code Quality and Review Improvements \(Completed\) - As part of the post-incident review, the affected code has been corrected to ensure failures in communication are handled appropriately and do not result in broader processing impacts. In addition, the development and review process has been reinforced to ensure that review findings are appropriately evaluated and addressed before future changes are approved for release.

Incident Description: We identified an issue affecting inventory processing in Flexera One IT Asset Management following the 2026 R1 release in the APAC and Europe environments. As a result, some inventory uploads were not processed successfully, causing inventory data displayed in Flexera One IT Asset Management to be delayed and not reflect the most recently uploaded customer inventory. Priority: P2 Restoration Activity: Technical teams identified a capacity-related issue affecting inventory processing and performed targeted service restarts across the impacted regions to restore normal processing. Service was restored by June 24, 2026, 11:00 PM PDT, and inventory files are now processing successfully. Our teams are continuing to monitor the platform to ensure sustained stability. A post-mortem report detailing the root cause and preventative measures will be shared once the investigation is complete.

Incident Description:Our teams identified an issue affecting Cognos Analytics in the EU Production environment. During the impact window, affected customers may have been unable to access or load Cognos Analytics. Current investigation confirmed that the impact was limited to the EU Production region. Priority:P2 Restoration Activity: Our technical teams determined that the issue was related to a recent upgrade to Cognos Analytics , which was completed as part of the EU Production IT Asset Management release activities. The team identified a configuration issue introduced during the upgrade, implemented the necessary configuration corrections, and restored normal service functionality. The environment remains stable under monitoring. Further details, including the root cause and preventative measures, will be shared in a post-mortem report.

Following extended monitoring, we have confirmed that service performance has remained stable and is operating as expected. This issue is now resolved.

Our investigation has identified a potential configuration issue associated with the affected functionality. As part of ongoing mitigation efforts, configuration changes have been reverted, and previously initiated capacity increases have now been completed. We are actively monitoring the environment and validating platform behavior as these changes take effect. Work remains ongoing to restore full functionality for affected customers, and we will provide further updates as progress is made.

Our investigation has identified elevated resource utilization affecting the functionality associated with the reported issue. Mitigation actions are currently underway, including increasing system capacity to support recovery efforts. We are actively monitoring the environment and validating platform behavior as these changes are implemented. Work remains ongoing to restore full functionality for affected customers, and we will share additional updates as progress is made.

Incident Description: We are experiencing an issue affecting Flexera One IT Asset Management (ITAM) customers in the APAC region. Customers may notice that certain navigation and menu items within the ITAM interface are not visible, resulting in limited access to some functionality. Priority: P2 Restoration Activity: Our technical teams are actively investigating this issue and working to restore full functionality. We will continue to provide updates as more information becomes available.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Flexera will be conducting scheduled maintenance on the Self Service, CWF, and Cloud Management Platform (CMP) environments for US-4. Affected Environments:CWF - Shard4Self-Service - Shard4Cloud Management Platform(CMP) - Shard4 Dates/Times:IST : Jul 8th, 2026 | 08:00 AM to 10:00 AMPDT : Jul 7th, 2026 | 07:30 PM – 09:30 PMUTC : Jul 8th, 2026 | 02:30 AM to 04:30 AMAEST : Jul 8th, 2026 | 12:30 PM to 02:30 PM Impact:During this period, users may experience platform unavailability and intermittent issues with Self-Service, CWF consoles, CMP