Companies / Confluent / incidents

Confluent: Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1

Affected components: Confluent Cloud

Timeline of updates

1. investigating2026-09-08 09:17 UTC

   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.

2. identified2026-09-08 10:37 UTC

   The issue has been identified and a fix is being implemented.

3. investigating2026-09-08 11:38 UTC

   We are currently investigating this issue.

4. identified2026-09-08 14:06 UTC

   The issue has been identified and a fix is being implemented.

5. identified2026-09-08 15:55 UTC

   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

6. identified2026-09-08 17:41 UTC

   We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.

7. identified2026-09-09 00:01 UTC

   Confluent is continuing to work on remediating the service disruption in AWS us-east-1.

8. identified2026-09-09 01:45 UTC

   Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.

9. monitoring2026-09-09 06:41 UTC

   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.

10. resolved2026-09-09 14:56 UTC

    The systems have recovered and Confluent Cloud is fully operational.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON