Is ClickHouse Cloud Down?

No — ClickHouse Cloud is up

Reachable from all 8 checked regions

Average response time: 239ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.clickhouse.com

ClickHouse Cloud uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

281ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak

Aug 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn

171ms

DNS 43ms TCP 1ms TLS 9ms TTFB 161ms

bom

133ms

DNS 21ms TCP 2ms TLS 8ms TTFB 119ms

cdg

264ms

DNS 0ms TCP 1ms TLS 8ms TTFB 251ms

dfw

217ms

DNS 41ms TCP 1ms TLS 14ms TTFB 207ms

ewr

220ms

DNS 50ms TCP 2ms TLS 7ms TTFB 209ms

fra

170ms

DNS 19ms TCP 2ms TLS 9ms TTFB 156ms

gru

578ms

DNS 0ms TCP 2ms TLS 10ms TTFB 566ms

iad

161ms

DNS 20ms TCP 1ms TLS 5ms TTFB 144ms

What ClickHouse Cloud does

ClickHouse Cloud is the managed version of the ClickHouse column-oriented database, used for analytics over large event and log datasets. Teams point dashboards, product analytics and customer-facing reporting at it, so an incident tends to be noticed first as charts failing to load rather than as a database alert.

What an outage looks like

Queries time out or return connection errors while the service itself still shows as running. Dashboards built on it fail to render or show stale figures from cache. Ingestion backs up, so recent data is missing from results even though older queries work normally. Services that scale to zero take much longer than usual to wake, which looks like a hang rather than an error.

What to do about it

status.clickhouse.com reports 82 components, almost all of them individual cloud regions across AWS, Google Cloud and Azure, so the row that matters is the region your service runs in rather than the overall state. Private regions are labelled as such. ClickHouse Agents is tracked separately from the regions. Avoid re-running heavy analytical queries during an incident, since each retry is expensive and adds load to a region that is recovering.

Is it down for everyone, or just you?

If this page says ClickHouse Cloud is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

ClickHouse Cloud outage FAQ

Is ClickHouse Cloud down or is my query just slow?

Check the component for your specific region first. Analytical queries can legitimately take a long time, so slowness alone is weak evidence. Connection errors, or simple queries that normally return instantly now timing out, are much stronger. A region marked healthy alongside one slow query usually means the query, not the platform.

Is my data lost if ingestion fails during an outage?

Data already written is not affected by an availability incident. What is at risk is data in flight, and that depends on your pipeline: a producer that buffers and retries will catch up, while one that fires and forgets will leave a gap. Check for holes in recent time ranges once the region recovers.

Does an outage in one region affect my service?

Only if your service runs there. ClickHouse Cloud reports each AWS, Google Cloud and Azure region as its own component, so an incident in one leaves the others untouched. Note that some regions are marked private, and those report separately again. Read the row matching where your service was created.

Why is my service taking minutes to respond after being idle?

Services that have scaled down need to wake before serving, and that first query carries the startup cost. During a degraded period this takes longer than usual, which reads as a hang. It is worth distinguishing from a real outage before escalating, particularly on development services that sit idle between working days.

Do my dashboards keep working during an outage?

Anything cached by the reporting tool keeps rendering, which is why a dashboard can look fine while showing figures from before the incident began. This is more misleading than an obvious error, because the numbers appear current. Check the timestamp on the data rather than trusting that the chart drew successfully.

How we measure this

We request ClickHouse Cloud's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where ClickHouse Cloud publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when ClickHouse Cloud goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required