ControlUp Outage History

Started Oct 23, 2026, 07:27 PM UTC· resolved Oct 23, 2026, 08:06 PM UTC

1. investigating Oct 23, 2026, 07:27 PM UTC

   We are currently investigating an issue causing DEX logins to fail. More information will be shared as it becomes available.

2. monitoring Oct 23, 2026, 07:42 PM UTC

   A fix has been implemented, and we are monitoring the results as all systems recover.

3. resolved Oct 23, 2026, 08:06 PM UTC

   This incident has been resolved. All systems are back to normal operation.

Read the full incident report →

Started Oct 01, 2026, 09:33 AM UTC· resolved Oct 01, 2026, 10:02 AM UTC

1. investigating Oct 01, 2026, 09:33 AM UTC

   We are investigating an issue with publicly shared forms in the Workflow application. We will provide updates as we investigate.

2. resolved Oct 01, 2026, 10:02 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 22, 2026, 11:33 AM UTC· resolved Sep 22, 2026, 11:56 AM UTC

1. investigating Sep 22, 2026, 11:33 AM UTC

   We are currently investigating an issue impacting some EU organizations, preventing standard logins. Users are presented with a "Network problem" error message. Updates will be provided as we learn more.

2. monitoring Sep 22, 2026, 11:39 AM UTC

   We identified the issue, and a fix was implemented. We are monitoring the results and will provide another update when the incident has been confirmed as resolved.

3. resolved Sep 22, 2026, 11:56 AM UTC

   This incident has been resolved, and performance is back to normal operation.

Read the full incident report →

Started Sep 06, 2026, 11:43 AM UTC· resolved Sep 06, 2026, 11:56 AM UTC

1. investigating Sep 06, 2026, 11:43 AM UTC

   We are currently undergoing maintenance on the DEX platform. All services will return to normal at the conclusion of the maintenance window.

2. identified Sep 06, 2026, 11:45 AM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary

3. monitoring Sep 06, 2026, 11:47 AM UTC

   The scheduled maintenance has been completed.

4. resolved Sep 06, 2026, 11:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 07:57 AM UTC· resolved Aug 20, 2026, 07:23 AM UTC

1. investigating Aug 18, 2026, 07:57 AM UTC

   We are currently investigating this issue.

2. monitoring Aug 18, 2026, 09:00 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 20, 2026, 07:23 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 02, 2026, 05:34 PM UTC· resolved Aug 02, 2026, 09:23 PM UTC

1. investigating Aug 02, 2026, 05:34 PM UTC

   Some organizations in the US region may experience performance and availability issues with their ControlUp Desktops tenants and other areas that depend on these resources. Microsoft Azure support alerted us to performance issues a short time ago, and we confirmed several impacts across the region. They are actively working on restoring access and will share updates with us as they progress. We will provide updates here as we continue to monitor the situation and react accordingly to restore the impacted areas.

2. identified Aug 02, 2026, 06:41 PM UTC

   The issue has been identified and a fix is being implemented

3. monitoring Aug 02, 2026, 08:04 PM UTC

   A fix has been implemented, and we are monitoring the results as performance returns to normal. We will close this incident after verifying that everything is back to normal operation.

4. resolved Aug 02, 2026, 09:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 26, 2026, 08:17 PM UTC· resolved Jul 26, 2026, 10:36 PM UTC

1. investigating Jul 26, 2026, 08:17 PM UTC

   We are currently investigating an issue impacting organizations' ability to access the VDI products. We will provide an update shortly.

2. monitoring Jul 26, 2026, 10:17 PM UTC

   A fix had been implemented and we are monitoring the status closely.

3. resolved Jul 26, 2026, 10:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 03, 2026, 07:44 AM UTC· resolved Jul 03, 2026, 08:54 AM UTC

1. 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.

2. identified Jul 03, 2026, 08:00 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 03, 2026, 08:01 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jul 03, 2026, 08:54 AM UTC

   This incident has been resolved.

5. 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. |

