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

The systems have recovered and Confluent Cloud is fully operational.

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.

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

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

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

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

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

We are currently investigating this issue.

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

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.