Statuspy
Databases

Is ClickHouse Cloud down right now?

No, it’s up.

ClickHouse Cloud appears to be up and running normally.

checked responded in 87msHTTP 200

Over the last 7 days, ClickHouse Cloud has answered our automated checks with 100.00% availability and a typical response time of ~123 ms. The most recent outage began 2026-08-02 14:44 UTC and lasted 4h 49m (severity: degraded).

ClickHouse Cloud is the managed version of the ClickHouse columnar database, used for analytics over very large datasets. Ingestion and query serving scale separately, so an incident often means inserts backing up while dashboards continue to query slightly stale data.

Response time (last 24h)
Last 24hpeak 337 ms
Incident history (last 90 days)
JunJulAug
  • up
  • slow
  • down
  • no reading
DateDurationSeverity
4h 49mDegraded
3h 26mDegraded
2h 42mDown
2h 25mDegraded
5mDown
2h 29mDegraded
0sDegraded
5h 7mDegraded
5d 2hDegraded
1h 22mDegraded
39mDegraded
2d 6hDegraded
1d 7hDegraded
Uptime
100.00%
7 days
100.00%
30 days
100.00%
90 days
What to do if ClickHouse Cloud is down for just you
  • Check your connection limit and pool settings first, since exhausting connections looks exactly like the database being down.
  • Retry with a longer timeout, because a serverless or scale-to-zero instance may simply be waking up.
  • Confirm your credentials and IP allowlist have not changed, as an auth or firewall denial reads as a failed query.
  • Query from another network or client to establish whether the cluster or your route to it is the problem.
Frequently asked questions
Is ClickHouse Cloud down right now?
ClickHouse Cloud appears to be up and running normally. Last checked 2026-08-05 04:42 UTC (4 minutes ago).
When was ClickHouse Cloud's last outage?
The most recent outage began 2026-08-02 14:44 UTC and lasted 4h 49m (severity: degraded).
What should I do if ClickHouse Cloud is down for me?
Check your connection limit and pool settings first, since exhausting connections looks exactly like the database being down. Retry with a longer timeout, because a serverless or scale-to-zero instance may simply be waking up. Confirm your credentials and IP allowlist have not changed, as an auth or firewall denial reads as a failed query. Query from another network or client to establish whether the cluster or your route to it is the problem.
ClickHouse Cloud’s official status page

Related services

CockroachDB CloudConfluent CloudFirebaseMongoDB AtlasNeonPinecone