HN Explorer

Is the AWS us-west-2 region experiencing an outage?

14 points by teachrdan ↗ HN
Our startup's EC2 instance in the us-west-2 (Oregon) region is down. This despite the AWS dashboard saying there are no problems. Is anyone else experiencing an outage with an AWS resource in that region?

9 comments

[ 4.8 ms ] story [ 25.4 ms ] thread
frausto
Anecdotal, but everything running fine and looking normal on our us-west-2 instances
linsomniac
Same. None of our alerts are going off, our EC2 instances seem happy. No user reports of problems which we would likely be getting if there were S3 issues for 40 minutes.
belter
What Availability Zone? What AWS Service?

For what it's worth, just successfully launched an EC2 instance and created a Bucket...

tytho
We're seeing some issues possibly related to s3. Uploads working, but downloads seem to fail occasionally.
waz0wski
not sure why this kind of 'sky is falling' post is allowed, particularly when there's no useful information provided

- status boards are rarely up to date, make sure you have your own internal/external monitoring

- a single vm instance does not indicate the health of an entire region. instances can be stopped for a variety of reasons, check the maintenance log and vm console

- when using cloud resources, architecture should not be dependent on a single vm instance

- your cloud architecture and app code should be built to handle transient failures from the start - queueing, retries, backoffs, load-shedding, graceful state failure, etc. use cloud-native services when possible, lift-and-shift of traditional vm architecture to the cloud can be operationally difficult and expensive to run

discodave
Joke answer: Because dumping on AWS is fun!

Serious answer: People will confirm or not in the comments, this post seems pretty reasonable, if a little trigger happy. It could just be a random launch failure.

banana_giraffe
One EC2 instance going down hardly suggests a region-wide problem.

I've certainly not seen any issue with us-west-2 in the last 24 hours.

brycewray
Did notice some oddities during that period accessing the Twitter oEmbed API.