Flexera Status

Resolved: Our investigation identified a connectivity issue within a service dependency path that affected customer access in the North America environment. Our technical teams updated the routing configuration, successfully restoring connectivity between the affected services. Service has been fully restored and is operating normally. The issue is resolved.

Investigating: Incident Description: We are currently investigating an issue affecting access to Flexera One services in the NAM 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.

Identified: Technical teams have implemented an updated remediation in the affected production environments and are currently reviewing the outcome of the deployment.

We are working to confirm whether inventory processing has returned to normal operation for affected customers and whether the issue has been fully resolved.

Further updates will be provided once validation activities have been completed.

Identified: Our investigation remains ongoing, and recent testing has shown that the previously deployed hotfix has not fully resolved the issue.

To address this, our teams have developed and deployed an updated hotfix to a validation environment, where additional testing and verification activities are currently underway. The investigation has narrowed the scope of the issue, and teams are actively working to identify the remaining factors contributing to the behaviour.

We remain focused on implementing a permanent resolution and will continue to provide updates as progress is made.

Monitoring: The hotfix has been successfully deployed to the production environment. Our teams are currently validating the results and closely monitoring the service to ensure continued stability and performance.

Identified: Our teams have successfully completed testing and validation of the hotfix designed to address the identified issue. The hotfix is now ready to be deployed to the production environment. Our technical teams are currently working to implement the fix in the production environment.

Following deployment, we will continue to closely monitor the service to ensure stability and expected performance. We will provide additional updates as progress is made.

Identified: Our teams have completed the hotfix development and successfully merged the changes . We are currently coordinating the deployment activities required to implement the fix in the production environment. Our teams are actively working to move the fix through the next stage as quickly as possible.

We will provide another update when additional progress has been made.

Identified: Our teams continue to make progress toward implementing a permanent resolution. During the validation process, additional issues were identified that required further review and remediation before the fix could be safely deployed.

Current investigations indicate that these validation findings do not appear to be related to the planned fix itself. The hotfix has since been rebuilt, and our teams are continuing validation and additional testing to ensure the solution can be deployed safely and effectively.

We will provide a further update as validation progresses .

Identified: Our teams continue to make progress toward implementing a permanent resolution. During the validation process, issues were identified that require further review and remediation before the fix can be safely deployed. As a result, the validation timeline has been extended while the team works through these findings and completes the necessary testing.

We will continue to provide updates as significant progress is made and additional information becomes available.

Identified: Our teams continue to progress through the validation phase for the proposed hotfix. Given the scale and complexity of the affected processing workflows, the validation activities are expected to take additional time to ensure the solution addresses the issue effectively.

We are closely monitoring progress and will provide further updates as validation continues and more information becomes available.

Identified: Our teams have identified the underlying cause of the issue and developed a targeted hotfix to address it. The hotfix is currently undergoing comprehensive validation to confirm its effectiveness and ensure service stability. Upon successful completion of validation, the fix will be deployed to the affected environments.

We will continue to provide updates as progress is made and additional information becomes available.

Investigating: Incident Description: We are investigating an issue affecting inventory .zip file processing for a subset of our customers using Flexera One IT Asset Management in the EU and APAC regions. Affected customers may experience issues with inventory .zip file processing. Inventory upload tasks may remain in an "In Progress" state for an extended period before eventually timing out, which may result in delays to inventory processing and data updates within Flexera One IT Asset Management.

Priority: P2

Restoration Activity: Our technical teams are actively investigating the issue and analysing inventory processing activity in the affected environments. Efforts are focused on identifying the root cause of the processing failures and implementing remediation as quickly as possible. We will continue to provide updates as additional information becomes available.

Resolved: 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.

Resolved: The hotfix was successfully deployed, and our teams closely monitored the services overnight to validate the effectiveness of the remediation and ensure continued stability.

No new errors were observed following the deployment, and the affected services remained stable throughout the monitoring period. Based on these results, this incident is now considered resolved.

