Resolved after 3 hours 57 minutes, affecting Confluent Cloud, on March 1, 2026.
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
Affected components
Update timeline
- investigating Mar 01, 2026, 06:08 PM UTC
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.
- identified Mar 01, 2026, 06:48 PM UTC
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.
- monitoring Mar 01, 2026, 09:41 PM UTC
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.
- resolved Mar 01, 2026, 10:05 PM UTC
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
Your product runs on more than Confluent
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services