On June 8th, a huge slice of the internet vanished for ~49 minutes — Reuters, the Guardian, gov.uk, Amazon’s homepage, Reddit, Twitch — and the cause was ONE customer’s valid configuration change hitting a dormant bug in FASTLY’s edge software, deployed a month earlier, waiting for the exact config shape that would detonate it globally. The file admires everything about the response (bug identified in minutes, mostly restored inside the hour, transparent postmortem within 24) and files the structural lesson with its siblings: the CDN layer is the new single point of failure the multi-cloud crowd forgot to diversify (#093’s Dyn entry, evolved — DNS then, edge now), “valid input, latent bug” is the failure signature staged rollouts exist to catch and config changes routinely skip (#159’s Cloudflare regex; the emergency lane and the config lane keep being the same unguarded lane), and a 49-minute outage that makes GLOBAL FRONT PAGES is, perversely, evidence of how reliable the substrate usually is — nobody headlines the highway that flows. The archive’s concentration-risk shelf (#093, #196, #201) now needs its own bookcase.
El Salvador, meanwhile, made BITCOIN LEGAL TENDER — the first nation-state adoption, passed in days, wallet app and $30 airdrops promised, IMF visibly unamused. The file’s read, balanced per doctrine (#200): as remittance infrastructure for a dollarized economy with 20%+ of GDP from abroad, the EXPERIMENT has genuine logic (the fees on the existing corridors are extractive); as monetary policy executed at meme velocity with volatility denominated in school budgets, the risk transfer lands on the citizens least equipped to hedge it (#204’s crash was THIS MONTH). Either way: the archive has now filed bitcoin as joke (#023), mania (#119), crash (#123), institution (#202), punchline (#204), and STATE CURRENCY — in eight years. No other thread has this range.
Also: Lina Khan — whose law-school article “Amazon’s Antitrust Paradox” reframed the entire monopoly debate this archive has tracked since #185 — was confirmed to the FTC and immediately named its CHAIR at 32. The scholar who wrote the critique now runs the agency; the #190 multi-year files just changed presiding philosophy. Watch everything.
TIL: blast-radius-per-customer as a metric — Fastly’s bug meant one customer’s config could crash the fleet; the fix category is per-customer isolation of config compilation (cells again, #192’s Kinesis file). “How much of the fleet can one tenant’s input touch?” belongs in every multi-tenant design review, including ours; we scored ourselves Monday and the answer prompted a sprint.