Description: Flexera One - IT Asset management - APAC - Access disruption

Timeframe: August 18, 2026, 2:10 AM PDT to August 18, 2026, 4:26:03 AM PDT

‌

Incident Summary

‌

On Tuesday, August 18, 2026, at 2:10 AM PDT , Flexera identified an issue affecting the Flexera One APAC Production environment that prevented customers from accessing Flexera One services. During the impact window, customers experienced login failures, session refresh failures, and issues retrieving user-related application data, resulting in widespread service access unavailability across the platform.

Initial investigation indicated that the impact was limited to IT Asset Management. Further analysis determined that the issue involved a shared platform service supporting authentication and authorization across Flexera One, resulting in a broader impact across the APAC environment.

Our technical teams identified an incorrect infrastructure scheduling configuration that prevented a critical platform service from operating as intended. The configuration was corrected, restoring the affected services. Following remediation, health checks returned successfully, application login and navigation functionality recovered, and teams completed post-restoration validation.

The environment was subsequently confirmed healthy and placed under continued monitoring to ensure ongoing stability.

‌

Root Cause

‌

The incident was caused by an incorrect infrastructure scheduling configuration within a critical shared identity and access service. The configuration prevented the service from being scheduled onto the intended infrastructure, resulting in service unavailability and failures affecting authentication and authorization requests.

‌

Remediation Actions

‌

Our teams performed the below actions to restore the services to normalcy:

• Configuration Correction: Corrected the infrastructure scheduling configuration affecting the impacted platform service.

• Service Restoration: Restored the affected platform services and confirmed successful health checks.

• Post-Restoration Validation: Performed automated health checks and platform validation to confirm application login, navigation, and related functionality had recovered.

• Continued Monitoring: The environment was monitored following restoration to confirm ongoing platform stability.

‌

Future Preventative Measures

‌

• Pre-Deployment Validation: Implement additional validation checks for infrastructure scheduling and placement configurations.

• Deployment Safeguards and Resiliency Controls: Review and strengthen deployment safeguards, configuration governance, and resiliency controls to prevent configuration mismatches from impacting service availability.

• Expanded Post-Change Verification: Review and enhance the post-deployment and post-maintenance validation processes to ensure critical platform services are functioning correctly following infrastructure changes.