Our teams will continue to investigate the underlying cause and identify any additional improvement opportunities. Further details, including the root cause analysis and corrective actions, will be shared in a post-mortem report.

Monitoring: The hotfix has been successfully deployed to the production environment. Our teams are currently validating the results and closely monitoring the service to ensure continued stability and performance.

Monitoring: Our investigation has identified an underlying defect that has the potential to impact any environment upgraded to version 2026 R1.3. To ensure continued service stability and performance, our teams are currently building and validating a targeted hotfix.

As a precaution, deployment of the 2026 R1.3 release to other regions has been temporarily deferred . Based on current progress, we estimate approximately 7 to 8 additional hours to complete the necessary validation and deployment activities.

Our teams remain actively engaged and continue to closely monitor the situation. We will provide further updates as they become available.

Monitoring: Our investigation has identified an underlying issue affecting a component involved in inventory processing. Recent platform changes have caused the issue to be detected and surfaced earlier in the processing workflow.

As an immediate mitigation, our teams have developed a hotfix . The hotfix is scheduled for deployment tomorrow morning (AEST). In parallel, engineering teams are conducting a deeper investigation to implement a permanent resolution and improve the performance and reliability of the affected processing path. We will continue to provide updates as additional progress is made and will share further details following the deployment and validation activities.

Monitoring: Our teams have continued to monitor the effectiveness of the configuration changes and processing timeout adjustments implemented to mitigate the impact of the underlying defect. While the service remains stable overall, our teams continue to closely monitor processing activity to confirm the long-term effectiveness of these mitigations and ensure sustained service stability. The investigation into the underlying defect remains ongoing as we work toward a permanent resolution.

We will provide further updates as additional information becomes available or if there are any significant changes to service status.

Monitoring: Our investigation has identified an underlying defect contributing to the inventory processing issues. To mitigate customer impact, our teams have implemented targeted configuration changes and adjusted processing timeout thresholds in all regions. Initial observations indicate improved processing behaviour; however, we will continue to closely monitor the affected services over the weekend to validate the effectiveness of these measures and confirm service stability.

We remain actively engaged in our investigation and will provide further updates as additional information becomes available.

Identified: While the mitigation has reduced the number of failures, a small percentage of reconciliation requests continue to experience issues. Our technical teams continuing to investigate the remaining failures and the underlying cause of the extended processing times. We will provide further updates as soon as additional information becomes available.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Our technical teams have identified that some reconciliation requests are taking longer than the configured processing timeout, resulting in intermittent delays or failures for customers in the EU Production environment. As an immediate mitigation, changes have been made to the processing timeout , and early results show improved reconciliation success, with many of the requests that previously timed out now completing successfully. Teams are continuing to investigate the underlying performance issue and are working toward a permanent resolution. Further updates will be provided as significant progress is made.

Monitoring: The service continues to operate stably, and error levels remain very low. However, a small number of residual errors are still being observed. Our teams remain actively engaged in investigating these errors and are working to implement further mitigations to eliminate the remaining impact and ensure complete resolution.

Monitoring: Following overnight monitoring, our teams have confirmed that while the service remains stable overall, a small number of errors are still being observed. The error rate remains very low, but the issue has not been fully eliminated. We continue to actively investigate the remaining errors and are working to identify and implement additional mitigations to address the residual impact. Our teams remain engaged and will provide further updates as more information becomes available.

Monitoring: Alternate infrastructure has been created and the configuration has been updated to direct processing to the new environment. All executions of the previously affected processing step have succeeded since the change was initiated, with the last observed failure occurring at 2:43 AM PDT on September 9, 2026. Technical teams are continuing to monitor the transition and processing activity to confirm sustained stability.

Investigating: Technical teams have narrowed the investigation to the reconciliation results retrieval process and are evaluating a potential capacity-related issue. As a mitigation measure, service capacity has been increased, and teams are monitoring whether this reduces reconciliation failures. Some reconciliation jobs continue to complete successfully, while others are experiencing timeouts when retrieving results.

