Skip to content
Confluent · Data and observabilityMar 1, 2026, 18:08 UTC

Elevated Error Rates in AWS me-central-1 region

MajorNot disclosedUpdated 37h ago
Mar 1, 18:08 UTCMar 1, 22:05 UTC
Duration
3h 57m
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
16 incidents
Affected
Confluent Cloud
Status page

Final update

This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.

Timeline

  1. Resolved · Mar 1, 22:05 UTC
    This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
  2. Monitoring · Mar 1, 21:41 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.
  3. Identified · Mar 1, 18:48 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.
  4. Investigating · Mar 1, 18:08 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.

More from Confluent

Full history

Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Outages by email

Saturday mornings: the week's major outages, new postmortems and disclosed breaches, only in weeks that had some.

Double opt-in. Unsubscribe any time.