Resolved -
Our teams have completed the validation for all remaining organizations and confirmed that services have returned to normal. The incident has been closed, and additional details will be shared in a post-mortem report.
Apr 3, 23:13 PDT
Update -
Our technical teams have completed further validation and confirmed that newly submitted data is now flowing as expected for the affected processing path. Based on this validation, retroactive replay of previously missed messages is not required. Recovery efforts are now focused on confirming full restoration of the remaining impact, and some customers may continue to experience temporary delays until that validation is complete.
Apr 3, 11:08 PDT
Update -
Our technical teams are continuing to validate the replay approach required for reingestion of previously missed messages. Newly submitted inventory packages are processing as expected, and recovery efforts for missed messages remain actively in progress.
Apr 3, 05:34 PDT
Update -
Our technical teams have completed generation of the retroactive messages needed for recovery and are now validating the replay approach before reingestion begins. This work is being carried out carefully to minimize excessive downstream strain during recovery. Newly submitted inventory packages continue to process as expected, while recovery for missed messages remains in progress.
Apr 2, 09:30 PDT
Update -
Our technical teams continue recovery efforts following the hotfix, and newly submitted inventory packages are progressing through processing as expected. Recovery work is currently focused on addressing missed messages from the affected period and validating the backfill approach for those items. As this work continues, some customers may still experience delays in processing.
Apr 1, 09:15 PDT
Update -
Backlog processing continues to progress at a steady rate following the hotfix implementation. Our teams are actively monitoring the recovery to ensure complete resolution and system stability.
Mar 31, 23:58 PDT
Update -
Our technical teams have identified the root cause and implemented a hotfix to restore normal data notification flow across the affected regions. Recovery activity is now focused on replaying missed notifications generated during the affected period. As this work continues, some customers may still experience residual delays and timeouts while backlog processing completes.
Mar 31, 15:39 PDT
Identified -
Incident Description: We are currently investigating an issue affecting third-party inventory imports in Flexera One IT Visibility across all regions. As a result, some customers may experience delays in inventory processing and timeouts during imports.
Priority: P2
Restoration Activity: Our technical teams have identified the issue and are actively implementing mitigation steps to restore normal processing. Recovery actions are underway across the affected processing path. As processing resumes, some customers may continue to experience residual delays and timeouts while backlog processing is worked through.
Mar 31, 15:12 PDT