AWS truly does stand for "All Web Sites".
AWS multiple services outage in us-east-1
161–170 of 1001 posts
Re: AWS multiple services outage in us-east-1
#162BGP (again)?
Re: AWS multiple services outage in us-east-1
#163Statuspage.io seems to load (but is slow) but what is the point if you can't post an incident because Atlassian ID service is down.
Re: AWS multiple services outage in us-east-1
#164Signal is also down for me.
Re: AWS multiple services outage in us-east-1
#165is this why docker is down?
Re: AWS multiple services outage in us-east-1
#16610:30 on a Monday morning and already slacking off. Life is good. Time to touch grass, everybody!
Re: AWS multiple services outage in us-east-1
#167AWS has been the backbone of the internet. It is single point of failure most websites.
Other hosting services like Vercel, package managers like npm, even the docker registeries are down because of it.
Re: AWS multiple services outage in us-east-1
#168Thanks god we built all our infra on top of EKS, so everything works smoothly =)
Re: AWS multiple services outage in us-east-1
#169I 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.
I think a lot of its probably technical debt. So much internally still relies on legacy systems in US-East-1, and every time this happens I'm sure theres a discussion internally about decoupling that reliance which then turns into a massive diagram that looks like a family tree dating back a thousand years of all the things that need to be changed to stop it happening.
Sounds plausible. It's also a "fat and happy" symptom not to be able to fix deep underlying issues despite an ever growing pile of cash in the company.
Re: AWS multiple services outage in us-east-1
#170Internet, out. Very big day for an engineering team indeed. Can't vibe code your way out of this issue...
Easiest day for engineers on-call everywhere except AWS staff. There’s nothing you can do except wait for AWS to come back online.
Pour one out for the customer service teams of affected businesses instead