Experiencing high error rate in AZURE in West Europe region
This incident has been resolved.
The latest update from Confluent Cloud.
State
Resolved
Started
22 d ago
2026-10-09 23:03 UTC
Lasted
10 h 33 min
until 2026-10-10 09:36 UTC
Worst impact
Partial outage
Timeline
12 updatesIdentified
9 h 44 min 92%
Monitoring
50 min 8%
Updates
Times in UTCAs posted by Confluent Cloud
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
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.
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.
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.
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.
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.
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.
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.
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.
Azure has identified the issue and recovery actions are underway
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.
Affected components
1Confluent Cloud in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
17
Median duration
3 h 45 min
This incident
2.8× the median
Other Confluent Cloud incidents
All incidentsConfluent Cloud·Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.
Confluent Cloud·Delay in Kafka cluster provisioning
This incident has been resolved.
Confluent Cloud·Confluent Cloud Console (UI) degraded functionality
This incident has been resolved.
Confluent Cloud·Possible outage in AWS us-east-1
This incident has been resolved. All affected services have fully recovered.
Confluent Cloud·Experiencing high error rate in AZURE in Germany West Central region
This incident has been resolved.
Follow Confluent Cloud
Your coding agent knows when Confluent Cloud is down, and tells you when a failure is theirs, not yours. You can also get Confluent Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "confluent" and tell me if Confluent Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=confluent/feed subscribe https://outages.cc/feed.xml?providers=confluentFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane