Changes / Confluent / Elevated error rates and latency in GCP us-west1
Confluent: Major incident: Elevated error rates and latency in GCP us-west1
Summary
Confluent Cloud reported a major incident affecting Kafka clusters in GCP us-west1, with elevated latency, request timeouts, and increased error rates. It started at 2026-08-20 17:10 UTC and was resolved at 2026-08-20 20:18 UTC, lasting 3 h 7 min. Confluent said the GCP issues were mitigated and monitoring showed no remaining impact.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 80%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Elevated error rates and latency in GCP us-west1
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-20 17:10 UTC
Before: not present
After: 2026-08-20 20:18 UTC
Before: not present
After: Confluent Cloud
Before: not present
After: 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.
Before: not present
After: We are seeing recovery of Confluent services and are continuing to monitor the situation. The next update will be posted within 1 hour.
Before: not present
After: The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Elevated error rates and latency in GCP us-west1 (this change) Confluent Cloud reported a major incident affecting Kafka clusters in GCP us-west1, with elevated latency, request timeouts, and increased error rates. It started at 2026-08-20 17:10 UTC and was resolved at 2026-08-20 20:18 UTC, lasting 3 h 7 min. Confluent said the GCP issues were mitigated and monitoring showed no remaining impact. | Major incident |
All Confluent changes → · Confluent profile · Markdown · JSON