Connectivity degradation - AWS us-east-1
Last updateresolvedSep 9 · 13:01 UTC
The issues is now resolved. Connectivity to AWS us-east-1 should be fully operational.
Reported by Confluent Cloud on their status page.
checked Sep 14, 2026 6:46 AM UTC · Confluent Cloud's official status page
Confluent Cloud is up and running.
Confluent Cloud is currently operational with all systems functioning normally.
All components operational
Email only. No password. No card.
Be the first to know
Statusfield watches Confluent Cloud alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
Confluent Cloud incident history
6 reports published by Confluent Cloud in the last 30 days
When Confluent Cloud breaks, it is typically resolved in 2h 38m — median across 10 resolved incidents over 90 days.
September 8, 2026
Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1
Last updateresolvedSep 9 · 14:56 UTC
The systems have recovered and Confluent Cloud is fully operational.
Reported by Confluent Cloud on their status page.
September 1, 2026
Investigating Elevated Errors in GCP us-central1
Last updateresolvedSep 1 · 17:14 UTC
The GCP issue affecting the us-central1 region has been mitigated and all Confluent Cloud services in the region have returned to normal operation. Provisioning capability, error rates and latency have recovered to expected levels. Customers should no longer experience impact. If you continue to see any issues, please contact Confluent Support.
Reported by Confluent Cloud on their status page.
August 25, 2026
Elevated error rates and latencies in Azure Southeast Asia region
Last updateresolvedAug 25 · 07:29 UTC
Confluent services in the Azure Southeast Asia region are now healthy and operating normally.
Reported by Confluent Cloud on their status page.
August 23, 2026
Confluent Cloud logging degradation - Connect and Flink
Last updateresolvedAug 23 · 21:00 UTC
Between 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.
Reported by Confluent Cloud on their status page.
August 20, 2026
Elevated error rates and latency in GCP us-west1
Last updateresolvedAug 20 · 20:18 UTC
The GCP issues in us-west1 region have been mitigated. Confluent services are no longer seeing any impact based on our monitoring.
Reported by Confluent Cloud on their status page.