Flexera incident

Flexera One – EU – Login Access Disruption

Major Resolved View vendor source →

Flexera experienced a major incident on June 24, 2026 affecting IT Asset Management - EU Beacon Communication and IT Visibility EU and 1 more component, lasting 59m. The incident has been resolved; the full update timeline is below.

Started
Jun 24, 2026, 08:00 AM UTC
Resolved
Jun 24, 2026, 09:00 AM UTC
Duration
59m
Detected by Pingoru
Jun 24, 2026, 08:00 AM UTC

Affected components

IT Asset Management - EU Beacon CommunicationIT Visibility EUCloud License Management - EUIT Asset Management - EU Inventory UploadIT Asset Management - EU Login PageIT Asset Management - EU Batch Processing SystemIT Asset Management - EU Business ReportingIT Asset Management - EU SaaS Manager

Update timeline

  1. investigating Jun 24, 2026, 08:00 AM UTC

    Incident Description: We have identified an issue affecting login access to Flexera One in the EU region. Customers may receive errors when attempting to log in to Flexera One. Priority: P1 Restoration Activity: Our technical teams are actively investigating the issue and working to implement corrective actions to restore normal login functionality. Investigation and stabilization efforts remain ongoing. We will continue to monitor the situation closely and provide further updates as progress continues.

  2. resolved Jun 24, 2026, 09:00 AM UTC

    The issue has been resolved, and login functionality has been restored for affected customers. Technical teams identified the cause of the issue and implemented corrective actions to restore normal service operation. The environment remains stable, and ongoing monitoring has confirmed successful authentication and platform access. A post-mortem report containing additional details, will be shared upon completion of the investigation.

  3. postmortem Jul 07, 2026, 08:28 AM UTC

    **Description:** Flexera One – EU – Login Access Disruption **Timeframe:** June 24, 2026, 12:41 AM PDT to June 24, 2026, 02:04 AM PDT ‌ **Incident Summary** ‌ On Wednesday, June 24, 2026, at 12:41 AM PDT, our teams detected an issue affecting customers in the EU region. Impacted users experienced authentication failures when attempting to sign in to Flexera One using Single Sign-On \(SSO\), resulting in server errors and preventing access to the platform. Upon detection, technical teams immediately initiated an investigation and confirmed that the issue was isolated to the authentication workflow. Validation of the application and underlying platform services showed that all core infrastructure remained healthy and operational. Further analysis determined that a service account used to communicate with the identity provider had become unavailable, causing authentication requests to fail. The service account was promptly restored, which re-established normal authentication processing and fully restored customer access. Following restoration, the environment was closely monitored and login functionality was comprehensively validated to ensure service stability. No additional customer impact was observed, and the incident was subsequently declared resolved. ‌ **Root Cause** ‌ The issue was caused by the unintended suspension of a service account that supports authentication between Flexera One and the identity provider. As a result, authentication requests could not be processed successfully, preventing affected customers in the EU production region from accessing the platform through Single Sign-On \(SSO\). Contributing Factors * A service account critical to the authentication workflow was inadvertently suspended during a routine cleanup activity. * The suspension prevented authentication requests from being validated successfully, resulting in login failures for impacted customers. * The issue was isolated to the authentication service and did not affect the availability of the underlying application or platform infrastructure. ‌ **Remediation Actions** ‌ * The affected service account was restored, re-establishing authentication with the identity provider. * Login functionality was validated following restoration. * Engineering teams continued monitoring to confirm platform stability and successful customer authentication. ‌ **Future Preventative Measures** ‌ * Service Account Governance - Processes governing critical service accounts will be strengthened to reduce the risk of inadvertent changes affecting production services. * Enhanced Monitoring - Monitoring and alerting will be enhanced to provide earlier detection of authentication failures affecting customer login workflows. * Operational Process Improvements - Our teams have documented this as lesson learnt and will implement process improvements to reduce the likelihood of similar incidents.