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

Project Visually
Random Sign in Subscribe
Previous episode Race condition: why three copies of one program did not prevent the AWS outage

Why one cloud outage takes down half the Internet

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

The DNS problem behind the AWS outage of October 2025 was fixed in under three hours. The outage lasted more than fourteen. Where did the rest of the day go?

  1. 1 By 2:25 AM, the name of DynamoDB works again. Then the morning rush begins at the dock, and your ticket app needs more servers, as on every busy morning. It asks AWS to start three more. AWS answers: no room.your appThree moreservers, please!AWSNo room.

    By 2:25 AM, the name of DynamoDB works again. Then the morning rush begins at the dock, and your ticket app needs more servers, as on every busy morning. It asks AWS to start three more. AWS answers: no room.

  2. 2 Strange answer. The data centres of us-east-1 are full of free machines, and DynamoDB has answered again since 2:25 AM.free machines, waitingDynamoDB

    Strange answer. The data centres of us-east-1 are full of free machines, and DynamoDB has answered again since 2:25 AM.

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 Hidden dependencies: why a cloud outage in one region reaches the others

Share this comic

More comics