We started checking ClickHouse Cloud on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when ClickHouse Cloud reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what ClickHouse Cloud's own status page declared. Below it, any public chatter we saw about ClickHouse Cloud and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what ClickHouse Cloud's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about ClickHouse Cloud in the last 24 hours, which is not evidence that nothing is wrong.
ClickHouse Cloud's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is ClickHouse Cloud's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention ClickHouse Cloud next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
433
US-West
99.70%
337
Europe
100.00%
308
Asia-Pacific
100.00%
186
Their declared record
ClickHouse Cloud's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Nov 2, 2026, 5:13 PM UTC to Nov 2, 2026, 6:03 PM UTC (50 min)resolved
their latest update (Nov 2, 2026, 6:03 PM UTC): This incident has been resolved. We are currently working on fixing the underlying issues that caused it.
Degraded support ticket submission and responseMinor incident
Oct 23, 2026, 4:51 AM UTC to Oct 23, 2026, 7:39 AM UTC (2h 48m)resolved
their latest update (Oct 23, 2026, 7:39 AM UTC): ```
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://st…
Google Cloud OutageMinor incident
Oct 20, 2026, 7:39 AM UTC to Oct 20, 2026, 2:23 PM UTC (6h 44m)resolved
their latest update (Oct 20, 2026, 2:23 PM UTC): The issue has been resolved. All services are fully operational.
Support case creation unavailableAll systems operational
Oct 12, 2026, 1:55 AM UTC to Oct 12, 2026, 2:26 AM UTC (31 min)resolved
their latest update (Oct 12, 2026, 2:26 AM UTC): 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.
Streaming ClickPipes degradation in AWS eu-central-1 regionMinor incident
Sep 24, 2026, 8:42 AM UTC to Sep 24, 2026, 9:11 AM UTC (29 min)resolved
their latest update (Sep 24, 2026, 9:11 AM UTC): Remediation was applied and we don't see signs of degradation anymore. Team will continue monitoring and investigating the root cause.
Some ClickPipes CDC pipes paused and can't be resumedMinor incident
Sep 24, 2026, 8:31 AM UTC to Sep 24, 2026, 9:05 AM UTC (33 min)resolved
their latest update (Sep 24, 2026, 9:05 AM UTC): All stuck pipes were resumed. ClickHouse team will continue monitoring and identifying the root cause to prevent similar issues in future.
We are investigating an issue affecting Azure eastus2 regionMinor incident
Sep 23, 2026, 3:28 PM UTC to Sep 23, 2026, 3:59 PM UTC (30 min)resolved
their latest update (Sep 23, 2026, 3:59 PM UTC): 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 are investigating an issue with CH servers in Azure germanywestcentral regionMinor incident
Sep 22, 2026, 1:19 PM UTC to Sep 22, 2026, 6:25 PM UTC (5h 6m)resolved
their latest update (Sep 22, 2026, 6:25 PM UTC): 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:4…
Intermittent Issues with the Support tabMinor incident
Sep 16, 2026, 10:16 AM UTC to Sep 17, 2026, 12:05 AM UTC (13h 50m)resolved
their latest update (Sep 17, 2026, 12:05 AM UTC): Salesforce has confirmed the incident is resolved on their end.
ClickPipes failing on Kinesis in AWS us-east-1Minor incident
Sep 15, 2026, 6:57 PM UTC to Sep 17, 2026, 12:43 AM UTC (1d 5h)resolved
their latest update (Sep 17, 2026, 12:43 AM UTC): 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: <https://console.clickhouse.cloud/support>
Showing the 10 most recent of 26 incidents ClickHouse Cloud has declared in the history we hold.
These entries are ClickHouse Cloud's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
ClickHouse Cloud's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.