Outage in Confluent
Elevated Error Rates in AWS me-central-1 region
Resolved MajorIncident Report
Summary AI Generated
Confluent Cloud services in the AWS me-central-1 region experienced elevated error rates for 4 hours starting at 12:51 PM UTC, caused by a disruption in AWS availability zone mec1-az2. The team identified the root cause as the AWS infrastructure issue and implemented mitigation steps to restore service health. All Confluent Cloud services in the region were fully restored and healthy by 21:15 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.
Components affected
Confluent CloudTrusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Start Free Trial
- No credit card
- 14-day trial
- 2-minute setup
Latest Updates ( sorted recent to last )
RESOLVED
about 2 months ago - at 03/01/2026 10:05PM
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
MONITORING
about 2 months ago - at 03/01/2026 09:41PM
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.
IDENTIFIED
about 2 months ago - at 03/01/2026 06:48PM
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.
INVESTIGATING
about 2 months ago - at 03/01/2026 06:08PM
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.
Latest Confluent outages
Metrics API was experiencing failures from 03:23 UTC to 03:58 UTC - about 1 month ago
Elevated error rates in AWS me-south-1 and me-central-1 regions - about 2 months ago
All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failing - about 2 months ago
Network provisioning service in Azure East US region is degraded - about 2 months ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
