Public postmortems, explained fast

Why it broke.
What actually happened.

CodeWicked takes the public root cause analysis behind the world’s biggest tech incidents — the outages, bugs, and bad updates that took everything down — and explains it in about 60 seconds. No hype. No guessing. Just what the companies themselves published, and a clear take on it.

The format

Same four steps. Every incident.

One incident per episode, traced the way engineers actually traced it — so you always know where the story is going, and what’s fact versus opinion.

01

Symptom

What the world saw first: the error, the outage, the grounded flights, the blank screens.

02

Investigation

How engineers narrowed it down — the clues, the dead ends, and the moment it clicked.

03

Root Cause

The actual failure, in plain language. The one line of code, file, or config that started it all.

04

The Take

What it really means, what should have caught it, and the lesson worth remembering.

Episodes

Coming first

These are in production now. They’re not published yet — when they go live, the links will appear here and on YouTube and TikTok.

CrowdStrike, July 2024 — the update that grounded the world

A single faulty update crashed millions of Windows machines worldwide — grounding flights, stopping hospitals, and taking banks offline.

Coming soon

AWS US-EAST-1, October 2025 — the DynamoDB DNS race

A race condition in DNS automation took down Amazon’s busiest cloud region — and a huge slice of the internet with it.

Coming soon

Cloudflare, November 2025 — the file that doubled

A configuration file quietly grew past its limit, and one of the internet’s core networks went down for hours.

Coming soon

Watch

Watch & subscribe

CodeWicked will publish on YouTube and TikTok. The channels aren’t live yet — this page is where the real links will land first.

YouTube

Full episodes and Shorts: one incident, one root cause, about a minute at a time.

YouTube Coming soon

TikTok

The 60-second version: the symptom, the investigation, and the root cause, fast.

TikTok Coming soon

About

Faceless on purpose.
Sourced on principle.

CodeWicked is a faceless channel. No face, no personal brand — because the story isn’t a person, it’s what broke and why.

Every episode is built from the public record: the postmortems, incident reports, and technical write-ups the companies involved published themselves. If a claim is in an episode, it traces back to one of those sources. Where CodeWicked adds an opinion, it’s labelled as exactly that — the take.

  • Public sources only Built from published postmortems and incident reports.
  • Every claim sourced No invented timelines, numbers, or causes.
  • Fact first, take second The root cause comes before the opinion — always.
  • Plain language Deep enough for engineers, clear enough for everyone else.