Skip to main content
Confluent Cloud

Experiencing high error rate in AZURE in West Europe region

Partial outage Lasted 10h 33m · started · Confluent Cloud's page

Level
confirmed
Worst impact
Partial outage
Components
Confluent Cloud
Regions
eu

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 10h 33m it lasted.

    Anything that failed between 2026-10-09 23:03 UTC and 2026-10-10 09:36 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.

Updates from Confluent Cloud 12

  1. investigating

    Users in West Europe region of Azure could face elevated error rates and experience degraded performance. We are currently investigating the issue and attempting to mitigate or provide a work-around.

    provider

  2. identified

    Azure has identified the issue and recovery actions are underway

    provider

  3. identified

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 20:00 UTC, or sooner, as updates are available.

    provider

  4. identified

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 21:00 UTC, or sooner, as updates are available.

    provider

  5. identified

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 22:00 UTC, or sooner, as updates are available.

    provider

  6. identified

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 23:00 UTC, or sooner, as updates are available.

    provider

  7. identified

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 00:00 UTC, or sooner, as updates are available.

    provider

  8. identified

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 01:00 UTC, or sooner, as updates are available.

    provider

  9. identified

    Confluent is continuing to work with Azure on recovery for a small number of affected clusters. Azure has not provided Confluent with a specific ETA for resolution. Our next update will be posted by 03:00 UTC, or sooner, as updates are available.

    provider

  10. identified

    Confluent continues to work closely with Azure, and we are seeing recovery across a number of affected clusters. Azure has not yet provided a specific ETA for full resolution. We will continue to provide updates as more information becomes available.

    provider

  11. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  12. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-1097e896b1

Is Confluent Cloud still down?

No, this incident was resolved 2026-10-10 09:36 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.

How long did it last?

10h 33m, from 2026-10-09 23:03 UTC to 2026-10-10 09:36 UTC, by the times Confluent Cloud posted.

What was affected?

Confluent Cloud named Confluent Cloud in eu.

What caused it?

Confluent Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Confluent Cloud's official status page, https://status.confluent.cloud, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.