Flexera experienced a major incident on July 28, 2026 affecting IT Asset Management - APAC Beacon Communication and api.flexera.au and 1 more component, lasting 2h 50m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 28, 2026, 11:14 PM UTC
Incident Description: We are investigating an intermittent issue affecting Flexera One services in the APAC region. Customers may experience intermittent access issues or errors while using Flexera One applications and services. The issue currently appears to be limited to the APAC region. Priority: P1 Restoration Activity: Our teams are actively investigating the issue. The scope and impact are being assessed across Flexera One services in the APAC region, and we are working to identify the underlying cause and restore service stability. Further updates will be provided as more information becomes available.
- investigating Jul 29, 2026, 12:34 AM UTC
Our technical teams are actively investigating the issue. The issue appears to be intermittent, with some requests succeeding while others continue to fail. We are reviewing affected services and their dependencies to determine the scope of impact, identify the underlying cause, and restore service stability.
- resolved Jul 29, 2026, 02:05 AM UTC
Technical teams have mitigated the issue affecting Flexera One services in the APAC region. Service functionality has been restored, and validation confirms that affected applications and services are operating as expected. During the investigation, teams identified intermittent service communication issues that resulted in access issues and errors for some customers. As part of the mitigation effort, technical teams restarted affected services, after which service functionality recovered and validation confirmed successful restoration of impacted services. We will continue to review the incident and monitor service health.
- postmortem Aug 12, 2026, 05:33 PM UTC
**Description:** Flexera One - APAC - Intermittent Service Disruption ## Timeframe **Timeframe:** July 28, 2026, 3:49 PM PDT - July 28, 2026, 5:40 PM PDT ## Incident Summary On Tuesday, July 28, 2026, at 3:49 PM PDT, customers using Flexera One services in the APAC region began experiencing intermittent service disruptions affecting multiple applications and platform capabilities. Customers may have encountered login issues, application errors, failed page loads, API errors, and intermittent access to certain Flexera One functionality. During the incident, multiple services experienced intermittent communication failures with shared platform services. As a result, customers experienced inconsistent application behavior, with some requests succeeding while others failed. Technical teams investigated the issue across affected applications and platform components to determine the scope and source of the failures. The investigation identified a connectivity issue affecting communication between application services and a shared platform dependency. Corrective configuration changes were implemented to restore service communication and stabilize affected functionality. Following implementation of the corrective changes, technical teams validated functionality across impacted applications and confirmed that services had returned to normal operation. Continued monitoring showed stable service behavior, and the incident was resolved at 5:40 PM PDT on July 28, 2026. ## Root Cause Investigation determined that the incident was caused by a connectivity issue introduced during a platform infrastructure migration. Following the migration, certain application services continued using legacy connection ports when communicating with shared platform services. When affected services restarted, they attempted to communicate using endpoint and port combinations that were no longer aligned with the updated platform configuration. This configuration mismatch resulted in intermittent communication failures between application services and shared platform components, causing customer-facing application errors and service disruptions across multiple Flexera One services in the APAC region. ## Remediation Actions The following actions were taken during the incident response: 1. **Incident Investigation Initiated:** Technical teams investigated reports of intermittent failures affecting multiple Flexera One services in the APAC region and assessed the scope of customer impact. 2. **Dependency Analysis Performed:** Technical teams reviewed communication paths between impacted applications and shared platform services to identify the source of the connectivity failures. 3. **Configuration Mismatch Identified:** Investigation determined that certain services were attempting to communicate through legacy ports that were not aligned with the updated platform configuration following the migration. 4. **Platform Configuration Updated:** The required ports were added to the updated platform configuration, restoring connectivity for the affected services. 5. **Service Recovery Validation:** Technical teams validated functionality across impacted applications and confirmed that service communication and customer-facing functionality had returned to normal operation. ## Future Preventative Measures The following improvements have been identified to further reduce the risk of similar incidents in the future: 1. **Migration Compatibility Validation:** Review and strengthen validation processes for infrastructure changes and platform migrations to help identify service configuration mismatches before deployment, reducing the risk of connectivity issues caused by legacy endpoint or port configurations.