Flexera incident

Flexera One - APAC - Access discruption

Critical Resolved View vendor source →

Flexera experienced a critical incident on August 18, 2026 affecting IT Visibility - APAC and IT Asset Management - APAC Login Page, lasting 2h 41m. The incident has been resolved; the full update timeline is below.

Started
Aug 18, 2026, 09:32 AM UTC
Resolved
Aug 18, 2026, 12:13 PM UTC
Duration
2h 41m
Detected by Pingoru
Aug 18, 2026, 09:32 AM UTC

Affected components

IT Visibility - APACIT Asset Management - APAC Login Page

Update timeline

  1. investigating Aug 18, 2026, 09:32 AM UTC

    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.

  2. identified Aug 18, 2026, 10:18 AM UTC

    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.

  3. identified Aug 18, 2026, 10:43 AM UTC

    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.

  4. identified Aug 18, 2026, 10:50 AM UTC

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

  5. monitoring Aug 18, 2026, 11:47 AM UTC

    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.

  6. resolved Aug 18, 2026, 12:13 PM UTC

    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.