Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
Subscribe
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.
Sep 09, 2026 - 06:41 UTC
Sep 09, 2026 - 06:41 UTC
Update - Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.
Sep 09, 2026 - 01:45 UTC
Sep 09, 2026 - 01:45 UTC
Update - Confluent is continuing to work on remediating the service disruption in AWS us-east-1.
Sep 09, 2026 - 00:01 UTC
Sep 09, 2026 - 00:01 UTC
Update - We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.
Sep 08, 2026 - 17:41 UTC
Sep 08, 2026 - 17:41 UTC
Update - 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
Sep 08, 2026 - 15:55 UTC
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
Sep 08, 2026 - 15:55 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 08, 2026 - 14:06 UTC
Sep 08, 2026 - 14:06 UTC
Investigating - We are currently investigating this issue.
Sep 08, 2026 - 11:38 UTC
Sep 08, 2026 - 11:38 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 08, 2026 - 10:37 UTC
Sep 08, 2026 - 10:37 UTC
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.
Sep 08, 2026 - 09:17 UTC
Sep 08, 2026 - 09:17 UTC
Monitoring - A fix has been implemented and the team is monitoring recovery.
Sep 08, 2026 - 20:30 UTC
Sep 08, 2026 - 20:30 UTC
Identified - A possible root cause has been identified and the Confluent Cloud team is implementing a fix
Sep 08, 2026 - 20:20 UTC
Sep 08, 2026 - 20:20 UTC
Update - We are continuing to investigate this issue.
Sep 08, 2026 - 20:13 UTC
Sep 08, 2026 - 20:13 UTC
Investigating - We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.
Sep 08, 2026 - 20:01 UTC
Sep 08, 2026 - 20:01 UTC
About This Site
Welcome to Confluent Cloud's status page. Here you will find high level availability information for the Confluent Cloud managed service. Visit https://confluent.cloud to manage your Confluent Cloud clusters.
Confluent Cloud
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance