- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Regions
- us
- Down Index
- 53of 100
What to do
Check whether you use Confluent Cloud Confluent Cloud in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 15h 1m it lasted.
Anything that failed between 2026-05-29 06:47 UTC and 2026-05-29 21:47 UTC may need a replay.Subscribe to Confluent Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=confluent works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Confluent Cloud 5
- 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.
provider
- investigating
Confluent cloud services are experiencing outage in Azure West US2 region linked to Azure network connectivity degradation. Team is continuing active investigation.
provider
- 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
provider
- 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
provider
- resolved
The Multi Service degradation on Azure has been mitigated. Confluent Cloud is operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a3433631aa
Is Confluent Cloud still down?
No, this incident was resolved 2026-05-29 21:47 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
15h 1m, from 2026-05-29 06:47 UTC to 2026-05-29 21:47 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud in us.
What caused it?
Confluent Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Confluent Cloud's official status page, https://status.confluent.cloud, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.