What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Confluent Cloud now? Check the current statusAffected services
Updates (4)
- Mar 1, 2026, 10:05 PMElevated Error Rates in AWS me-central-1 region
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
Confluent Cloud ↗ - Mar 1, 2026, 09:41 PMElevated Error Rates in AWS me-central-1 region
The problem has been mitigated as of 21:15 PM UTC today. All Confluent Cloud services are now healthy in me-central-1 region and we will monitor for any residual issues before resolving this incident in 1 hour.
Confluent Cloud ↗ - Mar 1, 2026, 06:48 PMElevated Error Rates in AWS me-central-1 region
We have identified the cause of the problem to be disruption in one of AWS’s availability zones (mec1-az2). We are taking steps to confirm the safest path to mitigation for any impacted Confluent Cloud services in this region.
Confluent Cloud ↗ - Mar 1, 2026, 06:08 PMElevated Error Rates in AWS me-central-1 region
We are experiencing increased error rates in some of our Confluent Cloud services in the AWS me-central-1 region. This began at approximately 12:51 PM UTC today and is linked to a disruption in one of AWS’s availability zones (mec1-az2). Our team is actively applying mitigation steps and will provide updates as the situation evolves.
Confluent Cloud ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Confluent Cloud's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.