Twelfth Post!

[hoisinsauce]

POST NAMER TBC-- work harder, meme!

Welcome back, anyway! Chat fandom, media, creative things, weirdness from around the net, funny stuff, anything! Meme awaits!

(start a comment thread by replying to this post)

 

Comments

Re: Coding - AWS Outage

[(Anonymous)]

Apparently it was a dns problem. Lol, I could've told them that. It's always fucking dns.

I've been wondering if the root cause is that they laid off a fuckton of cloud engineers to "replace" them with AI. I don't think there's been any comment either way about that, and I doubt amazon would leap to confirm if that is, indeed, the problem. But an 8 hour outage for a dns error suggests they don't have the best and brightest working on it.

Going to look for more details...

Re: Coding - AWS Outage

[(Anonymous)]

https://forums.theregister.com/forum/all/2025/10/20/amazon_aws_outage/

Re: Coding - AWS Outage

[(Anonymous)]

In which (at time of writing) 65 ppl have upvoted "it's always dns" lol.

Actual article:
https://www.theregister.com/2025/10/20/amazon_aws_outage/

Not much detail. I'm assuming it ended up misconfigured because amazon did something stupid.

Re: Coding - AWS Outage

[(Anonymous)]

El reg shares my suspicions:

https://www.theregister.com/2025/10/20/aws_outage_amazon_brain_drain_corey_quinn/

Re: Coding - AWS Outage

[(Anonymous)]

Amazon will never admit it, and water carriers for them will never admit it, but anyone with a lick of sense knows that laying off the people who can fix shit (and they and MSFT have been doing just that) is going to fuck you.

You'd think MSFT would have learned from laying off a bunch of SDETs when Windows 10 was in development and then shitting the bed, but that would be using your normal people brain and not your shareholder brain, I guess.

(Also, yep: it's always fucking DNS.)