81–90 of 214 posts
It's always East 1... Jokes aside I don't understand how often east-1 is taken down compared to other regions. Like it should be pretty similar to other regions architecture wise.
> AWS in 2025: The Stuff You Think You Know That’s Now Wrong
> us-east-1 is no longer a merrily burning dumpster fire of sadness and regret.
— https://www.lastweekinaws.com/blog/aws-in-2025-the-stuff-you...
Otherwise a good article!
Earlier quoted context omitted.
So Ashburn VA is a datacenter hub because the very first non-government Internet Exchange Point (IXP) anywhere in the world was there ( https://en.wikipedia.org/wiki/MAE-East ). Back in the 1990's something like half of all internet traffic all over the world hit MAE-East. That in turn made AWS put their first region there (us-east-1 preceded eu-west-1 by 2 years and us-west-1 by 3 years). Then because there were lot…
Well said. I'll also add, that with these networks, the sooner you can get traffic off your network the better. There's strong incentive to have your datacenter near these peering points. And since MAE-East was the first, it's been the largest as it's been snowballing the oldest. AOL's HQ was here, Equinix built their peering point soon after MAE-East, etc. There's a great read about the whole area here: https://www.…
Why is that? You would think the company ending events like IAM going poof due to it being dependent on us-east-1 would be top priority to fix?
It's always East 1... Jokes aside I don't understand how often east-1 is taken down compared to other regions. Like it should be pretty similar to other regions architecture wise.
AWS’s US-East 1 continues to be the Achilles heel of the Internet. And while yes building across multiple regions and AZs is a thing, AWS has had a string of issues where US-East 1 has broader impacts, which makes things far less redundant and resilient than AWS implies.
Too many people are using it. In fantasy magic dream land loads are distributed evenly across different cloud providers. A single point of failure doesn't exist. It worked out with my first girlfriend. The twins are fluent in English and Korean. They know when deploying a large scale service to not only depends on AWS. Healthcare in the US is affordable. All types of magical stuff exist here. But no. It's another day…
I bet post-mortem will say vibe coding confused fahrenheit and celsius, we run too hot...
Earlier quoted context omitted.
Too many people are using it. In fantasy magic dream land loads are distributed evenly across different cloud providers. A single point of failure doesn't exist. It worked out with my first girlfriend. The twins are fluent in English and Korean. They know when deploying a large scale service to not only depends on AWS. Healthcare in the US is affordable. All types of magical stuff exist here. But no. It's another day…
Core AWS services use it too. Even if you are hosted in another region, you can still be affected by a US-East 1 outage
Earlier quoted context omitted.
Too many people are using it. In fantasy magic dream land loads are distributed evenly across different cloud providers. A single point of failure doesn't exist. It worked out with my first girlfriend. The twins are fluent in English and Korean. They know when deploying a large scale service to not only depends on AWS. Healthcare in the US is affordable. All types of magical stuff exist here. But no. It's another day…
Core AWS services use it too. Even if you are hosted in another region, you can still be affected by a US-East 1 outage
But even then , the load balancer needs to run somewhere. Which becomes a new single point of failure.
I’m sure someone smarter than me has figured this out.
Earlier quoted context omitted.
Of course not. They fail above 100%. Some fail below 100% too.
You can't have a duty cycle above 100%. It's impossible.