We are investigating an issue with CH servers in Azure germanywestcentral region
The underlying AZ has recovered and we are fully back online. Since ClickHouse cloud architecture uses 3 AZs we were operational during this outage but there might have been some degradations. Azure support shared the details of the issue as following- Between 12:04 UTC and 17:46 UTC on 22 September 2022, a platform issue resulted in an impact to the Virtual Machines (VMs) and Virtual Machine Scale Sets (VMSS) in Germany West Central. Customers may have experienced their virtual machines becoming unresponsive, restarting unexpectedly, or being temporarily unavailable during the impact window.
The latest update from ClickHouse Cloud.
State
Resolved
Started
40 d ago
2026-09-22 13:19 UTC
Lasted
5 h 6 min
until 2026-09-22 18:25 UTC
Worst impact
Degraded
Timeline
8 updatesInvestigating
1 h 38 min 32%
Identified
29 min 9%
Monitoring
2 h 59 min 59%
Updates
Times in UTCAs posted by ClickHouse Cloud
The underlying AZ has recovered and we are fully back online. Since ClickHouse cloud architecture uses 3 AZs we were operational during this outage but there might have been some degradations. Azure support shared the details of the issue as following- Between 12:04 UTC and 17:46 UTC on 22 September 2022, a platform issue resulted in an impact to the Virtual Machines (VMs) and Virtual Machine Scale Sets (VMSS) in Germany West Central. Customers may have experienced their virtual machines becoming unresponsive, restarting unexpectedly, or being temporarily unavailable during the impact window.
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.
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.
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.
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.
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.
Only germanywestcentral Azure region is affected.
We detected an issue with CHC clusters in some Azure regions. ClickHouse cloud team is investigating. Some operations might be degraded.
ClickHouse Cloud in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
14
Median duration
1 h 14 min
This incident
4.2× the median
Other ClickHouse Cloud incidents
All incidentsClickHouse Cloud·Degraded support ticket submission and response
``` Salesforce team resolved the issue that prevented users from logging in. They identified an issue with a recent release that prevented login sessions from being created. Deployed a fix forward, and access is now restored. Users can log in and open their orgs again. https://status.salesforce.com/incidents/20004512 ```
ClickHouse Cloud·Google Cloud Outage
The issue has been resolved. All services are fully operational.
ClickHouse Cloud·Support case creation unavailable
The issue preventing customers from creating and viewing support cases in the ClickHouse Cloud console has been resolved. Support case functionality is working normally again. If you couldn’t open a case during the affected window, please submit it again from the console.
ClickHouse Cloud·Streaming ClickPipes degradation in AWS eu-central-1 region
Remediation was applied and we don't see signs of degradation anymore. Team will continue monitoring and investigating the root cause.
ClickHouse Cloud·Some ClickPipes CDC pipes paused and can't be resumed
All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future.
Follow ClickHouse Cloud
Your coding agent knows when ClickHouse Cloud is down, and tells you when a failure is theirs, not yours. You can also get ClickHouse Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "clickhouse" and tell me if ClickHouse Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=clickhouse/feed subscribe https://outages.cc/feed.xml?providers=clickhouseFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane