Summary
We continue to see significant signs of recovery as a result of our mitigation efforts for the connectivity issues impacting multiple AWS services in the US-WEST-2 Region. We have identified the root cause as an issue with a networking device responsible for network routing from the Region to the Seattle Metro. Engineers have finished all mitigation work. As routes continue to be restored, customers should see a continued reduction in error rates and timeouts when connecting to affected services
Impact
We continue to see significant signs of recovery as a result of our mitigation efforts for the connectivity issues impacting multiple AWS services in the US-WEST-2 Region. We have identified the root cause as an issue with a networking device responsible for network routing from the Region to the Seattle Metro. Engineers have finished all mitigation work. As routes continue to be restored, customers should see a continued reduction in error rates and timeouts when connecting to affected services
Lessons Learned
⚠AWS has experienced 70 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to network, routing have occurred 210 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: Network / Routing. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Incident With Blocked GitHub.com Traffic
GitHub · Jul 24, 2026
Service is operating normally: [RESOLVED] Connectivity Issues
AWS · Jul 24, 2026
Service impact: Connectivity Issues
AWS · Jul 24, 2026
Service impact: Connectivity Issues
AWS · Jul 24, 2026
Service impact: Connectivity Issues
AWS · Jul 24, 2026