- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Confluent Cloud. 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 0m it lasted.
Anything that failed between 2026-08-24 15:49 UTC and 2026-08-23 21:00 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 1
- resolved
Between 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.
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-2057d5d838
Is Confluent Cloud still down?
No, this incident was resolved 2026-08-23 21:00 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
0m, from 2026-08-24 15:49 UTC to 2026-08-23 21:00 UTC, by the times Confluent Cloud posted.
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.