We are investigating an issue affecting Azure eastus2 region
The configuration change was reverted and we do not observe impact anymore. The ClickHouse Cloud team will work on preventing similar situations in future.
The latest update from ClickHouse Cloud.
State
Resolved
Started
39 d ago
2026-09-23 15:28 UTC
Lasted
30 min
until 2026-09-23 15:59 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
8 min 26%
Monitoring
22 min 74%
Updates
Times in UTCAs posted by ClickHouse Cloud
The configuration change was reverted and we do not observe impact anymore. The ClickHouse Cloud team will work on preventing similar situations in future.
We have identified the cause of the disruption and already applying the remediation. We will monitor for recovery and send update as soon as it is fully recovered.
**Investigating delays to provisioning and autoscaling** We are investigating an issue affecting our Kubernetes infrastructure in Azure eastus2 region. Some customers may experience delays with provisioning and autoscaling of ClickHouse clusters. We are working closely with Azure support to restore normal behavior. We’ll provide another update within 30 minutes, or sooner if we have more information.
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
59% shorter than 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