Redis Outage History

Started Oct 20, 2026, 06:47 AM UTC· resolved Oct 20, 2026, 05:23 PM UTC

1. monitoring Oct 20, 2026, 06:48 AM UTC

   We are aware of an issue in GCP region europe-west2 (London), zone europe-west2-b and are actively investigating. If you experience any impact, please contact our Support team.

2. monitoring Oct 20, 2026, 07:42 AM UTC

   We continue to closely monitor the issues affecting GCP region europe-west2 and zone europe-west2-b. Restoring services remains our top priority. If you have questions or need assistance, please contact our support team

3. monitoring Oct 20, 2026, 08:46 AM UTC

   Our teams are actively monitoring the service disruption affecting the GCP europe-west2 region and europe-west2-b zone. Service restoration remains our highest priority, and we will provide further updates as they become available. For assistance, please contact our Support team.

4. monitoring Oct 20, 2026, 09:31 AM UTC

   We are still actively monitoring the service disruption affecting the GCP europe-west2 region and europe-west2-b zone. Our teams remain focused on restoring services as quickly as possible. We will provide further updates as they become available. If you require assistance, please contact our Support team.

5. monitoring Oct 20, 2026, 11:20 AM UTC

   We continue to monitor the disruption affecting GCP europe-west2 and europe-west2-b while working to restore services. Please contact Support if you need assistance.

6. monitoring Oct 20, 2026, 12:21 PM UTC

   The GCP power outage affecting the europe-west2 region and europe-west2-b zone has been mitigated, and the underlying GCP infrastructure has partially recovered. Our teams have initiated recovery procedures and are actively working to restore all affected services. We will continue monitoring the recovery and provide further updates as they become available. If you require assistance, please contact our Support team.

7. monitoring Oct 20, 2026, 01:54 PM UTC

   Our teams are continuing with the recovery procedures and are actively working to restore all affected services. We will provide further updates as they occur. If you require assistance, please contact our Support team.

8. monitoring Oct 20, 2026, 05:23 PM UTC

   All environments have been returned to a full operational state at this time. Please contact our Support team if there are questions or assistance is needed.

Read the full incident report →

Started Sep 05, 2026, 12:58 PM UTC· resolved Sep 05, 2026, 01:39 PM UTC

1. monitoring Sep 05, 2026, 01:00 PM UTC

   We’re currently investigating an issue affecting Redis IRIS functionality. Our team is actively working to restore normal service. We’ll provide another update as soon as more information is available.

2. monitoring Sep 05, 2026, 01:39 PM UTC

   This issue is now resolved, if you see or experience any additional issues, please contact https://redis.io/support/

Read the full incident report →

Started Sep 01, 2026, 04:00 PM UTC· resolved Sep 01, 2026, 07:31 PM UTC

1. monitoring Sep 01, 2026, 04:01 PM UTC

   We are aware of an issue in GCP US-Central1 and are actively investigating. If you experience any impact, please contact our Support team.

2. monitoring Sep 01, 2026, 05:27 PM UTC

   We continue to monitor the ongoing GCP US-Central1 event. Currently, our services are operating normally. For questions or assistance, please contact [email protected]

3. monitoring Sep 01, 2026, 07:21 PM UTC

   We continue to closely monitor the GCP US-Central1 event. Our services remain operational and are performing normally. For questions or assistance, please contact [email protected]

4. monitoring Sep 01, 2026, 07:30 PM UTC

   GCP has confirmed that the US-Central1 event is resolved. Our services are operating normally, and we are marking this issue as closed. If you have any questions or need assistance, please contact [email protected].

Read the full incident report →

Started Jul 17, 2026, 02:02 AM UTC· resolved Jul 17, 2026, 11:56 AM UTC

1. monitoring Jul 17, 2026, 02:03 AM UTC

   We have identified an issue with one of our upstream cloud service providers affecting GCP US East. We are actively working with our provider to resolve the issue and will share updates as progress is made. For questions or assistance, please contact [email protected].

