ChangesRedisAWS me-central-1 Zone Issue
Redis: Major incident: AWS me-central-1 Zone Issue
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Redis removed; blue is what they added. Muted text is unchanged context.
Before: not present
After: AWS me-central-1 Zone Issue
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-03-01 14:33 UTC
Before: not present
After: 2026-03-03 21:29 UTC
Before: not present
After: ➡️ **Investigating** — Type - network issues
Status - investigating
We are aware of an ongoing AWS service disruption impacting an availability zone within the me-central-1 region (zone ID: mec1az2). This zone may appear under different availability zone names across AWS accounts. As a result, some Redis Cloud clusters located in this zone may experience connectivity issues, increased latency, or temporary service interruptions.
Our teams are actively tracking the situation and working closely with AWS as they work toward full service restoration. We will continue to share updates as more information becomes available.
If you have any questions or are experiencing issues, please contact our Support team.
Before: not present
After: ➡️ **Investigating** — Update-
AWS is actively working to restore service following an ongoing disruption affecting an availability zone in the me-central-1 region (zone ID: mec1az2).
Some Redis Cloud clusters in this zone may continue to experience connectivity issues or increased latency while recovery is in progress.
We will provide additional updates as more information becomes available.
For further assistance, please contact our Support team.
Before: not present
After: ➡️ **Identified** — The issue impacting an availability zone in the me-central-1 region (zone ID: mec1az2) is still ongoing. AWS continues working toward full service restoration.
Some Redis Cloud clusters in this zone may still experience connectivity issues or increased latency. We will continue to share updates as more information becomes available.
For further assistance, please contact our Support team.
Before: not present
After: ➡️ **Identified** — The issue impacting an availability zone in the me-central-1 region (zone ID: mec1az2) is still ongoing. Restoration efforts are in progress.
Some Redis Cloud clusters in this zone may continue to experience connectivity issues or increased latency while service is being restored. We will provide further updates as more information becomes available.
For further assistance, please contact our Support team.
Before: not present
After: ➡️ **Identified** — Update — The issue impacting multiple Availability Zones in the me-central-1 (UAE) region remains ongoing. Recovery efforts are continuing, and restoration timelines may be extended due to the nature of the underlying infrastructure disruption.
Customers with workloads in mec1-az2 and mec1-az3 may continue to experience service degradation or availability issues. The mec1-az1 Availability Zone remains operational; however, capacity and deployment options may currently be limited. Customers are encouraged to follow AWS guidance and consider deploying workloads in alternate regions while recovery efforts continue.
AWS customers can continue monitoring updates directly via the AWS Account Health Dashboard - https://health.console.aws.amazon.com/
If you require assistance creating new subscriptions or migrating workloads to unaffected capacity, please contact Redis Support at support@redis.com.
We will continue to provide updates as more information becomes available.
Before: not present
After: ➡️ **Resolved** — UPDATE — The issue impacting availability in the AWS Middle East (UAE) Region (me-central-1) remains ongoing at the cloud provider level. While recovery efforts continue, the timeline for full restoration remains unclear. At this stage, Redis Cloud services are operating within the current regional constraints, and we are resolving this incident from active monitoring.
We recommend following AWS's current guidance, which is for customers to consider migrating workloads to alternate regions while recovery efforts continue. Redis Cloud supports workloads across multiple AWS and GCP regions, and customers may consider deploying in alternative locations such as ap-south-1 (Mumbai) or other unaffected regions.
Customers should continue monitoring updates via the AWS Health Dashboard:
https://health.console.aws.amazon.com/
If you require assistance planning or executing migrations, please contact support@redis.com. Our teams will also proactively reach out to impacted customers with additional best practices and support.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
History of this incident
Sunday, March 1
1 incident change
- OutageMajor incident
AWS me-central-1 Zone Issuethis change
Cite this
Major incident: AWS me-central-1 Zone Issue on Redis’s status page, changed 2026-03-01 14:33 UTC (change 1 of 1).
- Title
- Major incident: AWS me-central-1 Zone Issue
- Vendor
- Redis
- Date
- URL
- https://rewindex.com/change/ib2d79ec5cc5cda