- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Confluent Cloud
- Regions
- us, us-east-1
- Down Index
- 53of 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 27d 15h it lasted.
Anything that failed between 2026-05-08 01:14 UTC and 2026-06-04 16: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 investigating data plane impact (produce/consume) resulting from elevated error rates and latencies from AWS us-east-1 resources in AZ4. EC2 instances hosted on this availability zone are impaired by loss of power during an ongoing thermal event.
provider
- monitoring
We are monitoring the health of impacted brokers in the affected availability zone. More details about the thermal event on the AWS status page: https://health.aws.amazon.com/health/status
provider
- monitoring
AWS has resolved the underlying infrastructure issue in us-east-1 (use1-az4). The majority of Confluent Cloud services have recovered and are operating normally. We are continuing to monitor for any lingering effects and verifying full service restoration.
provider
- monitoring
AWS has reported the underlying infrastructure issue in us-east-1 (use1-az4) as resolved. However, some Confluent Cloud customers in the affected availability zone continue to experience connectivity issues. Confluent is actively investigating and working to restore full connectivity for impacted customers.
provider
- resolved
The incident has been resolved and us-east-1 (use1-az4) is fully operational.
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-d262dfc85e
Is Confluent Cloud still down?
No, this incident was resolved 2026-06-04 16:47 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
27d 15h, from 2026-05-08 01:14 UTC to 2026-06-04 16:47 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 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.