Confluent incident

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

Minor Resolved View vendor source →

Confluent experienced a minor incident on September 8, 2026 affecting Confluent Cloud, lasting 1d 5h. The incident has been resolved; the full update timeline is below.

Started
Sep 08, 2026, 09:17 AM UTC
Resolved
Sep 09, 2026, 02:56 PM UTC
Duration
1d 5h
Detected by Pingoru
Sep 08, 2026, 09:17 AM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Sep 08, 2026, 09:17 AM 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. identified Sep 08, 2026, 10:37 AM UTC

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

  3. investigating Sep 08, 2026, 11:38 AM UTC

    We are currently investigating this issue.

  4. identified Sep 08, 2026, 02:06 PM UTC

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

  5. identified Sep 08, 2026, 03:55 PM 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. identified Sep 08, 2026, 05:41 PM UTC

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

  7. identified Sep 09, 2026, 12:01 AM UTC

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

  8. identified Sep 09, 2026, 01:45 AM UTC

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

  9. monitoring Sep 09, 2026, 06:41 AM 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. resolved Sep 09, 2026, 02:56 PM UTC

    The systems have recovered and Confluent Cloud is fully operational.