Description: Flexera One – APAC – Login Issue
Timeframe: February 24, 2026, 07:33 AM PST to February 24, 2026, 10:50 PM PST
Incident Summary
On Tuesday, February 24, 2026, at 07:33 AM PST , our teams identified login failures affecting customers attempting to access Flexera One in the APAC region. The affected users encountered authentication errors during login, preventing access to the platform and associated workflows.
Initial investigation confirmed that the core authentication infrastructure and identity services were operating as expected. Further analysis isolated the issue to the API gateway layer, where requests were failing due to connection issues affecting specific backend services. As a result, authentication calls and dependent APIs returned errors when routed through the gateway.
Our technical teams reviewed the gateway routing configuration and discovered that the affected APAC services were using a specialized gateway path configured with a non-standard port. Traffic using this configuration encountered handshake failures at the gateway layer. To restore service, configuration updates were applied to the API gateway, and the impacted service endpoints were migrated to standard HTTPS communication over the recommended port. After the updated routing configuration was deployed and validated, authentication requests and dependent APIs returned to normal operation. Login access to Flexera One was fully restored, and the incident was closed following confirmation of platform stability.
Root Cause
The incident was caused by a gateway routing configuration that failed to properly handle secure service communication for certain APAC endpoints.
Some APAC services were configured to communicate through the API gateway using a non-standard port. Requests routed through this configuration experienced handshake failures within the gateway layer, which prevented authentication-related API calls from completing successfully. As a result, login attempts and certain backend service calls failed.
Contributing Factors
Remediation Actions
The following remediation steps were implemented to restore service functionality:
Future Preventative Measures