- Level
- confirmed
- Worst impact
- Degraded
- Components
- Confluent Cloud
- Regions
- us, us-east-1
- Down Index
- 43of 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 1d 5h it lasted.
Anything that failed between 2026-09-08 09:17 UTC and 2026-09-09 14:56 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 10
- investigating
We are investigating a service disruption affecting multiple services in AWS us-east-1 region. Affected customers may experience authentication failures, errors accessing Schema Registry, or issues with KSQL and Flink workloads. We are actively investigating the root cause and working toward mitigation.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- investigating
We are currently investigating this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We continue to work on remediating the service disruption in AWS us-east-1. Confirmed impact: - Authentication — a subset of requests may fail - Schema Registry — authorization errors on a subset of requests - ksqlDB — a subset of queries/requests may be affected - Flink — statement management operations (create/update/delete) are degraded, and some running Flink jobs may fail or restart - Kafka operations (create, delete etc) Not impacted: Kafka cluster data-plane operations are not affected by this incident. This issue is isolated to the AWS us-east-1 region; other regions are unaffected
provider
- identified
We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.
provider
- identified
Confluent is continuing to work on remediating the service disruption in AWS us-east-1.
provider
- identified
Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.
provider
- monitoring
We have applied a mitigation for the issue affecting Schema Registry, Authentication, ksqlDB, Flink, and Kafka operations in AWS us-east-1. Services are recovering and we are monitoring closely.
provider
- resolved
The systems have recovered and Confluent Cloud 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-122e712276
Is Confluent Cloud still down?
No, this incident was resolved 2026-09-09 14:56 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
1d 5h, from 2026-09-08 09:17 UTC to 2026-09-09 14:56 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.