Companies / Confluent / incidents
Confluent: Elevated Error Rates in AWS me-central-1 region
Confluent Cloud experienced elevated errors in AWS me-central-1 due to disruption in AWS availability zone mec1-az2, with major impact. Errors began approximately 12:51 PM UTC; the incident was recorded from 2026-03-01 18:08 UTC to 2026-03-01 22:05 UTC (3 h 57 min). Confluent applied mitigation and reported all regional services healthy.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Confluent Cloud
Timeline of updates
- investigating
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
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
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
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
Rewindex changes for this incident
- Major incident: Elevated Error Rates in AWS me-central-1 region 2026-03-01 18:08 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Confluent profile · Recent Confluent incidents · Markdown · JSON