Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

81–90 of 1001 posts

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

#84
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

Thankfully Slack is still holding up.

It’s acting up for me but wondering if it’s unrelated. Imagines failing to post and threads acting strange.

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

#86

I find it interesting that AWS services appear to be so tightly integrated that when there's an issue in a region, it affects most or all services. Kind of defeats the purported resiliency of cloud services.

You know how people say X startup is ChatGPT wrapper? A significant chunk of AWS services are wrappers of main services (DynamoDB, EC2, S3 and etc).

Yes, and that's exactly the problem. It's like choosing a microservice architecture for resiliency and building all the services on top of the same database or message queue without underlying redundancy.

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

#88
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.

I don't recommend to my clients they use us-east-1. It's the oldest and most prone to outages. I usually always recommend us-east-2 (Ohio) unless they require West Coast.

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

#89
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.

us-east-1 was, probably still is, AWS' most massive deployment. Huge percentage of traffic goes through that region. Also, lots of services backhaul to that region, especially S3 and CloudFront. So even if your compute is in a different region (at Tower.dev we use eu-central-1 mostly), outages in us-east-1 can have some halo effect.

This outage seems really to be DynamoDB related, so the blast radius in services affected is going to be big. Seems they're still triaging.

Post reply on HN