Outage in AWS
Instance Connectivity
Resolved
Minor
August 25, 2020 - Started about 4 years ago
- Lasted over 1 year
Need to monitor AWS outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including AWS, and never miss an outage again.
Start Free Trial →
Outage Details
3:21 AM PDT We are investigating instance connectivity issues in a single Availability Zone (euw2-az2) in the EU-WEST-2 Region.
3:52 AM PDT We are experiencing instance connectivity issues in a single Availability Zone (euw2-az2) in the EU-WEST-2 Region. As a result we are experiencing elevated API latencies for multiple APIs, as well as elevated API failure rates on the CreateSnapshot API only. We are also experiencing elevated instance launch failure rates in the affected Availability Zone.
4:46 AM PDT We have restored connectivity to some of the instances in the affected Availability Zone (euw2-az2), and API latencies and launch failure rates are largely recovered. Access to some EBS volumes in the affected Availability Zone was also affected. We are working to restore connectivity to the remaining affected instances and volumes.
5:50 AM PDT We have restored connectivity to a further subset of the instances and volumes in the affected Availability Zone (euw2-az2). We are continuing to work to restore connectivity to the remaining affected instances and volumes.
7:01 AM PDT We wanted to provide some more information for the event affecting some instances in a single Availability Zone (euw2-az2) in the EU-WEST-2 Region. Starting at 2:05 AM PDT we experienced power and network connectivity issues for some instances, and degraded performance for some EBS volumes in the affected Availability Zone. As a result of this we also experienced elevated API latencies for some of our APIs, elevated API failure rates on the CreateSnapshot API, and elevated instance launch failure rates in the affected Availability Zone. By 4:50 AM PDT, power and networking connectivity had been restored to the majority of affected instances, and degraded performance for the majority of affected EBS volumes had been resolved. While we will continue to work to recover the remaining instances and volumes, for immediate recovery, we recommend replacing any remaining affected instances or volumes if possible.
12:13 PM PDT Starting at 2:05 AM PDT we experienced power and network connectivity issues for some instances, and degraded performance for some EBS volumes in the affected Availability Zone (euw2-az2) . By 4:50 AM PDT, power and networking connectivity had been restored to the majority of affected instances, and degraded performance for the majority of affected EBS volumes had been resolved. Since the beginning of the impact, we have been working to recover the remaining instances and volumes. A small number of remaining instances and volumes are hosted on hardware which was adversely affected by the loss of power. We continue to work to recover all affected instances and volumes and have opened notifications for the remaining impacted customers via the Personal Health Dashboard. For immediate recovery, we recommend replacing any remaining affected instances or volumes if possible.