- Level
- confirmed
- Worst impact
- Degraded
- Regions
- ap-northeast-1, apac
- Cascade
- aws-2026-11-11
Summary
ClickHouse Cloud says provisioning and scaling operations in AWS ap-northeast-1 (Tokyo) may take longer than usual, an issue also reported on the AWS status page. The provider says the incident is resolved as of 23:44 UTC on 2026-11-11, with services and provisioning functioning normally in the region.
Written by anthropic/claude-haiku-5.5 from ClickHouse Cloud's own updates.
What to do
Check whether you use ClickHouse Cloud in ap-northeast-1, apac. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 7h 38m it lasted.
Anything that failed between 2026-11-11 16:05 UTC and 2026-11-11 23:44 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 3
- identified
Scaling and provisioning operations may take longer than usual. Issue is reported on AWS status page
provider
- monitoring
AWS is reporting that the previously reported issues in AWS ap-northeast-1 (Tokyo) are Resolved [ ], and ClickHouse has confirmed that services and provisioning are functioning normally in the region. ClickHouse is currently in a Monitoring status for this incident
provider
- resolved
This incident in AWS ap-northeast-1 (Tokyo) is Resolved [ ]
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-36e46be493
Is ClickHouse Cloud still down?
No, this incident was resolved 2026-11-11 23:44 UTC. For ClickHouse Cloud's live state, see https://down.guide/providers/clickhouse-cloud.
How long did it last?
7h 38m, from 2026-11-11 16:05 UTC to 2026-11-11 23:44 UTC, by the times ClickHouse Cloud posted.
What was affected?
ClickHouse Cloud named in ap-northeast-1, apac.
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.