outages.live
Live

ClickHouse Cloud

ClickHouse Cloud is operational

Checked 25 s ago Operational

History

90 days agoToday

Incidents in 90 days

14

Days with an incident

14

Median duration

1 h 14 min

Longest incident

29 h 46 min

Components

24
us-east-1 Operational
90 days agoNo incidentsToday
us-east-2 Operational
90 days agoNo incidentsToday
us-west-2 Operational
90 days agoNo incidentsToday
eu-central-1 Operational
90 days agoNo incidentsToday
eu-west-1 Operational
90 days agoNo incidentsToday
eu-west-2 Operational
90 days agoNo incidentsToday
ap-northeast-1 Operational
90 days agoNo incidentsToday
ap-northeast-2 Operational
90 days agoNo incidentsToday
ap-south-1 Operational
90 days agoNo incidentsToday
ap-southeast-1 Operational
90 days agoNo incidentsToday
ap-southeast-2 Operational
90 days agoNo incidentsToday
il-central-1 Operational
90 days agoNo incidentsToday
ap-east-1 (Private region) Operational
90 days agoNo incidentsToday
ap-east-2 (Private region) Operational
90 days agoNo incidentsToday
ap-southeast-3 (Private region) Operational
90 days agoNo incidentsToday
ap-southeast-5 (Private region) Operational
90 days agoNo incidentsToday
af-south-1 (Private region) Operational
90 days agoNo incidentsToday
eu-north-1 (Private region) Operational
90 days agoNo incidentsToday
mx-central-1 (Private region) Operational
90 days agoNo incidentsToday
sa-east-1 (Private region) Operational
90 days agoNo incidentsToday
us-central1 Operational
90 days agoNo incidentsToday
us-east1 Operational
90 days agoNo incidentsToday
europe-west4 Operational
90 days agoNo incidentsToday
asia-northeast1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 23, 2026

Duration2 h 48 min04:51 to 07:39Degraded support ticket submission and responseDegraded

``` 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 ```

Oct 20, 2026

Duration6 h 44 min07:39 to 14:23Google Cloud OutageDegraded

The issue has been resolved. All services are fully operational.

Oct 12, 2026

Duration31 min01:55 to 02:26Support case creation unavailableNotice

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.

Sep 24, 2026

Duration29 min08:42 to 09:11Streaming ClickPipes degradation in AWS eu-central-1 regionDegraded

Remediation was applied and we don't see signs of degradation anymore. Team will continue monitoring and investigating the root cause.

Duration33 min08:31 to 09:05Some ClickPipes CDC pipes paused and can't be resumedDegraded

All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future.

Sep 23, 2026

Duration30 min15:28 to 15:59We are investigating an issue affecting Azure eastus2 regionDegraded

The configuration change was reverted and we do not observe impact anymore. The ClickHouse Cloud team will work on preventing similar situations in future.

Sep 22, 2026

Duration5 h 6 min13:19 to 18:25We are investigating an issue with CH servers in Azure germanywestcentral regionDegraded

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.

Sep 16, 2026

Duration13 h 50 min10:16 to 00:05Intermittent Issues with the Support tabDegraded

Salesforce has confirmed the incident is resolved on their end.

Sep 15, 2026

Duration29 h 46 min18:57 to 00:43ClickPipes failing on Kinesis in AWS us-east-1Degraded

This incident has been resolved. AWS has confirmed that the Enhanced Fanhout (EFO) Kinesis pipes in us-east-1 region are fully operational. Please contact ClickHouse Support if you experience any further issues:

Sep 14, 2026

Duration3 h 59 min20:36 to 00:35Distributed Cache performance degradation in AWS us-east-1Degraded

This incident has been resolved. Distributed Cache performance in the region is back to normal. Please contact ClickHouse Support if any services in the Distributed Cache Private Preview are experiencing any remaining issues:

Sep 1, 2026

Duration19 min16:11 to 16:30Service degradation in GCP us-central-1Notice

All systems operational. GCP incident has no impact on ClickHouse Cloud.

Aug 23, 2026

Duration32 min10:14 to 10:47Slow provisioning times of services in GCP europe-west4 regionDegraded

Issue was resolved. Services are provisioning successfully.

Aug 17, 2026

Duration1 h 54 min15:23 to 17:17Provisioning of new CDC pipes for Postgres might be delayed or failingDegraded

This issue has been resolved. New CDC pipes for Postgres are provisioning normally.

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=clickhouse
Slack
/feed subscribe https://outages.live/feed.xml?providers=clickhouse

Go from tracking outages to fixing production issues with Polylane.

Try Polylane