Incidentsby GlyphElevated error rates in AWS me-south-1 and me-central-1 regions
Mar 20, 13:58 UTCJul 16, 03:21 UTC
Duration
117d 13h
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
20 incidents
Affected
Confluent Cloud
Final update
Resolved.
Timeline
- Resolved · Jul 16, 03:21 UTC
Resolved.
- Monitoring · Apr 2, 15:40 UTC
Per AWS, the me-south-1 region is now completely unavailable. Customers will not be able to access clusters in the me-south-1 region. Customers who have workloads in me-central-1 are strongly advised to relocate them to an alternative region.
- Monitoring · Apr 1, 19:52 UTC
Provisioning new workloads in AWS me-central-1 and me-south-1 regions is disabled. Migration steps to other AWS regions have been communicated to impacted customers.
- Monitoring · Mar 20, 13:58 UTC
AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.
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