You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Cascading failure: why a 3-hour DNS problem became a 14-hour cloud outage

Why one cloud outage takes down half the Internet

Hidden dependencies: why a cloud outage in one region reaches the others

A failure in one AWS region should stay in that region. On 20 October 2025, apps on the other side of the world failed too. Why distance alone does not protect an app.

  1. 1 Your ticket app lives in Virginia, so it went down with its region. Now take an app that lives far away, in the Ireland region. Its servers, its database, its zones: all fine that morning. It had no reason to notice a thing.Irelandus-east-1an appthousands of kilometres apart

    Your ticket app lives in Virginia, so it went down with its region. Now take an app that lives far away, in the Ireland region. Its servers, its database, its zones: all fine that morning. It had no reason to notice a thing.

  2. 2 Yet some apps far from Virginia failed too, in regions all over the world.Irelandus-east-1an app?

    Yet some apps far from Virginia failed too, in regions all over the world.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Multi-region failover: how an app keeps working when its cloud region goes dark

Share this comic

More comics