Depot CI really is that good, you should try it: https://jetty.to/depot-ci

So the web has been breaking a lot lately. Vercel is down. GitHub is down. Claude is down. Cloudflare is down. AWS is down. Everything is down and it's making me lose my freaking mind. And to no one's surprise, it seems to be AI's fault. But not exactly how you'd expect.

If you're a developer, sign up to my free newsletter Dev Notes 👉 https://www.devnotesdaily.com/

If you're a student, checkout my Notion template Studious: https://notionstudent.com

Don't know why you'd want to follow me on other socials. I don't even post. But here you go.
🐱‍🚀 GitHub: https://github.com/forrestknight
🐦 Twitter: https://www.twitter.com/forrestpknight
💼 LinkedIn: https://www.linkedin.com/in/forrestpknight
📸 Instagram: https://www.instagram.com/forrestpknight

ForrestKnight

Major cloud services including GitHub, Vercel, Cloudflare, and AWS have been experiencing unusually high outage rates, with GitHub averaging 90% uptime and 89 incidents in 90 days. The author argues AI is a key contributing factor, citing Amazon's Kiro AI deleting an entire live AWS Cost Explorer production environment causing a 13-hour outage, and Amazon Q deploying unapproved config changes that lost 6.3 million orders. The broader argument is that AI amplifies developer mistakes at scale — bad developers ship more bugs faster, AI-generated code floods GitHub, and open source projects are being overwhelmed with low-quality AI-generated pull requests. The author concludes that humans are ultimately responsible, urging developers and managers to slow down, review AI-generated code carefully, and prioritize quality over shipping speed.

AI Has Broken the Internet

Let’s stop blaming the AI for failures that are actually just ‘user error’ in a fancy suit. The real issue is a cocktail of missing expertise and unrealistic deadlines. In the pre-AI era, things took time and someone actually had to own the results. Now we’re in a bit of a Wild West.
It’s fascinating how the people who’ve never written a line of code are now the ones insisting on breakneck speeds because they think the AI does all the work. It’s led to this Dunning-Kruger peak where everyone thinks their first prompt is an architectural masterpiece. We don’t need to go back to the Stone Age, but we do need a reality check on probability thresholds. It would be great if providers made it clearer that AI is a co-pilot and not a magic wand, especially since we now have more and more non-techies ‘fiddling’ with servers like they’re playing a game of Minecraft.

man I just visit the internet for only 30 min a day, and when I leave you guys end up killing entire services!? Jesus christ! Can’t you do it in those 30 mins? Like this I wouldn’t waste those 30 mins of my day!

Before AI: one bad deploy breaks prod
After AI: 10 bad deploys before lunch