Skip to main content
ClickHouse Cloud

Service degradation in GCP us-central-1

Degraded Lasted 19m · started · ClickHouse Cloud's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-central-1, us-central1
Down Index
27of 100

What to do

  • Check whether you use ClickHouse Cloud in us, us-central-1, us-central1. 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 19m it lasted.

    Anything that failed between 2026-09-01 16:11 UTC and 2026-09-01 16:30 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

  1. investigating

    Due to networking issues in GCP us-central1 zone b (see ), ClickHouse Cloud services can be degraded as well. Symptoms can be temporarily unavailable metrics and monitoring dashboards. Creation of new services and ClickPipes pipelines can be temporarily unavailable as well. Existing ClickHouse Services are not affected and are operating normally.

    provider

  2. investigating

    After careful investigation we could not determine any impact of the [GCP service degradation](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev) (in zone b) on ClickHouse Cloud functionality.

    provider

  3. resolved

    All systems operational. GCP incident has no impact on ClickHouse Cloud.

    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-6173c16351

Is ClickHouse Cloud still down?

No, this incident was resolved 2026-09-01 16:30 UTC. For ClickHouse Cloud's live state, see https://down.guide/clickhouse-cloud.

How long did it last?

19m, from 2026-09-01 16:11 UTC to 2026-09-01 16:30 UTC, by the times ClickHouse Cloud posted.

What was affected?

ClickHouse Cloud named in us, us-central-1, us-central1.

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.