2. monitoring Jul 17, 2026, 03:30 AM UTC

   Regional Network Issues — Monitoring Our monitoring indicates that services in GCP US East have recovered, and Redis Cloud clusters in the region are currently operating normally. However, our upstream cloud provider has not yet confirmed full resolution of the underlying issue on their end. Out of an abundance of caution, we will continue to actively monitor the region until the provider confirms the incident is resolved. We will post a final update at that time. For questions or assistance, please contact [email protected].

3. monitoring Jul 17, 2026, 11:59 AM UTC

   The issue impacting the services in GCP US East have been resolved. Our upstream cloud provider has confirmed full resolution of the underlying issue on their end. For questions or assistance, please contact [email protected]

Read the full incident report →

Started Jul 15, 2026, 10:33 PM UTC· resolved Jul 16, 2026, 03:31 AM UTC

1. monitoring Jul 15, 2026, 10:33 PM UTC

   We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: C293

2. monitoring Jul 16, 2026, 12:29 AM UTC

   We have identified an issue with one of our upstream cloud service providers affecting the EU-Central-1 region. We are actively working with our provider to resolve the issue and will share updates as progress is made. For questions or assistance, please contact [email protected].

3. monitoring Jul 16, 2026, 02:37 AM UTC

   We continue to work on the recovery process post CSP issues within the EU Region affecting C293. We will provide continued updates as we recover the environment. For questions or assistance, please contact [email protected]

4. monitoring Jul 16, 2026, 03:31 AM UTC

   The connections issues affecting some resources with the following pattern in their endpoint: C293 have been resolved.

Read the full incident report →

Started Jun 28, 2026, 08:52 AM UTC· resolved Jun 28, 2026, 09:09 AM UTC

1. monitoring Jun 28, 2026, 08:55 AM UTC

   We’re currently investigating issues with connecting to Redis Cloud admin console (cloud.redis.io). We will provide an update shortly. Your database’s connectivity is not affected.