6. 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. |

Read the full incident report →

Started Jun 29, 2026, 01:22 PM UTC· resolved Jun 29, 2026, 10:50 PM UTC

1. investigating Jun 29, 2026, 01:22 PM UTC

   We are currently investigating an issue causing some organizations to encounter an error when drilling into device details from the Devices pane.

2. identified Jun 29, 2026, 02:43 PM UTC

   The issue has been identified, and a workaround is being validated

3. monitoring Jun 29, 2026, 09:31 PM UTC

   A workaround has been confirmed and will be distributed accordingly. The permanent fix will be deployed during the next maintenance cycle. We are monitoring the status before closing this incident

4. resolved Jun 29, 2026, 10:50 PM UTC

   This incident has been resolved. The RCA will be published at the conclusion of the investigation.

Read the full incident report →

Started Jun 23, 2026, 02:28 PM UTC· resolved Jun 23, 2026, 04:20 PM UTC

1. investigating Jun 23, 2026, 02:28 PM UTC

   We are currently investigating an issue with a 3rd party service outage impacting the availability of the AI Assistant inside the DEX Platform.

2. identified Jun 23, 2026, 02:42 PM UTC

   The issue has been identified, and a fix is being implemented.

3. monitoring Jun 23, 2026, 03:13 PM UTC

   A fix has been implemented, and we are monitoring the results as services recover.

4. resolved Jun 23, 2026, 04:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 16, 2026, 10:04 AM UTC· resolved Jun 16, 2026, 08:13 PM UTC

1. investigating Jun 16, 2026, 10:04 AM UTC

   We are currently investigating this issue.

2. investigating Jun 16, 2026, 10:09 AM UTC

   We are continuing to investigate this issue.

3. identified Jun 16, 2026, 03:06 PM UTC

   The issue has been identified and is related to an ongoing issue with Microsoft Azure. The Microsoft team are working towards a resolution.

4. monitoring Jun 16, 2026, 07:35 PM UTC

   A fix has been implemented and we are monitoring the results to ensure performance as returned to optimal status.

5. resolved Jun 16, 2026, 08:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2026, 11:54 PM UTC· resolved Jun 11, 2026, 10:47 AM UTC

1. identified Jun 10, 2026, 11:54 PM UTC

   We have identified an issue causing streaming data delays for some US customers. The root cause has been identified, and a permanent fix will be applied during a maintenance window to start at approximately 2 am EST/11 pm PST and lasting for approximately 2 hours. During the deployment, affected customers will notice that recent streaming data will not be available. Data will fill back in over time once the fix has been successfully deployed.

2. monitoring Jun 11, 2026, 08:15 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jun 11, 2026, 10:47 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 09, 2026, 09:56 AM UTC· resolved Jun 09, 2026, 10:21 PM UTC

1. 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.

2. identified Jun 09, 2026, 09:57 AM UTC

   The issue has been identified. This is caused by a Microsoft outage.

3. 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.

4. resolved Jun 09, 2026, 10:21 PM UTC

   This incident has been resolved

5. 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. |

Read the full incident report →

Started Jun 08, 2026, 04:00 AM UTC· resolved Jun 08, 2026, 04:00 AM UTC

1. resolved Jun 08, 2026, 04:00 AM UTC

   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 [email protected] or your account team and we’ll assist you directly.

2. postmortem Jul 17, 2026, 01:48 PM UTC

   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.

Read the full incident report →

Started Jun 07, 2026, 07:54 PM UTC· resolved Jun 08, 2026, 12:05 AM UTC

1. investigating Jun 07, 2026, 07:54 PM UTC

   We are currently experiencing an issue with Data Streaming in all regions.

2. identified Jun 07, 2026, 08:09 PM UTC

   The issue has been identified, and we are implementing a fix. There may be some duplication of data during this period, which will return to normal during the restoration process.

3. monitoring Jun 07, 2026, 10:43 PM UTC

   A fix has been implemented in all regions and data is uploading properly. The data gap will continually close over the next few hours.