Investigating: Technical teams continue to investigate reconciliation failures in the EU Production environment. Some reconciliation jobs are encountering timeout errors while retrieving results from a dependent service, resulting in failed or delayed processing. Infrastructure-related errors are also being investigated, and the root cause has not yet been confirmed.

Technical teams are continuing to analyze service telemetry and infrastructure health data to identify the underlying cause and implement the appropriate remediation. Further updates will be provided as they become available.

Investigating: Incident Description: We are currently investigating an issue impacting the reconciliation process within the IT Asset Management platform in the EU region. Affected customers may experience failures when attempting to run reconciliation jobs. As a result, reconciliation processes may not complete successfully, potentially delaying data updates and downstream processing.

Priority: P2

Restoration Activity: Our technical teams have been engaged and are actively working to identify the root cause and restore services. Further updates will be provided as we continue working toward resolution.

Identified: Technical teams have implemented an updated remediation in the affected production environments and are currently reviewing the outcome of the deployment.

We are working to confirm whether inventory processing has returned to normal operation for affected customers and whether the issue has been fully resolved.

Further updates will be provided once validation activities have been completed.

Identified: Our investigation remains ongoing, and recent testing has shown that the previously deployed hotfix has not fully resolved the issue.

To address this, our teams have developed and deployed an updated hotfix to a validation environment, where additional testing and verification activities are currently underway. The investigation has narrowed the scope of the issue, and teams are actively working to identify the remaining factors contributing to the behaviour.

We remain focused on implementing a permanent resolution and will continue to provide updates as progress is made.

Monitoring: The hotfix has been successfully deployed to the production environment. Our teams are currently validating the results and closely monitoring the service to ensure continued stability and performance.

Identified: Our teams have successfully completed testing and validation of the hotfix designed to address the identified issue. The hotfix is now ready to be deployed to the production environment. Our technical teams are currently working to implement the fix in the production environment.

Following deployment, we will continue to closely monitor the service to ensure stability and expected performance. We will provide additional updates as progress is made.

Identified: Our teams have completed the hotfix development and successfully merged the changes . We are currently coordinating the deployment activities required to implement the fix in the production environment. Our teams are actively working to move the fix through the next stage as quickly as possible.

We will provide another update when additional progress has been made.

Identified: Our teams continue to make progress toward implementing a permanent resolution. During the validation process, additional issues were identified that required further review and remediation before the fix could be safely deployed.

Current investigations indicate that these validation findings do not appear to be related to the planned fix itself. The hotfix has since been rebuilt, and our teams are continuing validation and additional testing to ensure the solution can be deployed safely and effectively.

We will provide a further update as validation progresses .

Identified: Our teams continue to make progress toward implementing a permanent resolution. During the validation process, issues were identified that require further review and remediation before the fix can be safely deployed. As a result, the validation timeline has been extended while the team works through these findings and completes the necessary testing.

We will continue to provide updates as significant progress is made and additional information becomes available.

Identified: Our teams continue to progress through the validation phase for the proposed hotfix. Given the scale and complexity of the affected processing workflows, the validation activities are expected to take additional time to ensure the solution addresses the issue effectively.

We are closely monitoring progress and will provide further updates as validation continues and more information becomes available.

Identified: Our teams have identified the underlying cause of the issue and developed a targeted hotfix to address it. The hotfix is currently undergoing comprehensive validation to confirm its effectiveness and ensure service stability. Upon successful completion of validation, the fix will be deployed to the affected environments.

We will continue to provide updates as progress is made and additional information becomes available.

Investigating: Incident Description: We are investigating an issue affecting inventory .zip file processing for a subset of our customers using Flexera One IT Asset Management in the EU and APAC regions. Affected customers may experience issues with inventory .zip file processing. Inventory upload tasks may remain in an "In Progress" state for an extended period before eventually timing out, which may result in delays to inventory processing and data updates within Flexera One IT Asset Management.

