Search

Companies / Confluent / incidents

Confluent: Experiencing high error rate in AZURE in West Europe region

Impact: majorStatus: resolvedStarted Resolved (11 h)12 updatesSource: stspg.io (opens in new tab)
Summary

Confluent Cloud experienced elevated error rates and degraded performance in Azure West Europe, with major impact. The incident started at 2026-10-09 23:03 UTC and was resolved at 2026-10-10 09:36 UTC, lasting 10 h 33 min; Azure identified the issue, and a fix was implemented.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Confluent Cloud

Timeline of updates

  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.

  2. identified

    Azure has identified the issue and recovery actions are underway

  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.

  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.

  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.

  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.

  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.

  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.

  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.

  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.

  11. monitoring

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

  12. resolved

    This incident has been resolved.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON