Elevated Error Rates in AWS me-central-1 region
Mar 1, 18:08 UTCMar 1, 22:05 UTC
Duration
3h 57m
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
20 incidents
Affected
Confluent Cloud
Final update
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
Timeline
- Resolved · Mar 1, 22:05 UTC
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
- 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.
- 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.
- 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 historyKafka - Increased latency and connectivity issues - Azure - brazilsouthlasted 2h 9mMultiple Confluent Cloud services are in a degraded state - GCP EU-West2lasted 10h 25mDelay in Kafka cluster provisioninglasted 7h 18mConfluent Cloud Console (UI) degraded functionalitylasted 2h 45mPossible outage in AWS us-east-1lasted 56mExperiencing high error rate in AZURE in West Europe regionlasted 20h 2m