Network Issues in AWS US-EAST-1

Update timeline

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.