- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 23of 100
What to do
Check whether you use ClickHouse Cloud in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 23m it lasted.
Anything that failed between 2026-08-14 19:25 UTC and 2026-08-14 19:47 UTC may need a replay.Subscribe to ClickHouse Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=clickhouse-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from ClickHouse Cloud 2
- monitoring
We noticed a network issue between 18:10–18:37 UTC affecting a small subset of services on AWS in the us-east-1 region. During that period, you may have experienced connection timeouts to your services. The issue has been resolved, and our team continues to monitor the situation.
provider
- resolved
This issue has been resolved. Connectivity has returned to normal.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-78bb6a06a8
Is ClickHouse Cloud still down?
No, this incident was resolved 2026-08-14 19:47 UTC. For ClickHouse Cloud's live state, see https://down.guide/clickhouse-cloud.
How long did it last?
23m, from 2026-08-14 19:25 UTC to 2026-08-14 19:47 UTC, by the times ClickHouse Cloud posted.
What was affected?
ClickHouse Cloud named in us, us-east-1.
What caused it?
ClickHouse Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
ClickHouse Cloud's official status page, https://status.clickhouse.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.