Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

201–210 of 1001 posts

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

#204

It's fun watching their list of "Affected Services" grow literally in front of your eyes as they figure out how many things have this dependency. It's still missing the one that earned me a phone call from a client.

It's seemingly everything. SES was the first one that I noticed, but from what I can tell, all services are impacted.

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

#208
post #78

Is there any data on which AWS regions are most reliable? I feel like every time I hear about an AWS outage it's in us-east-1.

We're mostly deployed on eu-west-1 but still seeing weird STS and IAM failures, likely due to internal AWS dependencies.

Also we use Docker Hub, NPM and a bunch of other services that are hosted by their vendors on us-east-1 so even non AWS customers often can't avoid the blast radius of us-east-1 (though the NPM issue mostly affects devs updating/adding dependencies, our CI builds use our internal mirror)

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

#210

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.

AWS engineers are trained to use their internal services for each new system. They seem to like using DynamoDB. Dependencies like this should be made transparent.
Post reply on HN