Changes / Confluent / Elevated Error Rates in AWS me-central-1 region

Confluent: Major incident: Elevated Error Rates in AWS me-central-1 region

Summary

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 diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 73%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Elevated Error Rates in AWS me-central-1 region
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-03-01 18:08 UTC
AddedResolved time#5
Before: not present
After: 2026-03-01 22:05 UTC
AddedAffected components#6
Before: not present
After: Confluent Cloud
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateidentified#8
Before: not present
After: 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.
AddedUpdatemonitoring#9
Before: not present
After: 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.
AddedUpdateresolved#10
Before: not present
After: This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Elevated Error Rates in AWS me-central-1 region (this change)
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.
Major incident

All Confluent changes → · Confluent profile · Markdown · JSON