Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

41–50 of 1001 posts

Re: AWS multiple services outage in us-east-1

#41

Couple of years ago us-east was considered the least stable region here on HN due to its age. Is that still a thing?

When I was there at aws (left about a decade ago), us-east-1 was considered least stable, because it was the biggest.

I.e. some bottle-necks in new code appearing only _after_ you've deployed there, which is of course too late.

It didn't help that some services had their deploy trains (pipelines in amazon lingo) of ~3 weeks, with us-east-1 being the last one.

I bet the situation hasn't changed much since.

Re: AWS multiple services outage in us-east-1

#43
post #13

Signal is down from several vantage points and accounts in Europe, I'd guess because of this dependence on Amazon overseas We're having fun figuring out how to communicate amongst colleagues now! It's when it's gone when you realise your dependence

Well, at least I now know that my Belgian university's Blackboard environment is running on AWS :)

Re: AWS multiple services outage in us-east-1

#44

Can't resolve any records for dynamodb.us-east-1.amazonaws.com However, if you desperately need to access it you can force resolve it to 3.218.182.212. Seems to work for me. DNS through HN curl -v --resolve "dynamodb.us-east-1.amazonaws.com:443:3.218.182.212" https://dynamodb.us-east-1.amazonaws.com/

thank you for that info!!!!!

Re: AWS multiple services outage in us-east-1

#48
post #42

Wasn't the point why AWS is so much premium that you will always get at least 6 nines if not more in availability?

Last time I checked the standard SLA is actually 99 % and the only compensation you get for downtime is a refund. Which is why I don't use AWS for anything mission critical.
Post reply on HN