Changes / Confluent / Experiencing high error rate in AZURE in West Europe region

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

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 diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 81%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Experiencing high error rate in AZURE in West Europe region
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-09 23:03 UTC
AddedResolved time#5
Before: not present
After: 2026-10-10 09:36 UTC
AddedAffected components#6
Before: not present
After: Confluent Cloud
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateidentified#8
Before: not present
After: Azure has identified the issue and recovery actions are underway
AddedUpdateidentified#9
Before: not present
After: 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.
AddedUpdateidentified#10
Before: not present
After: 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.
AddedUpdateidentified#11
Before: not present
After: 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.
AddedUpdateidentified#12
Before: not present
After: 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.
AddedUpdateidentified#13
Before: not present
After: 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.
AddedUpdateidentified#14
Before: not present
After: 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.
AddedUpdateidentified#15
Before: not present
After: 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.
AddedUpdateidentified#16
Before: not present
After: 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.
AddedUpdatemonitoring#17
Before: not present
After: A fix has been implemented and we are monitoring the results.
AddedUpdateresolved#18
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: Experiencing high error rate in AZURE in West Europe region (this change)
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.
Major incident

All Confluent changes → · Confluent profile · Markdown · JSON