Flexera One - IT Visibility - APAC - Data Explorer Service Disruption

Update timeline

1. investigating Jun 18, 2026, 02:44 PM UTC

   Incident Description: We are investigating an issue affecting Data Explorer functionality for Flexera One IT Visibility in the APAC region. As a result, customers may experience failures when running queries, delays in retrieving data, and issues accessing related features that depend on Data Explorer. Priority: P2 Restoration Activity: Our technical teams are actively investigating a disruption impacting upstream services required for Data Explorer. Recovery efforts are focused on restoring connectivity between dependent services and stabilizing query processing and data access. We will continue to monitor progress and provide updates as more information becomes available.

2. resolved Jun 18, 2026, 03:06 PM UTC

   This issue has been resolved. Data Explorer functionality in the APAC region has been fully restored following the identification and rollback of a recent service change that was impacting service communication. All services have been validated and are operating as expected. A full post-incident report, including detailed root cause and preventative measures, will be shared in the coming days.

3. postmortem Jul 07, 2026, 06:33 AM UTC

   **Description:** Flexera One – IT Visibility – APAC – Data Explorer Service Disruption **Timeframe:** June 17, 2026, 6:47 PM PDT – June 18, 2026, 7:46 AM PDT **Incident Summary** During the incident window, customers experienced issues with Data Explorer functionality for Flexera One IT Visibility in the APAC region. Affected customers experienced failures when running queries, delays and errors when retrieving data, and issues accessing related functionality that depends on Data Explorer. Some dependent functionality, including reporting and connections, did not operate as expected. Technical teams investigated and identified that Data Explorer and related services were unable to successfully communicate with required internal services used for request processing. This resulted in query execution failures and degraded behavior for related data and connection workflows. As part of the recovery effort, technical teams identified the issue and reverted the changes to restore the previous stable state. Following the rollback, connectivity between services was restored, and Data Explorer, query execution, reporting, connections, and related functionality returned to expected behavior. By June 18, 2026, at approximately 7:46 AM PDT, services had been validated and confirmed to be operating normally across APAC. The impact was limited to APAC. North America and Europe remained unaffected throughout the incident. **Root Cause** The issue occurred during an ongoing migration of internal platform services, where services were being moved incrementally to a new platform. During this activity, a change introduced while migrating a majority of dependent services caused a disruption in service-to-service connectivity. This impacted downstream components that rely on those services for request processing. The issue was not observed during validation performed before and after the migration activity. After the connectivity disruption occurred, Data Explorer and related services were unable to successfully communicate with the required internal services. This caused failures when running queries, delays and errors when retrieving data, and issues with dependent functionality including reporting and connections. **Remediation Actions** The following actions were taken during the incident response: 1. **Incident Investigation Initiated:** Technical teams investigated reports of Data Explorer issues affecting Flexera One IT Visibility in the APAC region. 2. **Impact Scope Reviewed:** The issue was confirmed to affect APAC. North America and Europe were reviewed and confirmed to be operating as expected. 3. **Dependent Functionality Reviewed:** Technical teams reviewed related functionality, including query execution, reporting, and connection-related workflows. 4. **Service Communication Issue Identified:** Technical teams identified that downstream services were unable to successfully communicate with required internal services. 5. **Migration Activity Reviewed:** Technical teams determined that the issue occurred during an ongoing migration of internal platform services to a new platform. 6. **Changes Reverted:** The changes introduced during the migration activity were reverted to restore the previous stable state. 7. **Service Connectivity Restored:** Following the rollback, connectivity between services was restored. 8. **Service Recovery Validated:** Technical teams validated Data Explorer, query execution, reporting, connections, and related functionality and confirmed that services were operating normally in APAC. **Future Preventative Measures** This incident highlighted the importance of planning, visibility, and validation for internal platform migration activities that may affect customer-facing services or downstream dependencies. Based on the investigation, the following follow-up activities are being reviewed: * **Migration Assessment and Planning:** Review assessment and planning practices for internal platform migration activities to better identify downstream dependencies, required validation steps, impacted workflows, and any potential customer impact before migration work is performed. * **Scheduled Maintenance Planning:** Ensure internal platform migration activities with any potential customer impact are planned and communicated through a scheduled maintenance window. * **Validation Coverage Review:** Review validation practices for migration activity to help ensure testing covers dependent customer-facing workflows before and after migration work is performed, especially where prior validation does not identify service-to-service connectivity issues.