Google Cloud Outage
The issue has been resolved. All services are fully operational.
The latest update from ClickHouse Cloud.
State
Resolved
Started
12 d ago
2026-10-20 07:39 UTC
Lasted
6 h 44 min
until 2026-10-20 14:23 UTC
Worst impact
Degraded
Timeline
6 updatesIdentified
5 h 25 min 80%
Monitoring
1 h 20 min 20%
Updates
Times in UTCAs posted by ClickHouse Cloud
The issue has been resolved. All services are fully operational.
We do not see any current impact on clickpipes or ClickHouse services, with full service restored. Google has not marked the incident as resolved, so we continue to monitor.
The zone is recovering. Clickpipes is fully restored but we continue to monitor until google reports all issues have been resolved.
This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: [https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj "https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj") Currently only zone B is impacted. Clusters in this region should be operational - accepting reads and writes, but provisioning of new services currently blocked until this zone is operational.
This is attributed to a Google outage in europe-west2. Latest updates from Google can be found at: [https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj "https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj") Currently only zone B is impacted. We are migrating workloads away from this zone.
Google Cloud has reported that multiple services are experiencing issues in the europe-west2 region. We are working closely with Google support to restore normal behavior and will provide an update as soon as 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
5.5× 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·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.
ClickHouse Cloud·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.
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