Major impactResolvedDatabases

Confluent Cloud outage: Elevated error rates and latency in GCP us-west1

Confluent Cloud reported this major-impact incident on its official status page on Aug 20, 2026, 17:10 UTC. It was resolved after 3h 8m.

Right now Confluent Cloud is operational. Live Confluent Cloud status →

🔔 Get alerted when Confluent Cloud has issuesFree · email alerts · no credit card
Aug 20, 2026, 17:10 UTC
started
Aug 20, 2026, 20:18 UTC
resolved
3h 8m
duration
Major
impact

Affected components

  • Confluent Cloud
  1. resolvedAug 20, 2026, 20:18 UTC

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

  2. investigatingAug 20, 2026, 19:18 UTC

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

  3. investigatingAug 20, 2026, 17:10 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history

Confluent Cloud outage on Aug 20, 2026: Elevated error rates and latency in GCP us-west1 · APIStatus.watch