What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Confluent Cloud now? Check the current statusAffected services
Updates (10)
- Sep 9, 2026, 02:56 PMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
The systems have recovered and Confluent Cloud is fully operational.
Confluent Cloud ↗ - Sep 9, 2026, 06:41 AMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
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 Cloud ↗ - Sep 9, 2026, 01:45 AMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.
Confluent Cloud ↗ - Sep 9, 2026, 12:01 AMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
Confluent is continuing to work on remediating the service disruption in AWS us-east-1.
Confluent Cloud ↗ - Sep 8, 2026, 05:41 PMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink 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.
Confluent Cloud ↗ - Sep 8, 2026, 03:55 PMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
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
Confluent Cloud ↗ - Sep 8, 2026, 02:06 PMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
The issue has been identified and a fix is being implemented.
Confluent Cloud ↗ - Sep 8, 2026, 11:38 AMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
We are currently investigating this issue.
Confluent Cloud ↗ - Sep 8, 2026, 10:37 AMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
The issue has been identified and a fix is being implemented.
Confluent Cloud ↗ - Sep 8, 2026, 09:17 AMService Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
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.
Confluent Cloud ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Confluent Cloud's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.