
When AWS Broke the Internet: What Really Happened and How to Prepare
When half the internet went offline due to a single DNS misconfiguration in AWS’s US East 1 region, it exposed a critical reality: even the world’s most sophisticated cloud infrastructure can fail in unexpected ways. In this episode of SaaS That App: Building B2B Web Applications, Daniel Cannon, Chief Innovation Officer at Delta Systems, joins hosts Aaron Marchbanks and Justin Edwards to break down exactly what happened during the outage, why it cascaded across Netflix, Spotify, and countless other services, and what it means for how you should architect your own systems. This podcast is brought to you by Delta Systems, your one-stop shop for front-end, back-end, and full-stack software development. At Delta, Justin and Aaron share the same philosophy when it comes to clients: they treat people like colleagues, not just customers. Maybe that’s why Delta typically spends years working with the same companies: how many software engineering firms can you say that about? So, if you’ve got a SaaS project in mind but have no idea where to start, come and get a free scope and estimate from Delta Systems on their website. Got a burning idea for an episode, or a SaaS question you absolutely must know the answer to? Leave us a voice memo at SaasThatApp.
SaaS That App - Building Tech-Enabled Businesses · Delta Systems
Audio is streamed directly from the publisher (media.fame.so) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
- How to diagnose the root cause before rushing to fix it
- Why single-region deployments are a calculated business trade-off
- The framework for evaluating infrastructure criticality
- How to communicate transparently during outages to build trust instead of eroding it
- Why race conditions in distributed systems are insidious and require architectural thinking
- The hidden vulnerability of correlated failures in redundant systems
Highlights:
- [00:00] Introduction
- [01:13] What Happened in AWS East?
- [05:56] The Domino Effect
- [08:00] How AWS Should Respond
- [10:24] Explaining Outages to Clients
- [19:30] Transparency Builds Trust
- [27:15] Postmortems and Prevention
- [29:08] Final Takeaway
- Daniel Cannon on LinkedIn
- Strive DB Website
- Aaron Marchbanks on LinkedIn
- Justin Edwards on LinkedIn
- Delta Systems Website
https://forms.gle/DN8hWFDcE9jwvNKo6
Your input helps us shape future episodes and continue bringing you practical, real-world insights into building B2B web applications.