Major incident
Confluent Cloud: Elevated error rates and latency in GCP us-west1
Aug 20, 2026, 17:10 UTC
started
20:18 UTC
resolved
3 h 08 min
duration
Affected: Confluent Cloud
Current status of Confluent Cloud: Operational — live Confluent Cloud status
Timeline
- Aug 20, 2026, 17:10 UTCinvestigatingWe 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.
- Aug 20, 2026, 19:18 UTCinvestigatingWe are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour.
- Aug 20, 2026, 20:18 UTCresolvedThe GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.
Updates as published by Confluent Cloud (original).
Other services with incidents at the same time
- Pitney Bowes 18:07 UTC · UPS Service Disruption Observed for CreateShipment.
- Vercel 17:46 UTC · New container functions are failing
- Ping Identity 17:41 UTC · PingID - US Region - Service Disruption
- Onshape 17:26 UTC · Increased errors in US-West region
- Harness 17:17 UTC · All modules are running slow in Prod1/2/3/4 due to cloud provider incident
- PandaDoc 17:03 UTC · Some users experience issues with creation and viewing of documents
More Confluent Cloud incidents
- October 20, 2026 Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
- October 16, 2026 Delay in Kafka cluster provisioning
- October 15, 2026 Confluent Cloud Console (UI) degraded functionality
- October 9, 2026 Possible outage in AWS us-east-1
- October 9, 2026 Experiencing high error rate in AZURE in West Europe region
- October 8, 2026 Experiencing high error rate in AZURE in Germany West Central region