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

Affected components

• Confluent Cloud

1. resolvedSep 9, 2026, 14:56 UTC

   The systems have recovered and Confluent Cloud is fully operational.

2. monitoringSep 9, 2026, 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.

3. identifiedSep 9, 2026, 01:45 UTC

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

4. identifiedSep 9, 2026, 00:01 UTC

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

5. identifiedSep 8, 2026, 17:41 UTC

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

6. identifiedSep 8, 2026, 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

7. identifiedSep 8, 2026, 14:06 UTC

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

8. investigatingSep 8, 2026, 11:38 UTC

   We are currently investigating this issue.

9. identifiedSep 8, 2026, 10:37 UTC

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

10. investigatingSep 8, 2026, 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.

What APIStatus.watch saw

• Sep 8, 2026, 09:20 UTCoperational → partial outage
• Sep 9, 2026, 06:45 UTCpartial outage → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• ReadMe: Admin interface outageCritical · Sep 8, 2026, 16:04 UTC
• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• dbt Cloud: User Login Sessions TerminatedMajor · Sep 8, 2026, 18:44 UTC
• Miro: Sign-in with username and password is unavailableMajor · Sep 8, 2026, 19:21 UTC
• Shippo: Elevated error rates for the Lasership Transaction servicesMajor · Sep 8, 2026, 19:22 UTC
• Telnyx: Edge Compute StatefulActor Deploys Partial OutageMajor · Sep 8, 2026, 21:29 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Telnyx: Intermittent delays for some outbound messagesMinor · Sep 2, 2026, 21:33 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history