Companies/Amazon Web Services/Incidents

Amazon Web Services: Increased Connectivity Issues (eu-west-3)

Affected components: AWS Private Certificate AuthorityAmazon API GatewayAWS AppConfigAmazon WorkSpaces ApplicationsAWS AppSyncAmazon AthenaAWS IoT Device ManagementAWS IoT CoreBedrock AgentCoreAWS Certificate ManagerAWS Client VPNAWS Cloud9AWS CloudFormationAmazon CloudFrontAWS CloudShellAWS Cloud WANAWS CodeArtifactAWS CodeCommitAWS CodeDeployAWS Database Migration ServiceAmazon DocumentDBAmazon Elastic Container ServiceAmazon Elastic Kubernetes ServiceAWS Elastic BeanstalkAmazon Elastic File SystemAmazon Elastic Load BalancingAmazon Elastic MapReduceAmazon EventBridgeAWS FargateAmazon FSxAWS IoT Device DefenderAmazon Interactive Video ServiceAmazon Kinesis Data StreamsAWS Key Management ServiceAWS LambdaAmazon MQAWS NAT GatewayNetwork Access AnalyzerAWS Network FirewallAWS Payment CryptographyAWS Parallel Computing ServiceAWS VPCE PrivateLinkAmazon RedshiftAmazon Simple Storage ServiceAmazon EventBridge SchedulerAmazon Simple Notification ServiceAmazon Simple Queue ServiceAWS Step FunctionsAmazon Simple Workflow ServiceTraffic MirroringAWS Transfer FamilyAWS Transit GatewayAWS Site-to-Site VPNAmazon WorkSpaces

Timeline of updates

1. update2026-04-27 11:27 UTC

   We are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region.

2. resolved2026-04-27 12:05 UTC

   Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region. During this time, customers attempting to launch new EC2 instances in the affected Availability Zone would have experienced launch failures. Additionally, a subset of existing EC2 instances and EBS volumes in this Availability Zone were impacted and became unreachable. We have identified the root cause to be a loss of power to infrastructure within the affected Availability Zone. Engineers were engaged at 4:02 AM and immediately began working to restore power and assess the scope of impact. By 4:20 AM, power was successfully restored to the affected infrastructure. We then focused our efforts on recovering impacted EC2 instances and EBS volumes. By 4:40 AM, all impacted EC2 instances and EBS volumes had been fully recovered and were operating normally. No additional action is required for EC2 instances and EBS volumes that were impacted during the power loss event, as these have been fully recovered. While EC2 and EBS have recovered, some AWS services may take additional time to fully recover as they process backlogs and complete their own recovery procedures. The issue has been resolved and the service is operating normally.

Impact, status and times are the vendor’s own, as last archived. View on health.aws.amazon.com (opens in new tab).

Amazon Web Services profileRecent Amazon Web Services incidentsMarkdownJSON