Flexera experienced a major incident on September 15, 2026 affecting Automation, lasting 9h 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 15, 2026, 11:05 PM UTC
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 Sep 16, 2026, 06:16 AM UTC
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.
- resolved Sep 16, 2026, 08:24 AM UTC
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.
- postmortem Oct 12, 2026, 12:02 PM UTC
**Description:** Flexera - EU - Policies/Automation Unavailable **Timeframe:** September 15, 2026, 3:50 PM PDT to September 16, 2026, 1:22 AM PDT **Incident Summary** On September 15, 2026, at 3:50 PM PDT, an infrastructure upgrade supporting Automation in the EU Production environment resulted in a network connectivity disruption affecting Policies and Automation. Customers experienced difficulties viewing policies in the user interface, and policy-related operations failed. The investigation identified unexpected behavior from a legacy network component . This disrupted connectivity required by the affected services.The team identified the component involved and brought the required resource online, restoring network connectivity. The underlying issue was resolved on September 15 at 10:13 PM PDT. Following this, the team continued monitoring service recovery and the processing of the backlog accumulated during the disruption. Once backlog processing had progressed as expected and service stability was confirmed, the incident was declared fully restored on September 16, 2026, at 1:22 AM PDT. The impact was limited to the EU Production environment. **Root Cause** The incident was caused by unexpected behavior from a legacy network component during the Automation infrastructure upgrade in the EU region. This disrupted network connectivity required by Policies and Automation, resulting in service unavailability and failures in policy-related functionality. **Remediation Actions** Our teams performed the below actions to restore the services to normalcy: * Connectivity restoration: Identified the legacy component involved and brought the required resource online to restore network connectivity. * Service recovery: Restored connectivity and resolved the underlying issue affecting Policies and Automation. * Backlog processing: Monitored the accumulated backlog as processing recovered following service restoration. * Post-restoration validation: Confirmed service stability and verified that backlog processing was progressing as expected before declaring the incident fully restored. **Future Preventative Measures** * Migration planning: The corresponding US migration was rescheduled with a longer maintenance window to allow additional time for troubleshooting and recovery. * Legacy component replacement: The legacy component is being replaced as part of the infrastructure modernization effort. Once the replacement is complete, this specific legacy dependency is expected to be eliminated in all environments.