Confluent incident

Multiple Confluent Cloud services are in a degraded state - GCP EU-West2

Major Resolved View vendor source →

Confluent experienced a major incident on October 20, 2026 affecting Confluent Cloud, lasting 10h 24m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2026, 08:02 AM UTC
Resolved
Oct 20, 2026, 06:27 PM UTC
Duration
10h 24m
Detected by Pingoru
Oct 20, 2026, 08:02 AM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Oct 20, 2026, 08:02 AM UTC

    Some customer may observe issues with Confluent Cloud services in EU-West2 region. This is due to ongoing issues with GCP EU-West2

  2. investigating Oct 20, 2026, 12:55 PM UTC

    We are currently working to restore the impacted services. Most customers should be able to use Confluent Cloud services normally.

  3. monitoring Oct 20, 2026, 02:46 PM UTC

    The underlying GCP issue has been mitigated. Confluent Cloud Kafka clusters in the affected zone are fully operational and Connect and Flink workloads have recovered. We are monitoring to confirm stability and working to restore the few remaining impacted resources.

  4. monitoring Oct 20, 2026, 02:51 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 20, 2026, 06:27 PM UTC

    This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.