Elevated error rates in AWS me-south-1 and me-central-1 regions
Apr 1, 19:52 UTCJul 16, 03:21 UTC
Duration
105d 7h
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
16 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 history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2311:47 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 11h 30m |
| Sep 2215:09 UTC | Elevated error rates in Azure Germany West Central region | major | 4h 50m |
| Sep 2116:15 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 9h 16m |
| Sep 1717:49 UTC | Confluent Cloud Metrics API experienced elevated latency and error rates | none | 0m |
| Sep 1523:59 UTC | Multiple Confluent Cloud services are in a degraded state - All regions | major | 1h 22m |
| Sep 820:01 UTC | Connectivity degradation - AWS us-east-1 | major | 17h |
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.