On October 20th (I’m in Australia, so yeah… dodgy accent and all), AWS had a massive outage and it was one of those moments where you watch the internet kind of “half work” and then fall over again. In this video I talk through what was happening, why it matters, and the real-world problem it creates for businesses that run a ton of workloads in one cloud region. When DNS and core services start failing, it’s not just one app that breaks—everything that depends on those building blocks starts to wobble. I’m coming at this as an IT leader/CIO who’s got tech spread across AWS, Azure, some Google, other SaaS platforms, and on-prem as well. The big takeaway is simple: you can’t prevent a major provider outage if you’ve put all your eggs in one bucket, and executives are absolutely going to ask, “How could we have stopped this?” That’s the conundrum—cloud gives you scale, but you give up control. This is exactly why I don’t put everything in the cloud; a hybrid or multi-cloud approach (plus on-prem where it makes sense) can reduce blast radius when a provider has a bad day.