ControlUp experienced a minor incident on June 9, 2026 affecting US Region and US Region, lasting 12h 24m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 09, 2026, 09:56 AM UTC
We are currently investigating an issue with Audit logs in the VDI and Desktop applications in the US region only.
- identified Jun 09, 2026, 09:57 AM UTC
The issue has been identified. This is caused by a Microsoft outage.
- monitoring Jun 09, 2026, 08:32 PM UTC
Mitigation efforts have been implemented in the US Region, which have allowed services to begin to recover. We are monitoring the situation and will provide one final update once all services have been confirmed back to normal operation.
- resolved Jun 09, 2026, 10:21 PM UTC
This incident has been resolved
- postmortem Jun 17, 2026, 02:18 PM UTC
| **RCA Owner** | **Andrew Renton** | | --- | --- | | **Priority** | Medium | | **Affected Services** | Audit log | | **Affected Clients** | US clients | | **RCA Reference** | 09/06/2026 | | **Executive Summary** | On 9 June 2026 at approximately 00:50 UTC, ControlUp detected delayed ingestion of audit log entries affecting all customers. The issue was first surfaced via automated alerts, which prompted an R&D investigation. The root cause was identified as an outage in Microsoft Azure's managed Event Grid service within the East US region, which caused increased publish failures and elevated end-to-end delivery latency. This directly impacted the pipeline responsible for writing audit records to the database, resulting in a lag between audit event generation and persistence. A support ticket was raised with Azure at 08:48 UTC and Azure confirmed the outage was affecting multiple customers. The issue was observed as resolved in Azure metrics on 10th June 2026 at 05:58 UTC, with formal mitigation confirmation from Azure Support at 06:30 UTC. Total incident duration was approximately 30 hours. No data loss occurred; all audit log entries were ultimately ingested, albeit with delay. As the root cause resided entirely within an Azure-managed service, no code or configuration changes were required on the ControlUp side. |