News for hackers. Stuff that matters.
Re:AWS Multiple Services Down in us-east-1 by hvb2 on Monday October 20, 2025 @02:02PM (#45647050)
It's a single region?

I don't think anyone would quote availability as availability in every region I'm in?

While this is their most important region, there's a lot of clients that are probably unaffected if they're not in use1.

They COULD be affected even if they don't have anything there because of the AWS services relying on it. I'm just saying that most customers that are multi region should have their east region out and are just humming along.

Re:AWS Multiple Services Down in us-east-1 by reactordev on Monday October 20, 2025 @02:21PM (#45647278)
It’s THE region. All of AWS operates out of it. All other regions bow before it. Even the government is there.
Re:AWS Multiple Services Down in us-east-1 by derektank on Monday October 20, 2025 @03:40PM (#45648273)
AWS GovCloud East is actually located in Ohio IIRC. Haven't had any issues with GovCloud West today; I'm pretty sure they're logically separated from the commercial cloud.
Re:AWS Multiple Services Down in us-east-1 by idontwantthis on Monday October 20, 2025 @02:33PM (#45647429)
"The Cloud" is just a computer that you don't own that's located in Reston, VA.
Re:AWS Multiple Services Down in us-east-1 by reactordev on Monday October 20, 2025 @03:29PM (#45648124)
Facts.
Re:AWS Multiple Services Down in us-east-1 by vasco on Monday October 20, 2025 @03:09PM (#45647885)
> All of AWS operates out of it.

I don't think this is true anymore. In the early days bad enough outages in us-east-1 would bring down everything because some metadata / control pane stuff was there, I remember getting affected while in other regions, but there's been many years since this has happened.

Today for example no issues. I just avoid us-east-1 and everyone else should to. It's their worst region by far in terms of reliability because they launch all the new stuff there and are always messing it up.

Re:AWS Multiple Services Down in us-east-1 by Root_Denied on Monday October 20, 2025 @03:47PM (#45648371)
A secondary problem is that a lot of the internal tools are still on US East, so likely the response work is also being impacted by the outage. Been a while since there was a true Sev1 LSE (Large Scale Event).
Re:AWS Multiple Services Down in us-east-1 by phinnaeus on Monday October 20, 2025 @04:49PM (#45649175)
What the heck? Most internal tools were in Oregon when I worked in BT pre 2021.
Re:AWS Multiple Services Down in us-east-1 by Root_Denied on Tuesday October 21, 2025 @06:10PM (#45662367)
The primary ticketing system was up and down apparently, so tcorp/SIM must still have critical components there.
Re:AWS Multiple Services Down in us-east-1 by reactordev on Monday October 20, 2025 @03:29PM (#45648131)
tell me it isn't true while telling me there isn't an outage across AWS because us-east-1 is down...
Re:AWS Multiple Services Down in us-east-1 by vasco on Monday October 20, 2025 @03:46PM (#45648343)
I help run quite a big operation in a different region and had zero issues. And this has happened many times before.
Re:AWS Multiple Services Down in us-east-1 by reactordev on Monday October 20, 2025 @04:52PM (#45649210)
If that were true, you’d be seeing the same issues we are in us-west-1 as well. Cheers.
Re:AWS Multiple Services Down in us-east-1 by hinkley on Monday October 20, 2025 @07:47PM (#45650844)
The Rot Starts at the Head.
Re:AWS Multiple Services Down in us-east-1 by hamburglar on Monday October 20, 2025 @02:43PM (#45647558)
The regions are independent, so you measure availability for each on its own.
Re:AWS Multiple Services Down in us-east-1 by logifail on Monday October 20, 2025 @03:08PM (#45647878)
Except if they aren't quite as independent as people thought
Re:AWS Multiple Services Down in us-east-1 by hamburglar on Monday October 20, 2025 @03:43PM (#45648316)
Well that’s the default pattern anyway. When I worked in cloud there were always some services that needed cross-regional dependencies for some reason or other and this was always supposed to be called out as extra risk, and usually was. But as things change in a complex system, it’s possible for long-held assumptions about independence to change and cause subtle circular dependencies that are hard to break out of. Elsewhere in this thread I saw someone mentioning being migrated to auth that had global dependencies against their will, and I groaned knowingly. Sometimes management does not accept “this is delicate and we need to think carefully” in the midst of a mandate.

I do not envy anyone working on this problem today.

Re:AWS Multiple Services Down in us-east-1 by alkhimey on Monday October 20, 2025 @04:48PM (#45649159)
Global services such as STS have regional endpoints, but is it really that common to hit specific endpoint rather than use the default?