Instance Connectivity

4:24 AM PST We are experiencing instance connectivity issues in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region.

5:34 AM PST We're continuing to address connectivity issues to impacted instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. Services that use EC2 and EBS including Elastic Load Balancing, EFS, Elasticache, ECS Fargate, Sagemaker and ELB, are also impacted.

6:08 AM PST We're continuing to address connectivity issues to impacted instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. We are experiencing elevated error rates for new instance launches in the impacted Availability Zone. Services that use EC2 and EBS including Connect, EFS, Elasticache, ECS Fargate, Managed Streaming for Apache Kafka and Sagemaker are also impacted.

6:50 AM PST We're continuing to address connectivity issues to impacted instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. We are starting to see recovery for new instance launches in the impacted Availability Zone. Services that use EC2 and EBS including EFS, Elasticache, ECS Fargate, Managed Streaming for Kafka, EMR and Sagemaker are also impacted. Between 3:02 AM and 5:20 AM PST, Amazon Connect customers experienced degraded call and Chat connectivity and handling for agents in the EU-WEST-2 Region. Amazon Connect issues have been resolved and the service is operating normally.

7:41 AM PST We're continuing to address connectivity issues to impacted instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. The elevated error rates that impacted some new instance launches in the affected Availability Zone have fully recovered.

8:29 AM PST We have resolved the connectivity issues for the vast majority of affected instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. We are also seeing recovery for the vast majority of EBS volumes experiencing degraded performance due to this event. Services that use EC2 and EBS including RDS, EFS, Elasticache, ECS Fargate, Managed Streaming for Apache Kafka, EMR and Sagemaker are also seeing recovery. We continue to work towards full recovery for the remaining instances and volumes.

8:53 AM PST Starting at 2:57 AM PST we experienced power and network connectivity issues for some instances, and degraded performance for some EBS volumes in the affected Availability Zone (euw2-az3). By 3:59 AM PST, power and networking connectivity had been restored to the majority of affected instances and, by 7:32 AM PST, 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 event. 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.