Outage in AWS
Instance Impairments
Resolved
Minor
August 25, 2020 - Started over 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:36 AM PDT We are investigating connectivity issues affecting some instances in a single Availability Zone (euw2-az2) in the EU-WEST-2 Region.
4:19 AM PDT We can confirm connectivity issues affecting some instances in a single Availability Zone (euw2-az2) in the EU-WEST-2 Region.
5:24 AM PDT We have restored connectivity to some of the instances in the affected Availability Zone (euw2-az2) in the EU-WEST-2 Region, and continue to work to restore connectivity to the remaining affected instances.
6:26 AM PDT We have restored connectivity to a further subset of the instances in the affected Availability Zone (euw2-az2) in the EU-WEST-2 Region, and continue to work to restore connectivity to the remaining affected instances.
7:55 AM PDT We wanted to provide additional information for the event affecting some RDS database 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 database instances within the affected Availability Zone. The affected Multi-AZ databases failed over to another Availability Zone as expected, and only Single-AZ databases remained affected. By 5:30 AM PDT, power and networking connectivity had been restored to the majority of affected Single-AZ database instances. We are continuing to work to recover the remaining instances.
12:29 PM PDT We have recovered the vast majority of RDS instances affected by the power event within a single Availability Zone (euw2-az2) in the EU-WEST-2 Region. Instances in other Availability Zones remain unaffected by this event.
12:45 PM PDT Starting at 2:05 AM PDT we experienced power and network connectivity issues for some database instances within the affected Availability Zone. The affected Multi-AZ databases failed over to another Availability Zone as expected, and only Single-AZ databases remained affected. By 5:30 AM PDT, power and networking connectivity had been restored to the majority of affected Single-AZ database instances. Since the beginning of the impact, we have been working to recover the remaining database instances. A small number of remaining database instances are hosted on hardware which was adversely affected by the loss of power. For these database instances, we have provided additional recovery guidance via the Personal Health Dashboard. The issue has been resolved and the service is operating normally.