All Systems Operational
About This Site
Welcome to Confluent Cloud's status page. Here you will find high level availability information for the Confluent Cloud managed service. Visit https://confluent.cloud to manage your Confluent Cloud clusters.
Confluent Cloud
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Sep 16, 2026
Resolved -
This incident has been resolved.
Sep 16, 01:21 UTC
Sep 16, 01:21 UTC
Monitoring -
The mitigation has been deployed and the degraded services are recovering as of 00:20 UTC on September 16th, 2026. We'll continue to monitor for any residual issues before resolving this incident in 1 hour (01:20 UTC).
Sep 16, 00:22 UTC
Sep 16, 00:22 UTC
Identified -
The issue has been identified and a fix is being implemented.
Sep 16, 00:00 UTC
Sep 16, 00:00 UTC
Investigating -
Starting on Tuesday, September 15th 2026 at 21:25 UTC, multiple Confluent Cloud services began entering a degraded state. We have identified the cause of the degradation and are actively mitigating the issue. Updates will be posted here in the next 30 minutes or when the issue is fully mitigated, whichever happens first.
Sep 15, 23:59 UTC
Sep 15, 23:59 UTC
Sep 15, 2026
Sep 14, 2026
No incidents reported.
Sep 13, 2026
No incidents reported.
Sep 12, 2026
No incidents reported.
Sep 11, 2026
No incidents reported.
Sep 10, 2026
No incidents reported.
Sep 9, 2026
Resolved -
The systems have recovered and Confluent Cloud is fully operational.
Sep 9, 14:56 UTC
Sep 9, 14:56 UTC
Monitoring -
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.
Sep 9, 06:41 UTC
Sep 9, 06:41 UTC
Update -
Confluent is continuing to work on the service disruption in AWS us-east-1. No immediate ETA for resolution is available.
Sep 9, 01:45 UTC
Sep 9, 01:45 UTC
Update -
Confluent is continuing to work on remediating the service disruption in AWS us-east-1.
Sep 9, 00:01 UTC
Sep 9, 00:01 UTC
Update -
We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.
Sep 8, 17:41 UTC
Sep 8, 17:41 UTC
Update -
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
Sep 8, 15:55 UTC
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
Sep 8, 15:55 UTC
Identified -
The issue has been identified and a fix is being implemented.
Sep 8, 14:06 UTC
Sep 8, 14:06 UTC
Investigating -
We are currently investigating this issue.
Sep 8, 11:38 UTC
Sep 8, 11:38 UTC
Identified -
The issue has been identified and a fix is being implemented.
Sep 8, 10:37 UTC
Sep 8, 10:37 UTC
Investigating -
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.
Sep 8, 09:17 UTC
Sep 8, 09:17 UTC
Resolved -
The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.
Sep 9, 13:01 UTC
Sep 9, 13:01 UTC
Monitoring -
A fix has been implemented and the team is monitoring recovery.
Sep 8, 20:30 UTC
Sep 8, 20:30 UTC
Identified -
A possible root cause has been identified and the Confluent Cloud team is implementing a fix
Sep 8, 20:20 UTC
Sep 8, 20:20 UTC
Update -
We are continuing to investigate this issue.
Sep 8, 20:13 UTC
Sep 8, 20:13 UTC
Investigating -
We are investigating a service disruption affecting connectivity to Kafka clusters in AWS us-east-1.
Sep 8, 20:01 UTC
Sep 8, 20:01 UTC
Sep 8, 2026
Sep 7, 2026
No incidents reported.
Sep 6, 2026
No incidents reported.
Sep 5, 2026
No incidents reported.
Sep 4, 2026
No incidents reported.
Sep 3, 2026
No incidents reported.
Sep 2, 2026
No incidents reported.