Rewindex

CompaniesClickHouse CloudIncidents

ClickHouse Cloud: Service degradation in GCP us-central-1

MinorStatus: resolvedStarted Resolved (19 min)3 updatesstatus.clickhouse.com (opens in new tab)
Part of an outage event

Google Cloud us-central1 outage, Sep 1, 2026 · 47 vendors, 54 incidents

ClickHouse Cloud’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +1 h 29 min vs Google Cloud’s own post)

“…Service degradation in GCP us-central-1 All systems operational. GCP incident has no impact on ClickHouse Cloud. After careful investigation we could not determine any impact of the GCP service degrad…”

Swipe sideways to see the whole diagram.

blamed GitHubblamed Twiliosame windowGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed Google CloudPinecone, Elastic Cloud, FullStory +51 to 4 hours later6 vendors, 6 blamed Google CloudApollo GraphQL, Temporal Cloud,Clerk +3GitHubposted +18 min, did not name GoogleCloudBolt.new+24 minTwilioposted +1 h 42 min, did not nameGoogle CloudGorgias, Iterable+2 h 23 min to +2 h 37 minClickHouse Cloud (this incident)posted +1 h 29 min
blamed GitHubblamed Twiliosame windowGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed GoogleCloudPinecone, Elastic Cloud,FullStory +51 to 4 hours later6 vendors, 6 blamed GoogleCloudApollo GraphQL, TemporalCloud, Clerk +3GitHubposted +18 min, did not nameGoogle CloudBolt.new+24 minTwilioposted +1 h 42 min, did notname Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 minClickHouse Cloud (this incident)posted +1 h 29 min
ClickHouse Cloud is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
  h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
  root --> h4
  p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Bolt.new<br/>+24 min"]:::hop2
  p0 -->|"blamed GitHub"| k0
  p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
  root -.-> p1
  k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
  p1 -->|"blamed Twilio"| k1
  me["ClickHouse Cloud (this incident)<br/>posted +1 h 29 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. investigating

    Due to networking issues in GCP us-central1 zone b (see https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev), 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.

  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.

  3. resolved

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

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.clickhouse.com (opens in new tab).

ClickHouse Cloud profileRecent ClickHouse Cloud incidentsMarkdownJSON