Confluent incident

Experiencing high error rate in AZURE in West Europe region

Major Resolved View vendor source →

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

Started
Oct 09, 2026, 01:34 PM UTC
Resolved
Oct 10, 2026, 09:36 AM UTC
Duration
20h 2m
Detected by Pingoru
Oct 09, 2026, 01:34 PM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Oct 09, 2026, 01:34 PM UTC

    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 Oct 09, 2026, 04:46 PM UTC

    Azure has identified the issue and recovery actions are underway

  3. identified Oct 09, 2026, 07:10 PM UTC

    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 Oct 09, 2026, 08:02 PM UTC

    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 Oct 09, 2026, 09:07 PM UTC

    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 Oct 09, 2026, 10:04 PM UTC

    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 Oct 09, 2026, 11:03 PM UTC

    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 24:00 UTC, or sooner, as updates are available.

  8. identified Oct 10, 2026, 12:12 AM UTC

    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 Oct 10, 2026, 02:12 AM UTC

    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 02:00 UTC, or sooner, as updates are available.

  10. identified Oct 10, 2026, 04:15 AM UTC

    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 Oct 10, 2026, 08:47 AM UTC

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

  12. resolved Oct 10, 2026, 09:36 AM UTC

    This incident has been resolved.