CU4VDI Database Cleanup Incident

Incident Report for ControlUp Status Page

Postmortem

During routine database maintenance, a cleanup process incorrectly removed some historical reporting data. This affected some aggregated reports, primarily 1-hour and 1-day reporting views, and may have resulted in incomplete historical trends for a subset of customers. Live platform operation was not the primary area of impact.

Our engineering team identified the issue through investigation, rolled back the affected deployment, restored data processing across all regions by 07:30 UTC on 8 June, and completed follow-up duplicate-data cleanup over the following days.

We are strengthening safeguards so that destructive maintenance actions are not based on a single approximate metadata value. Follow-up improvements include additional validation checks, targeted test coverage, enhanced anomaly monitoring, expanded operational logging, and improved internal communication for production maintenance and recovery work.

Posted Jul 17, 2026 - 13:48 UTC

Resolved

What happened
Our routine VDI database maintenance jobs — which have run reliably for years — depend on the underlying platform to accurately report the contents of each data table. A recently introduced third-party (Microsoft) platform bug caused certain tables to be incorrectly reported as empty. As a result, our cleanup processes removed data that should have been retained.

What we’ve done
As soon as we identified the issue, we launched a full recovery effort and were able to restore the majority of the affected data (VDI). Unfortunately, a limited number of tables and partitions could not be recovered.

What this means
The impacted data ranges from approximately two months to one year old. The specific records affected vary by organization, so the scope is not identical across accounts. Your current, recent, and ongoing data is unaffected, and your environment is operating normally.

What happens next
We’ve implemented safeguards to prevent this specific failure from recurring, and we’re continuing to monitor closely. If you’d like help understanding exactly which data was affected in your environment, or to discuss next steps, please reach out to support@controlup.com or your account team and we’ll assist you directly.

Posted Jun 08, 2026 - 04:00 UTC