Companies / Confluent / incidents
Confluent: Elevated error rates and latencies in Azure westus2 region
Confluent Cloud had a major outage with elevated errors and latencies in Azure westus2, linked to Azure network connectivity degradation. The incident ran from 2026-05-29 06:47 UTC to 2026-05-29 21:47 UTC (15 h 0 min), though Confluent reported symptoms beginning around 05:10 UTC. Azure’s degradation was mitigated and Confluent Cloud returned to normal.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Confluent Cloud
Timeline of updates
- investigating
We are currently experiencing increased error rates and latencies in the Azure westus2 region. This began at approximately 5:10 AM UTC 29th May. Our team is actively investigating it.
- investigating
Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation. Team is continuing active investigation.
- monitoring
We are monitoring the health of impacted Confluent services in the Azure West US2 region. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status
- monitoring
Confluent services in the Azure West US2 region are now healthy. We are continuing to monitor for residual effects as Azure continues to address their service outage. More details about the Multi Service degradation on the Azure status page: https://azure.status.microsoft/en-us/status
- resolved
The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
Rewindex changes for this incident
- Major incident: Elevated error rates and latencies in Azure westus2 region 2026-05-29 06:47 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON