- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Regions
- us, us-south1
- Down Index
- 53of 100
What to do
Check whether you use Confluent Cloud Confluent Cloud in us, us-south1. 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 2d 13h it lasted.
Anything that failed between 2026-02-25 05:01 UTC and 2026-02-27 18:16 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 6
- investigating
We are currently investigating the issue
provider
- identified
GCP has identified the issue and is actively working on applying mitigation.
provider
- identified
At this time, single zone clusters in us-south1 Zone-a are impacted.
provider
- monitoring
A fix has been implemented and we are monitoring the results
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
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-74a06a5854
Is Confluent Cloud still down?
No, this incident was resolved 2026-02-27 18:16 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
2d 13h, from 2026-02-25 05:01 UTC to 2026-02-27 18:16 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud in us, us-south1.
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.