4. resolved Jun 08, 2026, 12:05 AM UTC

   Systems are running normally, and data gaps are continuing to fill in completely.

Read the full incident report →

Started Jun 02, 2026, 09:16 AM UTC· resolved Jun 02, 2026, 12:03 PM UTC

1. identified Jun 02, 2026, 09:16 AM UTC

   We are aware of an issue affecting AI Assistant. We have identified the issue and will provide updates as the investigation progresses

2. monitoring Jun 02, 2026, 10:47 AM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Jun 02, 2026, 11:04 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Jun 02, 2026, 12:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 11, 2026, 07:44 PM UTC· resolved May 11, 2026, 11:05 PM UTC

1. investigating May 11, 2026, 07:44 PM UTC

   We are currently investigating an issue with third-party services (Azure API) that may result in some AI Assistant query errors. The query should succeed on a retry. We will provide updates as we learn more.

2. monitoring May 11, 2026, 10:21 PM UTC

   We have been informed that all third-party services have recovered and we are monitoring our systems to validate that everything is back to operational. One final update will be sent once confirmed.

3. resolved May 11, 2026, 11:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2026, 01:12 PM UTC· resolved May 08, 2026, 01:16 PM UTC

1. investigating May 07, 2026, 01:12 PM UTC

   We are currently experiencing a partial outage affecting some customers in Ireland, where one‑time passwords (OTP) for the DEX Portal may not be delivered via SMS. Other authentication and login methods are operating normally and are not impacted.

2. identified May 07, 2026, 06:08 PM UTC

   The issue has been identified with service providers in the EMEA regions. We are working closely with third-party services to ensure a speedy recovery. Alternative authentication methods (other than SMS) are still operating normally.

3. monitoring May 07, 2026, 11:31 PM UTC

   A fix has been implemented by the service providers, and we are monitoring the results.

4. resolved May 08, 2026, 01:16 PM UTC

   This incident has now been resolved.

Read the full incident report →

Started Apr 27, 2026, 05:10 PM UTC· resolved Apr 28, 2026, 12:37 AM UTC

1. investigating Apr 27, 2026, 05:10 PM UTC

   We are currently investigating an issue causing some DEX environments to be inaccessible.

2. investigating Apr 27, 2026, 05:38 PM UTC

   We are still investigating the issue. Some environments may still experience intermittent access issues to the DEX platform.

3. identified Apr 27, 2026, 06:07 PM UTC

   The issue has been identified. We are currently working on a fix to deploy to all environments. Some DEX environments may still be impacted at this time. We will provide another update once the fix is ready for deployment.

4. monitoring Apr 27, 2026, 08:03 PM UTC

   A fix has been implemented, and we are monitoring the results as we see access being restored across all environments. A final update will be posted once everything is confirmed.

5. resolved Apr 28, 2026, 12:37 AM UTC

   This incident has been resolved.

6. postmortem May 08, 2026, 01:34 PM UTC

   On the evening of April 27, 2026, some customers experienced intermittent issues when logging in or accessing resources. The disruption lasted approximately 5.5 hours, from 22:00 to 03:12 \(GMT\+2\). The issue was caused by an internal service becoming unstable, which triggered a surge of automated retry attempts that overwhelmed a supporting system. Our teams responded immediately and put the following protective measures in place: * **Added automatic safeguards** to stop failing requests from piling up and spreading to other services * **Reduced wait times** so requests no longer blocked the system for extended periods * **Limited the number of automatic retries** to prevent traffic from multiplying during the disruption * **Stopped retries on requests that could never succeed**, reducing unnecessary load * **Added safety checks** to prevent one failure from triggering thousands of others * **Doubled the capacity** of the affected system to handle higher demand * **Improved logging** to help diagnose issues faster in the future * **Added temporary data storage** so the system can continue serving customers even during disruptions Full service was restored at 03:12 \(GMT\+2\) on April 28, with no further issues reported. Most customer data continued to be served during the disruption, limiting the overall impact.

