AWS multiple services outage in us-east-1
241–250 of 1001 posts
Re: AWS multiple services outage in us-east-1
#242Can'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
> 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
#243Signal is also down for me.
Re: AWS multiple services outage in us-east-1
#244Re: AWS multiple services outage in us-east-1
#245Just 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
Re: AWS multiple services outage in us-east-1
#246To 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.
Re: AWS multiple services outage in us-east-1
#247Just 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
Re: AWS multiple services outage in us-east-1
#248Re: AWS multiple services outage in us-east-1
#249Re: AWS multiple services outage in us-east-1
#250We 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