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

Final update

The systems have recovered and Confluent Cloud is fully operational.

1. Resolved · Sep 9, 14:56 UTC
   The systems have recovered and Confluent Cloud is fully operational.
2. Monitoring · Sep 9, 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. Identified · Sep 9, 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. Identified · Sep 9, 00:01 UTC
   Confluent is continuing to work on remediating the service disruption in AWS us-east-1.
5. Identified · Sep 8, 17:41 UTC
   We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.
6. Identified · Sep 8, 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. Identified · Sep 8, 14:06 UTC
   The issue has been identified and a fix is being implemented.
8. Investigating · Sep 8, 11:38 UTC
   We are currently investigating this issue.
9. Identified · Sep 8, 10:37 UTC
   The issue has been identified and a fix is being implemented.
10. Investigating · Sep 8, 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.