- Level
- confirmed
- Worst impact
- Degraded
- Components
- Confluent Cloud
- Down Index
- 40of 100
What to do
Check whether you use Confluent Cloud 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 2h 45m it lasted.
Anything that failed between 2026-10-15 16:01 UTC and 2026-10-15 18:46 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 2
- monitoring
Between 14:23 and 15:35 UTC on Oct 15, 2026, some users of the Confluent Cloud Console experienced errors and degraded page functionality. No other services were affected. The issue has been mitigated and no further problems have been observed. Confluent is investigating root cause and monitoring. No customer action is required.
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-cbb92b6c9a
Is Confluent Cloud still down?
No, this incident was resolved 2026-10-15 18:46 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
2h 45m, from 2026-10-15 16:01 UTC to 2026-10-15 18:46 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud.
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.