Elevated error rates in Azure Germany West Central region
This incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational.
The latest update from Confluent Cloud.
State
Resolved
Started
40 d ago
2026-09-22 15:09 UTC
Lasted
4 h 50 min
until 2026-09-22 19:58 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
4 h 27 min 92%
Monitoring
23 min 8%
Updates
Times in UTCAs posted by Confluent Cloud
This incident has been resolved. Clusters in the Azure's Germany West Central region are now fully operational.
The Azure regional disruption has ended, and Confluent Cloud mitigation was achieved as of 18:00 UTC. Clusters in the Azure's Germany West Central region are now fully operational. We will monitor for residual impact before marking this incident resolved.
We are investigating connectivity issues and elevated error rates affecting some Confluent Cloud clusters hosted in Microsoft Azure's Germany West Central region, beginning at approximately 13:00 UTC on 22 Sep 2026. Affected customers may experience degraded availability or intermittent connectivity for clusters in the region. This is associated with an ongoing Microsoft Azure service disruption in that region. We are actively engaged with Microsoft Azure.
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
1.3× 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 West Europe 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