AWS EC2 West Down

> 7:23 AM PDT We are investigating networking connectivity issues for some instances in the US-WEST-2 Region.

They should really change the color of the checkmark if they're having issues.

I've always advised other startups using AWS to begin on us-west-2 as it has a couple key pros:

1. Lower latency to SF/Bay Area

2. Cheaper then US-West-1 (California).

3. Updated and cared for. West-2 is sometimes behind East-1 on some features - things like govcloud, some instance types etc rolled out on East-1 first - However, unlike US-West-1, it eventually gets updated. [0]

4. Until now, it hasn't had a single incident. I knew this would never last, but given that it's smaller and simpler (less legacy hardware), I still think that Oregon will have better uptime then VA.

This advice doesn't changes at all, even with this most recent blip. I'm just sad that I can't say "US-West-2. Closer and never had an incident"

[0] Given how US-West-1 (CA) often falls behind on features, it will not surprise me if AWS announces that they're going to deprecate that region.

Seems to have affected NPM: http://status.npmjs.org/

Amazon Elastic Compute Cloud (Oregon): 7:23 AM PDT We are investigating networking connectivity issues for some instances in the US-WEST-2 Region.

West what? US? Europe? Asia? And not according to that page you linked. Green across the board.