Skip to main content
Confluent Cloud

Elevated error rates and latency in GCP us-west1

Partial outage Lasted 3h 8m · started · Confluent Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
Confluent Cloud
Regions
us, us-west1
Down Index
50of 100

What to do

  • Check whether you use Confluent Cloud Confluent Cloud in us, us-west1. 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 3h 8m it lasted.

    Anything that failed between 2026-08-20 17:10 UTC and 2026-08-20 20:18 UTC may need a replay.
  • Subscribe to Confluent Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=confluent works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Confluent Cloud 3

  1. investigating

    We are investigating an incident affecting services in the GCP us-west1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates. Our engineering teams are actively working to restore normal performance.

    provider

  2. investigating

    We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour.

    provider

  3. resolved

    The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.

    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-7712c29e92

Is Confluent Cloud still down?

No, this incident was resolved 2026-08-20 20:18 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.

How long did it last?

3h 8m, from 2026-08-20 17:10 UTC to 2026-08-20 20:18 UTC, by the times Confluent Cloud posted.

What was affected?

Confluent Cloud named Confluent Cloud in us, us-west1.

What caused it?

Confluent Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Confluent Cloud's official status page, https://status.confluent.cloud, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.