Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

241–250 of 1001 posts

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

#242
post #219

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/

It's always DNS

Confirmed.

> Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1.

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

#245

Just a couple of days ago in this HN thread [0] there were quite some users claiming Hetzner is not an options as their uptime isn't as good as AWS, hence the higher AWS pricing is worth the investment. Oh, the irony. [0]: https://news.ycombinator.com/item?id=45614922

Finally IT managers will start understanding that cloud is no difference than Hetzner.

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

#246
post #148
post #102

To everyone that got paged (like me), grab a coffee and ride it out, the week can only get better!

To everyone who was supposed to get paged but didn't, do a postmortem, chances are your service is running via Twilio and needs migrating elsewhere.

Hah good point, pagerduty is working at least.

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

#247

Just a couple of days ago in this HN thread [0] there were quite some users claiming Hetzner is not an options as their uptime isn't as good as AWS, hence the higher AWS pricing is worth the investment. Oh, the irony. [0]: https://news.ycombinator.com/item?id=45614922

When AWS is down, everybody knows it. People don’t really question your hosting choice. It’s the IBM of cloud era.

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

#250
post #212

We just had a power outage in Ashburn starting at 10 pm Sunday night. It restored at 3:40am ish, and I know datacenters have redundant power sources but the timing is very suspicious. The AWS outage supposedly started at midnight

Their latest update on the status page says it's a Dynamodb DNS issue
Post reply on HN