Read the full incident report →

Started Apr 21, 2026, 03:47 PM UTC· resolved Apr 21, 2026, 05:13 PM UTC

1. investigating Apr 21, 2026, 03:47 PM UTC

   We are currently investigating an issue impacting some organizations' ability to access the VDI products. We will provide another update shortly.

2. monitoring Apr 21, 2026, 04:19 PM UTC

   We identified the issue, and a fix has been implemented. We are monitoring the results.

3. resolved Apr 21, 2026, 05:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 13, 2026, 06:19 PM UTC· resolved Mar 13, 2026, 08:15 PM UTC

1. investigating Mar 13, 2026, 06:19 PM UTC

   We are currently investigating an issue causing issues logging into the DEX platform. We will provide updates as soon as we learn more.

2. identified Mar 13, 2026, 07:08 PM UTC

   The issue has been identified, and a fix is being implemented. Another update will be provided once a fix is in place.

3. monitoring Mar 13, 2026, 07:41 PM UTC

   A fix has been implemented, and we are monitoring the results. We will mark the issue resolved once confirmed.

4. resolved Mar 13, 2026, 08:15 PM UTC

   This incident has been resolved, and all services are back to normal operation.

Read the full incident report →

Started Mar 04, 2026, 10:14 PM UTC· resolved Mar 05, 2026, 12:31 AM UTC

1. investigating Mar 04, 2026, 10:14 PM UTC

   We are currently investigating a stability issue that may cause some users to encounter access issues to several static pages in the DEX platform. More information will be shared as we learn more.

2. identified Mar 04, 2026, 10:37 PM UTC

   The issue has been identified. A fix is being worked on and will be implemented as soon as possible.

3. monitoring Mar 04, 2026, 10:57 PM UTC

   The fix has been implemented, and we are monitoring the results as all services return to normal operation.

4. resolved Mar 05, 2026, 12:31 AM UTC

   This incident is resolved, and all services have returned to normal.

Read the full incident report →

Started Feb 18, 2026, 04:20 AM UTC· resolved Feb 18, 2026, 06:26 AM UTC

1. investigating Feb 18, 2026, 04:20 AM UTC

   We are currently investigating an issue where the Synthetic Monitoring web console shows that the Service is temporarily unavailable.

2. monitoring Feb 18, 2026, 05:48 AM UTC

   We have identified the issue and immediately deployed a fix. We are monitoring the services as everything returns to normal operation now.

3. resolved Feb 18, 2026, 06:26 AM UTC

   This incident has been resolved and all operations are back to normal.

Read the full incident report →

Started Feb 08, 2026, 03:39 PM UTC· resolved Feb 08, 2026, 07:59 PM UTC

1. investigating Feb 08, 2026, 03:39 PM UTC

   We are currently investigating an issue causing some tenants in multiple regions to appear down. More information to follow.

2. identified Feb 08, 2026, 04:20 PM UTC

   The issue has been identified as related to the data pipeline maintenance. We reverted the changes and are testing the fix at this time. We expect to have tenants begin to return to online status quickly.

3. monitoring Feb 08, 2026, 04:52 PM UTC

   A fix has been confirmed and implemented across all tenants. We are monitoring the results as performance returns to normal.

4. resolved Feb 08, 2026, 07:59 PM UTC

   This incident has been resolved, and all performance has returned to normal.

Read the full incident report →

Started Jan 26, 2026, 05:00 PM UTC· resolved Jan 26, 2026, 06:07 PM UTC

1. monitoring Jan 26, 2026, 05:00 PM UTC

   We are currently experiencing an issue with certain organizations being unable to access their tenants through DEX. This is related to the critical hot fix that was deployed a short time ago. The fix is taking longer to deploy to all organizations, but access will be restored shortly. Thank you for your patience.

2. resolved Jan 26, 2026, 06:07 PM UTC

   This incident has been closed, and all tenants are back to operational status.

Read the full incident report →