2. monitoring Jun 28, 2026, 09:10 AM UTC

   The issue has been fully resolved. Should you encounter any remaining issues, please contact our support team via our Support Portal(https://support.redislabs.com/hc/en-us/requests/new). Thank you for your patience.

Read the full incident report →

Started Jun 16, 2026, 06:38 PM UTC· resolved Jun 16, 2026, 07:13 PM UTC

1. monitoring Jun 16, 2026, 06:38 PM UTC

   We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c270

2. monitoring Jun 16, 2026, 07:17 PM UTC

   The instance failure issue affecting some resources with the following pattern in their endpoint: c270 has been resolved. Our team has confirmed that connectivity has returned to normal and impacted resources are operating as expected. We will continue to monitor the environment to ensure stability. Thank you for your patience while we investigated and resolved this issue.

Read the full incident report →

Started Jun 07, 2026, 01:08 PM UTC· resolved Jun 09, 2026, 09:02 PM UTC

1. monitoring Jun 07, 2026, 01:09 PM UTC

   We are investigating an issue affecting a subset of LangCache deployments in the GCP us-east4 region. Customers using affected LangCache caches may experience service disruptions. LangCache deployments in other regions and cloud providers are not impacted. Our team is actively investigating and will provide updates as more information becomes available.

2. monitoring Jun 07, 2026, 02:24 PM UTC

   We have identified the cause of the issue affecting a subset of LangCache deployments in the GCP us-east4 region and are actively monitoring progress toward full resolution. LangCache deployments in other regions and cloud providers remain unaffected. We will continue to provide updates as they become available.

3. monitoring Jun 09, 2026, 09:02 PM UTC

   We are concluding public updates for this incident related to a subset of LangCache deployments in the GCP us-east4 region. Our team will continue to manage any remaining remediation through follow-up processes. LangCache deployments in other regions and cloud providers remain unaffected. If you experience any issues, please contact our support team for assistance.

Read the full incident report →

Started Jun 07, 2026, 09:39 AM UTC· resolved Jun 07, 2026, 12:59 PM UTC

1. monitoring Jun 07, 2026, 09:41 AM UTC

   Until this event is fully mitigated, please submit any support requests via [email protected].

2. monitoring Jun 07, 2026, 11:33 AM UTC

   The Redis Cloud Admin Console is operating normally and is accessible to customers. We are continuing to investigate a separate issue affecting LangCache functionality and will provide additional updates as more information becomes available.

3. monitoring Jun 07, 2026, 12:59 PM UTC

   We have completed the maintenance activity. Services have been restored to normal operation, and we are monitoring to ensure continued stability.

Read the full incident report →

Started Jun 03, 2026, 10:31 PM UTC· resolved Jun 03, 2026, 10:34 PM UTC

1. monitoring Jun 03, 2026, 10:31 PM UTC

   We are currently investigating network issues to some resources that have the following pattern in their endpoint: c277

Read the full incident report →

Started May 31, 2026, 08:48 AM UTC· resolved May 31, 2026, 09:03 AM UTC

1. monitoring May 31, 2026, 08:48 AM UTC

   Service maintenance applies to all of the resources with the following pattern in their endpoint : SM_S208_76

2. monitoring May 31, 2026, 09:01 AM UTC

   We have completed the maintenance activity. Services have been restored to normal operation, and we are monitoring to ensure continued stability.

Read the full incident report →

Started May 28, 2026, 11:56 PM UTC· resolved May 29, 2026, 12:10 AM UTC

1. monitoring May 28, 2026, 11:56 PM UTC

   We are currently investigating network issues to some resources that have the following pattern in their endpoint: c282

2. monitoring May 28, 2026, 11:57 PM UTC

   We are experiencing some network issues. This may affect resources that have the following pattern in their endpoint: c282

3. monitoring May 29, 2026, 12:10 AM UTC

   Incident is resolved.

Read the full incident report →

Started May 18, 2026, 04:52 PM UTC· resolved May 18, 2026, 07:49 PM UTC

1. monitoring May 18, 2026, 04:54 PM UTC

   We are currently investigating connectivity issues with some resources that have the following pattern in their endpoint: c278. Some resources in this cluster may be impacted. We will continue to update until the resolution.

2. monitoring May 18, 2026, 05:16 PM UTC

   We have identified the issue and are currently working on the resolution steps. Thank you for your patience.

3. monitoring May 18, 2026, 05:56 PM UTC

   Our teams have made progress in the resolution effort and are actively applying mitigation steps. We are continuing to monitor recovery and work toward full resolution.

4. monitoring May 18, 2026, 06:27 PM UTC

   Our teams have made progress in the resolution effort and are actively applying mitigation steps. We are continuing to monitor recovery and work toward full resolution.

5. monitoring May 18, 2026, 07:20 PM UTC

   Our teams continue to focus on the resolution steps to fully resolve this issue. Thank you for your continued patience.

6. monitoring May 18, 2026, 07:49 PM UTC

   The incident has been resolved. We will continue to monitor system performance to ensure ongoing stability. If you continue to experience any issues, please contact our support team for assistance.

Read the full incident report →

Started May 13, 2026, 04:07 PM UTC· resolved May 13, 2026, 07:05 PM UTC

1. monitoring May 13, 2026, 04:09 PM UTC

   We are currently investigating connectivity issues with some resources that have the following pattern in their endpoint: c265. Some resources in this cluster may be impacted. We will continue to update until the resolution.

2. monitoring May 13, 2026, 04:32 PM UTC

   We have identified the issue and are currently working on the resolution steps. Thank you for your patience.

3. monitoring May 13, 2026, 05:23 PM UTC

   Our teams continue to focus on the resolution steps to fully resolve this issue. Thank you for your continued patience.

4. monitoring May 13, 2026, 06:36 PM UTC

   Our teams have made progress in the resolution effort and are actively applying mitigation steps. We are continuing to monitor recovery and work toward full resolution.

5. monitoring May 13, 2026, 06:50 PM UTC

   The issue has been fully resolved. Should you encounter any remaining issues, please contact our support team via our support portal. Thank you for your patience.

Read the full incident report →

Started May 10, 2026, 10:53 AM UTC· resolved May 10, 2026, 03:41 PM UTC

1. monitoring May 10, 2026, 10:54 AM UTC

   We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c240

2. monitoring May 10, 2026, 11:02 AM UTC

   We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c240

3. monitoring May 10, 2026, 11:47 AM UTC

   Our teams continue to investigate the instance failure issue in order to resolve it. We will continue to update as we progress. Thank you for your continued patience.

4. monitoring May 10, 2026, 01:27 PM UTC

   Our teams are still working on the instance failure issue in order to restore the service. Thank you for your patience.

5. monitoring May 10, 2026, 02:44 PM UTC

   We have identified the issue and are currently working on the resolution steps. Thank you for your patience.

6. monitoring May 10, 2026, 03:41 PM UTC

   The incident has been resolved. We will continue to monitor system performance to ensure ongoing stability. If you continue to experience any issues, please contact our support team for assistance.

Read the full incident report →

Started May 08, 2026, 12:01 AM UTC· resolved May 09, 2026, 04:20 PM UTC

1. monitoring May 08, 2026, 12:15 AM UTC

   We are investigating intermittent network connectivity issues impacting services hosted in AWS us-east-1 due to an ongoing AWS EC2 infrastructure issue in the region. Our teams are actively monitoring the situation and working to mitigate impact where possible. We will continue to provide updates as more information becomes available. If you have any questions or require assistance, please contact [email protected].

2. monitoring May 08, 2026, 01:00 AM UTC

   We have identified the cause of the intermittent network connectivity issues impacting services hosted in AWS us-east-1 as an ongoing AWS EC2 infrastructure issue in the region. Our teams are actively working to mitigate impact where possible and are closely monitoring AWS for updates and recovery progress. We will continue to provide timely updates as more information becomes available. If you have any questions or require assistance, please contact [email protected].

3. monitoring May 08, 2026, 01:50 AM UTC

   We continue to monitor the intermittent network connectivity issues impacting services hosted in AWS us-east-1, which have been identified as related to an ongoing AWS EC2 infrastructure issue in the region. Our teams are actively engaged and working closely with our partners at AWS to monitor recovery progress and mitigate impact where possible. We will continue to provide updates as new information becomes available. If you have any questions or require assistance, please contact [email protected].

4. monitoring May 08, 2026, 02:35 AM UTC

   We continue to monitor the intermittent network connectivity issues impacting services in the us-east-1 region. There have been no significant changes since the last update. The issue remains related to underlying AWS infrastructure impairments, and recovery is in progress. We are closely tracking the situation and will provide further updates as soon as more information becomes available. If you have any questions or require assistance, please contact [email protected].

5. monitoring May 08, 2026, 04:17 AM UTC

   We are continuing to monitor intermittent network connectivity issues affecting services hosted in AWS us-east-1. These issues have been identified as related to an ongoing AWS EC2 infrastructure issue in the region. Our teams are actively engaged and working closely with AWS to track recovery progress and mitigate customer impact wherever possible. We will share additional updates as more information becomes available. For questions or assistance, please contact [email protected]

6. monitoring May 08, 2026, 05:37 AM UTC

   We are continuing to monitor intermittent network connectivity issues affecting services hosted in AWS us-east-1. These issues have been identified as related to an ongoing AWS EC2 infrastructure issue in the region. Our teams are actively engaged and working closely with AWS to track recovery progress and mitigate customer impact wherever possible. We will share additional updates as more information becomes available. For questions or assistance, please contact [email protected]

7. monitoring May 08, 2026, 06:58 AM UTC

   We are continuing to monitor an ongoing AWS infrastructure issue affecting the us-east-1 region. This issue is impacting EC2 instances and EBS volumes, which may result in elevated error rates, increased latency, and intermittent connectivity issues for some services. AWS is actively working on recovery, and our teams are closely monitoring the situation while taking steps to mitigate customer impact where possible.Some services may remain degraded until AWS completes full recovery. We will share additional updates as more information becomes available. For questions or assistance, please contact [email protected]

8. monitoring May 08, 2026, 09:59 AM UTC

   We are continuing to monitor an ongoing AWS infrastructure issue affecting the us-east-1 region. This issue is impacting EC2 instances and EBS volumes, which may result in elevated error rates, increased latency, and intermittent connectivity issues for some services. AWS is actively working on recovery, and our teams are closely monitoring the situation while taking steps to mitigate customer impact where possible.Some services may remain degraded until AWS completes full recovery. We will share additional updates as more information becomes available. For questions or assistance, please contact [email protected]

9. monitoring May 08, 2026, 11:13 AM UTC

   We are still observing impact from the ongoing infrastructure issue in the us-east-1 region. There has been no material change since our last update. The issue continues to affect underlying AWS compute and storage resources, which may result in intermittent connectivity issues, increased latency, and elevated error rates for some services. AWS recovery efforts are ongoing at the infrastructure level. We remain focused on monitoring the situation and will share updates as soon as new information is available. For questions or assistance, please contact [email protected].

10. monitoring May 08, 2026, 12:30 PM UTC

    We’re continuing to closely monitor the issue affecting services in the AWS us-east-1 region. We’ll share more information as soon as it becomes available. For questions or assistance, please contact [email protected].

11. monitoring May 08, 2026, 01:36 PM UTC

    We’re continuing to monitor the issue affecting services in the AWS us-east-1 region. Recovery efforts are ongoing at the infrastructure level within AWS, and while progress is being made, some services may continue to experience intermittent impact. We’ll share further updates as more information becomes available. For questions or assistance, please contact [email protected].

12. monitoring May 08, 2026, 02:33 PM UTC

    We’re continuing to closely monitor the issue affecting services in the AWS us-east-1 region. We’ll share more information as soon as it becomes available. For questions or assistance, please contact [email protected].

13. monitoring May 08, 2026, 04:14 PM UTC

    We’re continuing to monitor the issue affecting services in the AWS us-east-1 region. AWS recovery is progressing incrementally at the infrastructure level, though some services may continue to experience intermittent impact during this time. We’ll share further updates as more information becomes available. For questions or assistance, please contact [email protected].

14. monitoring May 08, 2026, 06:22 PM UTC

    We’re continuing to monitor the issue affecting services in the AWS us-east-1 region as AWS recovery efforts continue. We’ll share updates as more information becomes available. For questions or assistance, please contact [email protected].

15. monitoring May 08, 2026, 08:20 PM UTC

    We’re continuing to monitor the issue affecting services in the AWS us-east-1 region as AWS works toward recovery. AWS has indicated that recovery of impaired EC2 instances and degraded EBS volumes in us-east-1 region is progressing slower than anticipated. Affected resources may continue to experience impairments during this time. We’ll share further updates as more information becomes available. For questions or assistance, please contact [email protected].

16. monitoring May 08, 2026, 10:14 PM UTC

    We’re continuing to monitor the issue affecting services in the AWS us-east-1 region as AWS recovery efforts remain ongoing. AWS has indicated that full recovery is still expected to take several hours, and affected resources may continue to experience impairments during this time. We’ll share further updates as more information becomes available. For questions or assistance, please contact [email protected].

17. monitoring May 09, 2026, 12:25 AM UTC

    We’re continuing to monitor the issue affecting services in the AWS us-east-1 region as AWS recovery efforts remain ongoing. AWS has reported some improvement in affected EC2 instances and EBS volumes; however, impairments persist and recovery is still expected to take several hours. We’ll share further updates as more information becomes available. For questions or assistance, please contact [email protected].

18. monitoring May 09, 2026, 02:37 AM UTC

    We’re continuing to monitor the issue affecting services in the AWS us-east-1 region as AWS recovery efforts remain ongoing. Some impairments may persist, and recovery is still expected to take several hours. We will continue to share updates as more information becomes available. For questions or assistance, please contact [email protected].

19. monitoring May 09, 2026, 04:48 AM UTC

    We’re continuing to monitor the service impact in AWS us-east-1 region, Although AWS has marked the incident as resolved, some impairments may still persist, and full recovery is expected to take several more hours. CloudOps is actively reviewing cluster status and coordinating with AWS to determine when all instances will be fully restored. We will continue to share updates as more information becomes available. For questions or assistance, please contact [email protected].

20. monitoring May 09, 2026, 07:31 AM UTC

    We’re continuing to monitor the service impact in AWS us-east-1 region, Although AWS has marked the incident as resolved, some impairments may still persist and full recovery is expected to take several more hours. Our Team is actively reviewing cluster status and coordinating with AWS to determine when all instances will be fully restored. We will continue to share updates as more information becomes available. For questions or assistance, please contact [email protected].

21. monitoring May 09, 2026, 09:40 AM UTC

    We’re continuing to track the service impact in the AWS us-east-1 region. Most nodes that could be recovered through standard replacement have already been restored, while the remaining affected clusters appear to be more complex and may require support from the R&D team. Our team is actively reviewing cluster health and coordinating with AWS to determine when all impacted instances will be fully restored. We will continue to share updates as more information becomes available. For questions or assistance, please contact [email protected].

22. monitoring May 09, 2026, 11:44 AM UTC

    We continue to monitor the service impact in the AWS us-east-1 region. Most nodes that could be recovered through standard replacement have already been restored. The remaining affected clusters appear to be more complex and may require support from the R&D team. Our team is actively reviewing cluster health and working with AWS to determine when all impacted instances can be fully restored. We will continue to share updates as more information becomes available. For questions or assistance, please contact [email protected]

23. monitoring May 09, 2026, 01:53 PM UTC

    We are continuing to monitor the service impact in the AWS us-east-1 region. Most nodes recoverable through standard replacement procedures have now been restored. The remaining affected clusters appear to involve more complex recovery scenarios and may require additional support from our R&D team. Our team is actively assessing cluster health and coordinating with AWS to define the path to full restoration for all impacted instances. We will share further updates as new information becomes available. For questions or assistance, please contact [email protected]

24. resolved May 09, 2026, 04:20 PM UTC

    We'd like to let you know that full resolution of the network issues affecting services in the US-EAST-1 region are completed. All Redis Cloud environments are operating as expected. If you have any questions or concerns, please do not hesitate to contact Redis support.

Read the full incident report →

Started May 03, 2026, 09:08 AM UTC· resolved May 26, 2026, 09:05 AM UTC

1. monitoring May 03, 2026, 09:08 AM UTC

   We’re currently performing periodic maintenance for the Redis Cloud admin console, which may impact your access to it (app.redislabs.com). Your database’s connectivity is not affected.

2. monitoring May 03, 2026, 09:26 AM UTC

   The periodic maintenance activitiy for the Redis Cloud is completed.

Read the full incident report →

Started Apr 30, 2026, 01:04 PM UTC· resolved Apr 30, 2026, 03:50 PM UTC

1. monitoring Apr 30, 2026, 01:04 PM UTC

   We are currently investigating connectivity issues to some resources that have the following pattern in their endpoint: c280

2. monitoring Apr 30, 2026, 01:43 PM UTC

   We have identified the issue and are currently working on the resolution steps. Thank you for your patience.

3. monitoring Apr 30, 2026, 02:30 PM UTC

   Our teams continue to focus on the resolution steps to fully resolve this issue. Thank you for your continued patience.

4. monitoring Apr 30, 2026, 03:27 PM UTC

   Our teams have made progress in the resolution effort and are actively applying mitigation steps to restore affected resources. We are continuing to monitor recovery and work toward full resolution.

5. monitoring Apr 30, 2026, 03:45 PM UTC

   This incident has been resolved, and affected resources are now operating normally. We will continue to monitor closely to ensure ongoing stability. If you experience or observe any further issues, please reach out to our support team for assistance.

Read the full incident report →

Started Apr 28, 2026, 07:11 AM UTC· resolved Apr 28, 2026, 01:15 PM UTC

1. monitoring Apr 28, 2026, 07:11 AM UTC

   We are currently investigating connectivity issues to some resources that have the following pattern in their endpoint: c55

2. monitoring Apr 28, 2026, 09:12 AM UTC

   The issue is identified and we are currently working on the mitigation steps.

3. monitoring Apr 28, 2026, 12:09 PM UTC

   Update- We have continued to make progress on mitigation. Our team remains engaged and is monitoring closely while work toward full resolution continues.

4. monitoring Apr 28, 2026, 01:15 PM UTC

   Update - The issue has been fully resolved. Should you encounter any remaining issues, please contact our support team via our support portal. Thank you for your patience.

Read the full incident report →

Started Apr 01, 2026, 02:32 PM UTC· resolved Apr 01, 2026, 07:20 PM UTC

1. monitoring Apr 01, 2026, 02:33 PM UTC

   We’re currently investigating issues with connecting to Redis Cloud admin console (cloud.redis.io). We will provide an update shortly. Your database’s connectivity is not affected. Until this event is fully mitigated, please submit any support requests via [email protected]. We appreciate your patience.

2. monitoring Apr 01, 2026, 04:02 PM UTC

   We are continuing to investigate issues with connecting to the Redis Cloud admin console (cloud.redis.io). -Your database’s connectivity is not affected, but you may be unable to access Redis Cloud Console. Additionally, the REST API and Terraform transactions may be affected. -Until this event is fully mitigated, please submit any support requests via [email protected].

3. monitoring Apr 01, 2026, 06:31 PM UTC

   We have identified the issues with connecting to the Redis Cloud admin console (cloud.redis.io) and are currently in the process of deploying corrective measures. We are actively working to restore full access as quickly as possible. -Your database’s connectivity is not affected, but you may be unable to access Redis Cloud Console. Additionally, the REST API and Terraform transactions may be affected. -Until this event is fully mitigated, please submit any support requests via [email protected].

4. monitoring Apr 01, 2026, 07:11 PM UTC

   The issue has been fully resolved. Should you encounter any remaining issues, please contact our support team via our Support Portal(https://support.redislabs.com/hc/en-us/requests/new). Thank you for your patience.

5. monitoring Apr 01, 2026, 07:11 PM UTC

   Incident is Resolved

Read the full incident report →

Started Mar 22, 2026, 09:49 AM UTC· resolved Mar 22, 2026, 10:01 AM UTC

1. investigating Mar 22, 2026, 09:49 AM UTC

   We’re currently performing periodic maintenance for the Redis Cloud admin console, which may impact your access to it (cloud.redis.io). Your database’s connectivity is not affected.

2. resolved Mar 22, 2026, 10:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 19, 2026, 05:38 PM UTC· resolved Mar 19, 2026, 05:52 PM UTC

1. monitoring Mar 19, 2026, 05:38 PM UTC

   We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c102.us-east-1

2. resolved Mar 19, 2026, 05:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 17, 2026, 06:28 PM UTC· resolved Mar 17, 2026, 06:59 PM UTC

1. monitoring Mar 17, 2026, 06:28 PM UTC

   Urgent maintenance applies to all of the resources with the following pattern in their endpoint: c320

2. resolved Mar 17, 2026, 06:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 13, 2026, 02:48 AM UTC· resolved Mar 13, 2026, 02:48 AM UTC

1. resolved Mar 13, 2026, 02:48 AM UTC

   Dear Customer, This is a friendly reminder that we will be transitioning our customer status page to a new platform on March 23, 2026, as part of our efforts to improve reliability and enhance the overall user experience. As previously communicated: No impact to Redis services is expected during this transition. If you are subscribed to status notifications, you will receive a one-time confirmation email during the transition. This is expected and confirms your subscription on the new platform. Action Required for RSS Subscribers: If you follow updates via RSS, please ensure your feed URL is updated to: https://status.redis.io/data/rss.xml We will post a confirmation update once the transition has been successfully completed. If you have any questions, please do not hesitate to reach out.

Read the full incident report →

Started Mar 01, 2026, 02:33 PM UTC· resolved Mar 03, 2026, 09:29 PM UTC

1. investigating Mar 01, 2026, 02:33 PM UTC

   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.

2. investigating Mar 01, 2026, 04:59 PM UTC

   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.

3. identified Mar 01, 2026, 08:47 PM UTC

   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.

4. identified Mar 02, 2026, 01:22 PM UTC

   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.

5. identified Mar 03, 2026, 03:22 AM UTC

   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 [email protected]. We will continue to provide updates as more information becomes available.

6. resolved Mar 03, 2026, 09:29 PM UTC

   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 [email protected]. Our teams will also proactively reach out to impacted customers with additional best practices and support.

Read the full incident report →