Priority: P2

Restoration Activity: Our technical teams are actively investigating the issue and analysing inventory processing activity in the affected environments. Efforts are focused on identifying the root cause of the processing failures and implementing remediation as quickly as possible. We will continue to provide updates as additional information becomes available.

Resolved: Our investigation identified a connectivity issue within a service dependency path that affected customer access in the North America environment. Our technical teams updated the routing configuration, successfully restoring connectivity between the affected services. Service has been fully restored and is operating normally. The issue is resolved.

Investigating: Incident Description: We are currently investigating an issue affecting access to Flexera One services in the NAM 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.

Resolved: Our investigation identified a connectivity issue within a service dependency path that affected customer access in the North America environment. Our technical teams updated the routing configuration, successfully restoring connectivity between the affected services. Service has been fully restored and is operating normally. The issue is resolved.

Investigating: Incident Description: We are currently investigating an issue affecting access to Flexera One services in the NAM 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.

Resolved: Our investigation identified a connectivity issue within a service dependency path that affected customer access in the North America environment. Our technical teams updated the routing configuration, successfully restoring connectivity between the affected services. Service has been fully restored and is operating normally. The issue is resolved.

Investigating: Incident Description: We are currently investigating an issue affecting access to Flexera One services in the NAM 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.

Resolved: Our teams have continued to monitor the service closely, and no new issues have been observed. The backlog of queued work that accumulated during the disruption is processing successfully and continuing to decrease as expected. Based on the stability observed since recovery, this incident is now resolved. We will continue to monitor processing to ensure the remaining backlog clears completely and the service continues to operate as expected.

Monitoring: The issue affecting the EU environment has been resolved, and access to the user interface has been fully restored.

While the service is now operating normally, it may take some time for the backlog of queued work that accumulated during the outage to be processed. Our teams are actively monitoring the recovery to ensure the backlog is cleared and services continue to perform as expected.

We will continue to monitor the environment closely and confirm once processing has fully returned to normal levels.

Investigating: Incident Description: We are currently investigating an issue affecting the Policies and Automation services in the EU Production environment. Customers in the EU may experience failures when using Policies and may be unable to view their policies through the user interface. The impact is limited to the EU region.

Priority: P2

Restoration Activity: Our technical teams have been engaged and are actively investigating an issue encountered during an infrastructure upgrade to identify the underlying cause and restore normal service as quickly as possible. Further updates will be provided as the investigation progresses.

Monitoring: Our service provider has declared the underlying incident resolved following successful mitigation and extended validation.

Community remains accessible, and no confirmed ongoing impact has been identified. Monitoring throughout the recovery period has not identified any additional issues.

This incident is now considered resolved.

Monitoring: Our service provider reports that service telemetry has remained healthy following deployment of the mitigation. Community remains accessible at this time, and no confirmed ongoing impact has been identified.

We will continue monitoring the environment to ensure ongoing stability while final validation activities are completed. We will provide a further update as additional information becomes available.

Identified: The service provider has successfully validated the fix in a test environment and has begun deploying it across all affected instances. The rollout is progressing on a region-by-region basis, and services are returning to normal in regions where deployment has been completed.

Identified: Incident Description: We are currently experiencing an issue affecting the Flexera Community site. Due to an ongoing outage impacting a third-party service provider, customers may be unable to access the Flexera Community portal or may experience intermittent and unreliable behaviour. Additionally, customers may be unable to create, update, or interact with support cases through the Community site. Emails sent to [email protected] during this period may not be received or processed until the underlying outage has been resolved. This third party service provider outage also impacts the proactive monitoring ability for Spot support teams to detect any customer environment issues along with a chatbot widget inside the Spot console as well.

Priority: P3

Restoration Activity: Our technical teams are actively monitoring the situation and working with the third-party provider to track restoration efforts. We will continue to assess customer impact and provide further updates as additional information becomes available.