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

What to do

• Check whether you use Confluent Cloud Confluent Cloud in eu. 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 41m it lasted.

  Anything that failed between 2026-10-20 14:46 UTC and 2026-10-20 18:27 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.

Root cause

This is due to ongoing issues with GCP EU-West2

Updates from Confluent Cloud 5

1. investigatingOct 20, 2026, 8: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

   provider

2. investigatingOct 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.

   provider

3. monitoringOct 20, 2026, 2: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.

   provider

4. monitoringOct 20, 2026, 2:51 PM UTC

   We are continuing to monitor for any further issues.

   provider

5. resolvedOct 20, 2026, 6: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.