ControlUp experienced a critical incident on July 3, 2026 affecting US Region and EMEA Region and 1 more component, lasting 1h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 03, 2026, 07:44 AM UTC
We are currently investigating an issue impacting organizations' ability to access the VDI products. We will provide an update shortly.
- identified Jul 03, 2026, 08:00 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 03, 2026, 08:01 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 03, 2026, 08:54 AM UTC
This incident has been resolved.
- postmortem Jul 10, 2026, 09:52 AM UTC
| **RCA Owner** | _**Andrew Renton**_ | | --- | --- | | **Priority** | High | | **Affected Services** | VDI & DaaS Web Console | | **Affected Clients** | All VDI Customers | | **RCA Reference** | 0001/03/07/2026 | | **Executive Summary** | OnJul 3, 2026, customers using the VDI & DaaS Web Console experienced a temporary loss of visibility into real-time and historical monitoring data. The issue was caused by an unexpected service interruption in the Monitor Proxy layer following automated operating system security updates on production servers. Customer data was not lost; the incident affected data visibility only. The engineering team restored service by redeploying the affected Monitor Proxy services, and customers were able to see their data again shortly after recovery. To reduce the risk of recurrence, automatic unattended OS package upgrades have been disabled on the production Monitor Proxy servers, related hardening automation has been updated, and additional resiliency improvements are being evaluated. |
- postmortem Jul 10, 2026, 10:02 AM UTC
| **RCA Owner** | _**Andrew Renton**_ | | --- | --- | | **Priority** | High | | **Affected Services** | VDI & DaaS Web Console | | **RCA Reference** | 03/07/2026 | | **Executive Summary** | OnJul 3, 2026, customers using the VDI & DaaS Web Console experienced a temporary loss of visibility into real-time and historical monitoring data. The issue was caused by an unexpected service interruption in the Monitor Proxy layer following automated operating system security updates on production servers. Customer data was not lost; the incident affected data visibility only. The engineering team restored service by redeploying the affected Monitor Proxy services, and customers were able to see their data again shortly after recovery. To reduce the risk of recurrence, automatic unattended OS package upgrades have been disabled on the production Monitor Proxy servers, related hardening automation has been updated, and additional resiliency improvements are being evaluated. |