ClickHouse incident
We are investigating an issue with CH servers in Azure germanywestcentral region
Resolved after 5 hours 6 minutes, affecting germanywestcentral and eastus2 and 1 more, on September 22, 2026.
Azure support shared they are working on fixing the underlying issue, we started seeing some recovery but the incident is not completely resolved yet. We are working with Azure to get this fixed as soon as possible.
Affected components
Update timeline
- investigating Sep 22, 2026, 01:19 PM UTC
We detected an issue with CHC clusters in some Azure regions. ClickHouse cloud team is investigating. Some operations might be degraded.
- investigating Sep 22, 2026, 01:21 PM UTC
Only germanywestcentral Azure region is affected.
- investigating Sep 22, 2026, 01:31 PM UTC
Only one Availability zone is affected in germanywestcentral Azure region. The problem affects internal component (ClickHouse Keepers). Some ClickHouse Services in this region may see increased latency on inserts or DDL queries.
- investigating Sep 22, 2026, 01:49 PM UTC
The problem is caused by Azure outage in the germanywestcentral region. ClickHouse Cloud team is working with Azure support. Impact: • New ClickHouse services can't be provisioned (appear as stuck in UI). • Some services may experience higher latency due to reduced capacity.
- identified Sep 22, 2026, 02:57 PM UTC
The Azure team is working on resolution of the issue. The ClickHouse Cloud team will relay any updates related to ClickHouse clusters operation. An excerpt from Azure incident status: "As per our investigation, we believe this stemmed from multiple underlying storage systems becoming unavailable at the same time, which led to attached virtual machines becoming unresponsive, restarting unexpectedly, or being temporarily unavailable. "
- monitoring Sep 22, 2026, 03:26 PM UTC
The issue is still present on Azure infrastructure side and ClickHouse Cloud team is actively monitoring for any impact for existing ClickHouse Clusters. Correction on earlier impact description: Provisioning of new instances is expected to work. Operations like autoscaling of the ClickHouse Keeper replicas can be stuck or slow. Latency for insert and DDL queries are not affected, thanks to cross-AZ redundancy.
- monitoring Sep 22, 2026, 05:02 PM UTC
Azure support shared they are working on fixing the underlying issue, we started seeing some recovery but the incident is not completely resolved yet. We are working with Azure to get this fixed as soon as possible.
- resolved Sep 22, 2026, 06:25 PM UTC
The underlying AZ has recovered and we are fully back online.
Your product runs on more than ClickHouse
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services