Changes / Confluent / Elevated error rates and latencies in Azure westus2 region

Confluent: Major incident: Elevated error rates and latencies in Azure westus2 region

Summary

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

Major incidentLabel: outage (model (Jev), 79%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Elevated error rates and latencies in Azure westus2 region
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-05-29 06:47 UTC
AddedResolved time#5
Before: not present
After: 2026-05-29 21:47 UTC
AddedAffected components#6
Before: not present
After: Confluent Cloud
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateinvestigating#8
Before: not present
After: Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation. Team is continuing active investigation.
AddedUpdatemonitoring#9
Before: not present
After: 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
AddedUpdatemonitoring#10
Before: not present
After: 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
AddedUpdateresolved#11
Before: not present
After: The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Elevated error rates and latencies in Azure westus2 region (this change)
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.
Major incident

All Confluent changes → · Confluent profile · Markdown · JSON