Confluent Status
Maintenance
Last incident: 5/8/2026
Current Status
Overall StatusMaintenance
Last IncidentElevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
Incident Statusmonitoring
Recent Incidents
Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4
5/8/2026, 1:14:00 AM
AWS has reported the underlying infrastructure issue in us-east-1 (use1-az4) as resolved. However, some Confluent Cloud customers in the affected availability zone continue to experience connectivity issues.
Confluent is actively investigating and working to restore full connectivity for impacted customers.
Affected Components:
Confluent Cloud
Scheduled Confluent Cloud maintenance on May 6, 2026
5/6/2026, 10:12:13 PM
The maintenance is complete.
Affected Components:
Confluent Cloud
Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements
4/24/2026, 5:18:15 PM
This incident has been resolved.
Affected Components:
Confluent Cloud
Experiencing delays in Tableflow external catalog syncs in AWS
4/21/2026, 9:34:28 AM
This incident has been resolved.
Affected Components:
Confluent Cloud
Elevated error rates in AWS me-south-1 and me-central-1 regions
3/20/2026, 1:58:18 PM
Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
Affected Components:
Confluent Cloud