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

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-04-27 11:27 UTC · Resolved: 2026-04-27 12:05 UTC · Duration: 39 min
- Updates: 2 · Affected components: AWS Private Certificate Authority, Amazon API Gateway, AWS AppConfig, Amazon WorkSpaces Applications, AWS AppSync, Amazon Athena, AWS IoT Device Management, AWS IoT Core, Bedrock AgentCore, AWS Certificate Manager, AWS Client VPN, AWS Cloud9, AWS CloudFormation, Amazon CloudFront, AWS CloudShell, AWS Cloud WAN, AWS CodeArtifact, AWS CodeCommit, AWS CodeDeploy, AWS Database Migration Service, Amazon DocumentDB, Amazon Elastic Container Service, Amazon Elastic Kubernetes Service, AWS Elastic Beanstalk, Amazon Elastic File System, Amazon Elastic Load Balancing, Amazon Elastic MapReduce, Amazon EventBridge, AWS Fargate, Amazon FSx, AWS IoT Device Defender, Amazon Interactive Video Service, Amazon Kinesis Data Streams, AWS Key Management Service, AWS Lambda, Amazon MQ, AWS NAT Gateway, Network Access Analyzer, AWS Network Firewall, AWS Payment Cryptography, AWS Parallel Computing Service, AWS VPCE PrivateLink, Amazon Redshift, Amazon Simple Storage Service, Amazon EventBridge Scheduler, Amazon Simple Notification Service, Amazon Simple Queue Service, AWS Step Functions, Amazon Simple Workflow Service, Traffic Mirroring, AWS Transfer Family, AWS Transit Gateway, AWS Site-to-Site VPN, Amazon WorkSpaces
- [Vendor status page: https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status)
- [Company: Amazon Web Services](https://rewindex.com/company/aws.md)

## Timeline of updates

- **update** 2026-04-27 11:27 UTC: We are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region.
- **resolved** 2026-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.


---
Canonical: https://rewindex.com/company/aws/incidents/eu-west-3-aws_ec2_operational_issue_fb70e_b77b1d343fd · Markdown: https://rewindex.com/company/aws/incidents/eu-west-3-aws_ec2_operational_issue_fb70e_b77b1d343fd.md · JSON: https://rewindex.com/api/v1/companies/aws/incidents/eu-west-3-aws_ec2_operational_issue_fb70e_b77b1d343fd · Generated 2026-10-20T00:51:11.242Z