Skip to content

Cloud · Amazon Web Services

AWS us-west-2 loses internet connectivity over the route to the Seattle metro

Started
Jul 24, 2026, 10:55 UTC
Resolved
Jul 24, 2026, 12:12 UTC
Duration
1h 17m (from provider timestamps)
Affected
Amazon API Gateway, AWS IoT Core, AWS Direct Connect, Amazon EC2, Amazon ECS, Elastic Load Balancing, AWS Global Accelerator, AWS Internet Connectivity, Amazon VPC, AWS Site-to-Site VPN, AWS Management Console (some customers)
Cause
Preliminary causeAWS said an issue with networking devices that route traffic from the us-west-2 Region to the Seattle metro cut connectivity into the Region for about 20 minutes, while connectivity inside the Region was unaffected. A brief route reconvergence caused more intermittent loss later, and Direct Connect customers on one Seattle location saw a longer window. AWS has not said what went wrong with the devices.
Was it an attack?
Not stated
State
resolved

Anatomy

  1. 1. Trigger

    Not stated

  2. 2. Already broken

    None stated

  3. 3. What made it spread

    None stated

  4. 4. Blast radius

    single region: us-west-2

  5. 5. Cause category

    Network

Labels follow the root-cause taxonomy. A person's change is recorded as the trigger and the missing safeguard as what was already broken; “human error” is never a cause here.

How the explanation changed

  1. July 24, 2026 · Preliminary cause

    “We have identified the root cause as an issue with a networking device responsible for network routing from the Region to the Seattle Metro.”

    AWS Health Dashboard event history feed (us-west-2 '[RESOLVED] Connectivity Issues', AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_83A36_24C89B493A6)

  2. July 24, 2026 · Preliminary cause

    “We identified the root cause as an issue with networking devices responsible for network routing from the Region to the Seattle Metro, and began working in parallel on multiple paths to mitigate the impact.”

    AWS Health Dashboard event history feed (us-west-2 '[RESOLVED] Connectivity Issues', AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_83A36_24C89B493A6)

Sources

  1. AWS Health Dashboard event history feed (us-west-2 '[RESOLVED] Connectivity Issues', AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_83A36_24C89B493A6) (provider, read November 17, 2026)

Last verified November 17, 2026. Spot an error? The methodology page says how corrections work.