HavocLabAll scenarios →
SEV-0Resilience

Kamikaze Query

November 2025: a query change at Cloudflare doubles a global rule file, blowing past the memory limit of every edge-proxy parser at once. The result is a synchronized, worldwide reboot loop, and because the poisoned file regenerates every few minutes, the network keeps lurching back to life just long enough for you to close the incident channel before it explodes again. The Job: Stop the poison from crash-looping the fleet and keep serving through the flapping, with error and tail latency inside the SLA, knowing the bad file will keep coming back. Break the suicide pact before it reaches your origin.

Free to play, no account needed. A deterministic engine grades your design against this scenario's SLA - error rate, latency, and cost.