Live  /  Confluent Cloud  /  Incident

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

Confluent Cloud · confluent.cloudMinor incidentResolved2026-09-09 06:41 UTC
Public — what happened

Summary

Confluent Cloud reported a disruption in its AWS us-east-1 region affecting Authentication, Schema Registry, ksqlDB, Flink, and Kafka operations, which began on 2026-09-08 at 09:17 UTC and was rated minor. The company said it had put a mitigation in place and that the affected services were coming back. Confluent Cloud did not name a cause and was still watching the situation, with the incident marked resolved at 15:03 on 2026-09-09.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Confluent Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Confluent Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Confluent Cloud report →

More from Confluent Cloud

Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.

The full archive is on the Confluent Cloud status & history page.

Related: Confluent Cloud status & history. SquidGrid is not affiliated with Confluent Cloud.