Subscribe to UpdatesSubscribe
Get email notifications whenever Redis creates, updates or resolves an incident.
Get text message notifications whenever Redis creates or resolves an incident.
Visit our support site.
All Systems Operational
About This Site
Status and alerts are provided according to service endpoints or API.
Subscribe above to get up to minute alert notifications on any service interruption.
Admin Console
Operational
Heroku Integration
Operational
REST API
Operational
Support Site
Operational
DNS Resolvers
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Mar 6, 2026
Resolved -
This incident has been resolved.
Mar 6, 18:27 UTC
Mar 6, 18:27 UTC
Monitoring -
Urgent maintenance applies to all of the resources with the following pattern in their endpoint: c320
Mar 6, 15:20 UTC
Mar 6, 15:20 UTC
Mar 5, 2026
No incidents reported.
Mar 4, 2026
No incidents reported.
Mar 3, 2026
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.
Mar 3, 21:29 UTC
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.
Mar 3, 21:29 UTC
Update -
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.
Mar 3, 03:22 UTC
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.
Mar 3, 03:22 UTC
Update -
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.
Mar 2, 13:22 UTC
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.
Mar 2, 13:22 UTC
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.
Mar 1, 20:47 UTC
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.
Mar 1, 20:47 UTC
Update -
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.
Mar 1, 16:59 UTC
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.
Mar 1, 16:59 UTC
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.
Mar 1, 14:33 UTC
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.
Mar 1, 14:33 UTC
Resolved -
This incident has been resolved.
Mar 3, 18:12 UTC
Mar 3, 18:12 UTC
Monitoring -
Urgent maintenance applies to all of the resources with the following pattern in their endpoint: c17.us-east-1-4
Mar 3, 17:04 UTC
Mar 3, 17:04 UTC
Mar 2, 2026
Mar 1, 2026
Resolved -
This incident has been resolved.
Mar 1, 14:32 UTC
Mar 1, 14:32 UTC
Investigating -
We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: me-central-1b
Mar 1, 14:14 UTC
Mar 1, 14:14 UTC
Feb 28, 2026
No incidents reported.
Feb 27, 2026
No incidents reported.
Feb 26, 2026
No incidents reported.
Feb 25, 2026
No incidents reported.
Feb 24, 2026
Resolved -
Dear customer,
We’re transitioning our customer status page to a new platform on March 23 2026, to improve reliability and the overall experience.
What to expect:
- No impact to Redis services is expected from this change.
- If you’re subscribed to status notifications, you will receive a one-time subscription notification email during the transition. This is expected and confirms your subscription on the new platform.
RSS subscribers – action required:
If you follow updates via RSS, please update your feed URL to:
https://status.redis.io/data/rss.xml
We’ll post an update here when the transition is complete.
Feb 24, 04:52 UTC
We’re transitioning our customer status page to a new platform on March 23 2026, to improve reliability and the overall experience.
What to expect:
- No impact to Redis services is expected from this change.
- If you’re subscribed to status notifications, you will receive a one-time subscription notification email during the transition. This is expected and confirms your subscription on the new platform.
RSS subscribers – action required:
If you follow updates via RSS, please update your feed URL to:
https://status.redis.io/data/rss.xml
We’ll post an update here when the transition is complete.
Feb 24, 04:52 UTC
Feb 23, 2026
No incidents reported.
Feb 22, 2026
No incidents reported.
Feb 21, 2026
No incidents reported.
Feb 20, 2026
No incidents reported.