Flexera One - IT Visibility - APAC - Inventory upload status reporting is down

Update timeline

1. investigating Mar 16, 2026, 04:06 AM UTC

   Incident Description: We are currently investigating an issue affecting inventory upload status reporting within Flexera One – IT Visibility (ITV) for customers in the APAC region. Inventory ingestion is processing successfully; however, the system responsible for reporting upload processing status is failing. As a result, inventory uploads may incorrectly appear as “Timed Out” even though the underlying data ingestion may have completed successfully. Priority: P3 Restoration Activity: Our technical teams are actively investigating the issue impacting upload status reporting and are working to identify the underlying cause. We are monitoring the situation closely and will provide further updates as progress is made.

2. resolved Mar 16, 2026, 06:17 AM UTC

   Our teams identified the issue as an incorrect routing configuration and implemented the necessary updates to correct it. Following the change, routing behavior, traffic flow, and overall service health were validated, and all components are now confirmed to be operating normally.

3. postmortem Mar 30, 2026, 03:41 AM UTC

   **Description:** Flexera One – IT Visibility – APAC – Inventory Upload Status Reporting Failure **Timeframe:** March 15, 2026, 8:20 PM PDT – March 15, 2026, 11:08 PM PDT **Incident Summary** On March 15, 2026, at approximately 8:20 PM PDT, technical teams identified an issue affecting inventory upload status reporting in the APAC region. During this period, inventory uploads continued to be ingested and processed, but the status reporting associated with those uploads did not update correctly. As a result, affected uploads could appear as timed out within the application even though processing was continuing successfully. Technical teams immediately began investigating the issue and worked to isolate the source of the reporting failure. The investigation confirmed that the issue was limited to the APAC region and was specific to the status reporting path rather than the underlying inventory upload processing itself. By March 15, 2026, at approximately 11:08 PM PDT, the underlying issue had been corrected and service behavior was validated as functioning normally. Following verification that traffic flow and status reporting had returned to expected behavior, the incident was considered resolved. **Root Cause** The incident was caused by an incorrect routing configuration within the service communication path used for inventory upload status reporting. This prevented status-related requests from reaching the intended service endpoint, which caused status reporting to fail even though the underlying upload processing continued to operate normally. Further investigation determined that the deployed configuration did not match the intended configuration. **Remediation Actions** The following actions were taken during the incident response: 1. Incident Detection and Response Initiated: Technical teams were notified of the issue and began investigating the failure affecting inventory upload status reporting in APAC. 2. Impact Isolation: It was confirmed that the issue was limited to the APAC region and that inventory uploads were continuing to process successfully while status reporting was not updating correctly. 3. Configuration Review and Validation: The relevant service configuration was reviewed to identify where status-related requests were not reaching the intended endpoint. 4. Corrective Configuration Update: A corrective routing change was applied to direct traffic to the proper service endpoint used for status communication. 5. Service Restoration Verification: Following the corrective update, service traffic and status reporting behavior were verified as functioning as expected. **Future Preventative Measures** This incident highlighted the importance of ensuring configuration consistency and correct service communication paths within the platform. Based on this experience, the following measures are being applied: 1. Configuration Consistency Controls: We are reviewing controls to ensure deployed configurations remain aligned with intended configuration standards. 2. Post-Change Validation: We are evaluating validation steps following configuration changes to ensure service communication paths are functioning as expected.