Flexera One – IT Asset Management – EU – Inventory Uploads Failures

Update timeline

1. investigating Apr 08, 2026, 11:07 AM UTC

   Incident Description: We are investigating an issue impacting inventory data uploads for IT Asset Management (ITAM) in the EU region. Affected customers may experience upload failures and related error messages. Priority: P2 Restoration Activity: Our technical teams are actively investigating the cause and working to restore normal upload processing. We are monitoring the environment closely and will continue to share updates as progress is made toward full restoration.

2. resolved Apr 08, 2026, 02:11 PM UTC

   We have identified the issue affecting inventory uploads in the EU region. The disruption was caused by a service responsible for handling communication between components becoming unavailable following an unexpected system event. The service has since been successfully restored, and inventory uploads are now processing as expected. There has been no data loss, as affected uploads will automatically retry and complete. Our teams are actively monitoring the system to ensure stability as processing returns to normal and are investigating the underlying cause of the event. Additional safeguards are also being implemented to help prevent recurrence.

3. postmortem Apr 22, 2026, 03:43 AM UTC

   **Description:** Flexera One – IT Asset Management – EU – Inventory Upload Failures **Timeframe:** April 7, 2026, 10:53 AM PDT – April 8, 2026, 7:45 AM PDT **Incident Summary** On April 7, 2026, at approximately 10:53 AM PDT, an issue began affecting inventory data uploads for Flexera One IT Asset Management in the EU production environment. During this period, customers in the EU region experienced failures when attempting to upload inventory data, which also resulted in delays in downstream data processing. Technical teams began investigating the issue after reports were received of upload failures affecting the EU region. During the investigation, it was confirmed that the upload endpoint was reachable and responding, while customer upload attempts were still failing. Further analysis continued to identify the source of the disruption and determine why uploads were not being processed successfully. The issue was subsequently identified as a required service in the EU production environment being unexpectedly stopped. As a result, upload requests were not processed successfully during the affected period, which caused authentication failures and prevented data from being received for processing. Once the service was restarted, uploads began processing successfully again and recovery activity was monitored. By April 8, 2026, at approximately 7:45 AM PDT, successful uploads had resumed and the incident was considered resolved. It was confirmed during the incident that there was no data loss, as affected uploads would automatically re-upload after service restoration. Technical teams continued monitoring following restoration to ensure recovery progressed as expected. **Root Cause** The incident was caused by a required service in the EU production environment being unexpectedly stopped. This interruption prevented inventory upload requests from being processed successfully, resulting in authentication failures and no data being received for processing during the affected period. Further analysis is underway to determine the cause of the unexpected service interruption. **Remediation Actions** The following actions were taken during the incident response: 1. Incident Investigation Initiated: Technical teams began investigating reports of inventory upload failures affecting the EU region. 2. Endpoint Behavior Reviewed: Technical teams confirmed that the upload endpoint was reachable and responding while further analysis continued to isolate the source of the failure. 3. Cause Identified: Investigation determined that a required service in the EU production environment had been unexpectedly stopped. 4. Service Restarted: The affected service was restarted in the EU production environment. 5. Upload Recovery Validated: Technical teams confirmed that uploads were processing successfully again following service restoration. 6. Post-Restoration Monitoring Performed: Recovery activity and backlog behavior were monitored after restoration. **Future Preventative Measures** The following follow-up actions were identified during the incident: 1. Automatic Service Restart Measures: We are implementing measures to help ensure the affected service starts automatically in the event of a similar occurrence.