← Outage Reports
Confluent logo
Confluent
confluent.io
⚠️ Outages Resolved

Confluent reports multiple service issues

Confluent is dealing with 2 concurrent service issues — tracked live below.

By The Downtime · Sep 8, 2026 · 8:15 PM ·Updated 1 month ago

Confluent is investigating a service disruption affecting client connectivity to Kafka clusters in the AWS us-east-1 region. The company has classified the incident as major impact and remains in investigating status.

Confluent provides managed Apache Kafka and stream processing services used by enterprises for real-time data pipelines and event streaming applications.

The company first reported the connectivity degradation and has continued investigating the underlying cause. No resolution timeline has been provided.

This is a developing story. The Downtime will provide updates as more information becomes available.

⚠️ Issues being tracked (2)

Connectivity degradation - AWS us-east-1
Resolved · 🇺🇸 US East
source ↗
Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
Resolved · 🇺🇸 US East
source ↗

🕒 Live updates (15)

resolved Service Disruption affecting Authenticat... Sep 9, 2:56 PM

The systems have recovered and Confluent Cloud is fully operational.

resolved Connectivity degradation - AWS us-east-1 Sep 9, 1:01 PM

The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.

monitoring Service Disruption affecting Authenticat... Sep 9, 6:41 AM

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.

identified Service Disruption affecting Authenticat... Sep 9, 1:45 AM

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

identified Service Disruption affecting Authenticat... Sep 9, 12:01 AM

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

monitoring Connectivity degradation - AWS us-east-1 Sep 8, 8:30 PM

A fix has been implemented and the team is monitoring recovery.

identified Connectivity degradation - AWS us-east-1 Sep 8, 8:20 PM

A possible root cause has been identified and the Confluent Cloud team is implementing a fix

investigating Connectivity degradation - AWS us-east-1 Sep 8, 8:13 PM

We are continuing to investigate this issue.

investigating Connectivity degradation - AWS us-east-1 Sep 8, 8:01 PM

We are investigating a service disruption affecting client connectivity to Kafka clusters in AWS us-east-1.

identified Service Disruption affecting Authenticat... Sep 8, 5:41 PM

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

identified Service Disruption affecting Authenticat... Sep 8, 3:55 PM

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

identified Service Disruption affecting Authenticat... Sep 8, 2:06 PM

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

investigating Service Disruption affecting Authenticat... Sep 8, 11:38 AM

We are currently investigating this issue.

identified Service Disruption affecting Authenticat... Sep 8, 10:37 AM

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

investigating Service Disruption affecting Authenticat... Sep 8, 9:17 AM

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.

📎 Sources

Outage details are aggregated from official provider status pages. The Downtime reports them as a public service and is not affiliated with the providers named.

💬 Comments (0)

No comments yet — be the first to weigh in.

Join the conversation.