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

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-10-09 23:03 UTC · Resolved: 2026-10-10 09:36 UTC · Duration: 11 h
- Updates: 12 · Affected components: Confluent Cloud
- [Vendor status page: https://stspg.io/hnth2zjystz5](https://stspg.io/hnth2zjystz5)
- [Company: Confluent](https://rewindex.com/company/confluent.md)

## 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, sol)_
## Timeline of updates

- **investigating** 2026-10-09 13:34 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.
- **identified** 2026-10-09 16:46 UTC: Azure has identified the issue and recovery actions are underway
- **identified** 2026-10-09 19:10 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.
- **identified** 2026-10-09 20:02 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.
- **identified** 2026-10-09 21:07 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.
- **identified** 2026-10-09 22:04 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.
- **identified** 2026-10-09 23:03 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 00:00 UTC, or sooner, as updates are available.
- **identified** 2026-10-10 00:12 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.
- **identified** 2026-10-10 02:12 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 03:00 UTC, or sooner, as updates are available.
- **identified** 2026-10-10 04:15 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.
- **monitoring** 2026-10-10 08:47 UTC: A fix has been implemented and we are monitoring the results.
- **resolved** 2026-10-10 09:36 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2026-10-09 23:03 UTC: [Major incident: Experiencing high error rate in AZURE in West Europe region](https://rewindex.com/change/i487d8101457c8f.md)


---
Canonical: https://rewindex.com/company/confluent/incidents/07y1w8m52p0q · Markdown: https://rewindex.com/company/confluent/incidents/07y1w8m52p0q.md · JSON: https://rewindex.com/api/v1/companies/confluent/incidents/07y1w8m52p0q · Generated 2026-10-18T12:32:33.415Z