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.
This incident has been resolved. All Confluent Cloud services are now healthy in me-central-1 region.
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.
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.
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.
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 · 6020 services available
Integrations with