October 24, 2025 09:09:35

And I want to talk about it because the read is a little bit complicated. And I want to simplify it. What caused it was a simple automator. Not an AI automator, just an automator. They had some routines in place to rotate and clean up their DNS records. And their architecture is set up where each region has a single endpoint for DynamoDB. And most of their services rely on that single endpoint for DynamoDB. And automation was coming in. And it was doing its job, but then it got stuck and sort of slowed down. And it didn't complete its job. And another automation came in and started doing its job, which is to clean up the old records. Now that the new records have been written. And since there was a delay, it deleted all the records. These were DNS records, these were IP addresses. And that simple delay took the Internet down to 14 hours. The reason I want to talk about this is not to just help you understand what happened. It's because of what just happened in 2009. Every opportunist out there, and then some that were not opportunists, but had noble intentions, leapt on this huge wave of selling automations to small businesses or big businesses. And most of those people selling these automations were not that good. They don't understand technology. They didn't understand it. And I've been saying for a long time that a lot of this happening is going to cause problems. AWS didn't say this. But the day after the event, or perhaps the day after that, they banned all VibeCoded code from being used in the AWS services. They didn't come out and say it, but they may as well have. This was a VibeCoded mistake. At least, this is my educated guess. That somebody in their team VibeCoded these automations, these DNS jobs. And it messed up. Even if this wasn't caused by VibeCode, it was caused by an automation, meaning nobody was watching. They trusted machines to do the jobs correctly. But machines, at least not yet, they're not capable of doing it correctly all the time. Throughout my career and across many jobs, I learned long ago that automated updates and automated backups are not acceptable. You can automate them, but if you don't watch them complete and come back online the way that they're supposed to, you are risking problems. So even though in my current job and in previous jobs, I automate many tasks, I sit there until they're done. And I make sure that they complete the way they're supposed to and I read the reports. And not just me, other people on my team do that as well. Because I have been in systems for 24 years, meaning I control the system, the underlying foundation of all the computers and all the networks that other people use to get their job done. So nearly a quarter century of experience has taught me to take responsibility, whereas everybody else sort of looks down when you're doing it this way. And they make fun of me for doing it this way sometimes, not always, but they do have a negative opinion. And since I've spent many months warning people about VibeCode, about automation, when you don't understand technology, people laugh at me like, well, you don't need to understand it now. The AI can do it for you. No, they can't. Not yet. And I don't see it happening anytime soon. So I just wanted to explain that and sort of help open people's eyes up. I know many won't care, but I'm going to do it anyway. If you want to see a simplified version of the report that AWS released, go to my X. I had Claude summarize it in very plain language, and I posted it there. So if you want to see it, there's the summarized version on my X, and then there's a link below that to the original article. Have a great day.