- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Regions
- us, us-east-1
- Down Index
- 47of 100
What to do
Check whether you use Confluent Cloud Confluent Cloud in us, us-east-1. 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 56m it lasted.
Anything that failed between 2026-10-09 23:27 UTC and 2026-10-10 00:23 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.
Root cause
No action is required from customers at this point and we are monitoring and investigating further to understand the root cause with the provider.Read the postmortem
Updates from Confluent Cloud 3
- investigating
We are investigating an incident affecting services in the AWS us-east-1 region. Customers with Kafka clusters in this region may experience elevated latency, request timeouts, or increased error rates.
provider
- monitoring
The observed elevated error rates seen in AWS us-east-1 have subsided and all services have recovered. No action is required from customers at this point and we are monitoring and investigating further to understand the root cause with the provider.
provider
- resolved
This incident has been resolved. All affected services have fully recovered.
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-340f0488d7
Is Confluent Cloud still down?
No, this incident was resolved 2026-10-10 00:23 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
56m, from 2026-10-09 23:27 UTC to 2026-10-10 00:23 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud in us, us-east-1.
What caused it?
Confluent Cloud wrote: "No action is required from customers at this point and we are monitoring and investigating further to understand the root cause with the provider." The postmortem: https://stspg.io/57ltxrm4nnrr
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.