Is ClickHouse Cloud down?
Right now
No. ClickHouse Cloud is operational.
No incidents reported.
Read from status.clickhouse.com · every 120s
For agents
proceed
Proceed.
GET upbutler.com/status/clickhouse/status.agent.json
MCP: upstream_status {"service":"clickhouse"}
Managed ClickHouse services per cloud region.
What ClickHouse Cloud reports
Operational
Taken as is from ClickHouse Cloud's own status page API. Incident titles and component names below are theirs.
Open status.clickhouse.comUpButler's independent probe
There is no keyless endpoint of ClickHouse Cloud that says anything useful, so UpButler does not probe it. To check your own ClickHouse Cloud account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
ClickHouse Cloud components
24 operational
- us-east-1Operational
- us-east-2Operational
- us-west-2Operational
- eu-central-1Operational
- eu-west-1Operational
- eu-west-2Operational
- ap-northeast-1Operational
- ap-northeast-2Operational
- ap-south-1Operational
- ap-southeast-1Operational
- ap-southeast-2Operational
- il-central-1Operational
- ap-east-1 (Private region)Operational
- ap-east-2 (Private region)Operational
- ap-southeast-3 (Private region)Operational
- ap-southeast-5 (Private region)Operational
- af-south-1 (Private region)Operational
- eu-north-1 (Private region)Operational
- mx-central-1 (Private region)Operational
- sa-east-1 (Private region)Operational
- us-central1Operational
- us-east1Operational
- europe-west4Operational
- asia-northeast1Operational
ClickHouse Cloud incidents, last 90 days
No finished incidents on record yet. UpButler keeps what ClickHouse Cloud publishes for 90 days from the day it starts tracking a service.
Tell your outage from ClickHouse Cloud's
Declare that your project depends on ClickHouse Cloud. When one of your monitors fails while ClickHouse Cloud has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- clickhousecurl -s https://upbutler.com/status/clickhouse/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "clickhouse",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is ClickHouse Cloud down right now?
- No. As of 2026-10-10 05:10 UTC, ClickHouse Cloud is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From ClickHouse Cloud's own status page API at https://status.clickhouse.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are ClickHouse Cloud's words.
- How can my agent or app check ClickHouse Cloud status?
- Fetch https://upbutler.com/status/clickhouse/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"clickhouse"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or ClickHouse Cloud's?
- Add "clickhouse" to the dependencies of your UpButler workspace. When one of your monitors fails while ClickHouse Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in databases and data
UpButler is not affiliated with ClickHouse Cloud. Status and incident text belong to ClickHouse Cloud and are read from their public status source; the probe result is UpButler's own measurement.