271–280 of 1001 posts
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
There's no way it's DNS
It was DNS
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
Coinbase down as well: https://status.coinbase.com/
Probably makes sense to add "relies on AWS" to the criteria we're using to evaluate 3rd-party services.
Their status page ( https://health.aws.amazon.com/health/status ) says the only disrupted service is DynamoDB, but it's impacting 37 other services. It is amazing to see how big a blast radius a single service can have.
“Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1. We are working on multiple parallel paths to accelerate recovery.” It’s always DNS.
DynamoDB is performing fine in production in eu-central-1. Seems to be really limited to us-east-1 ( https://health.aws.amazon.com/health/status ). I think they host a lot of console and backend stuff there.