Confluent incident
Elevated error rates and latencies in Azure westus2 region
Resolved after 15 hours 50 minutes, affecting Confluent Cloud, on May 29, 2026.
The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
Affected components
Update timeline
- investigating May 29, 2026, 05:57 AM UTC
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 May 29, 2026, 06:47 AM UTC
Confluent cloud services are experiencing a zonal outage in Azure West US2 linked to Azure network connectivity degradation. Team is continuing active investigation.
- monitoring May 29, 2026, 10:25 AM UTC
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 May 29, 2026, 04:49 PM UTC
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 May 29, 2026, 09:47 PM UTC
The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
Your product runs on more than Confluent
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services