What this tests
authretry-logic
Point your client at this specimen and find out — before prod does — whether it handles auth failure without panic-retrying into a second incident.
Anatomy
Google ran out of quota in its own identity system — the internal service that decides whether tokens are real — and for forty-five minutes Gmail, YouTube, Workspace, all of it, told every credentialed user on Earth that their perfectly good token was rubbish. The bouncer forgot the guest list, then forgot who the bouncer was. "Your token is bad" and "the identity plane is on fire" produce the same 401. That's the horror of it: a client cannot distinguish "expired credential" from "the concept of credentials has collapsed". Only one of those is fixed by re-logging in, and the other one will eat your retry budget, your refresh tokens, and eventually your session store while you're doing it. Mostly 401s with a garnish of 500s — a composite that says "not only are you not who you say you are, we're not entirely sure we are either". Clients that retry-once-on-401 survive. Clients that retry- aggressively just DDoS'd the thing that's supposed to save them.
Source: Google Cloud infrastructure components incident 20013 · 2020-12-14
Replay it
curl -i https://faultydata.com/r/FD-2026-026
// response appears hereSignature
{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[{Weight:70 Signature:{Status:401 Headers:map[] Body:{"error":{"code":401,"message":"Request had invalid authentication credentials.","status":"UNAUTHENTICATED"}} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}} {Weight:30 Signature:{Status:500 Headers:map[] Body:{"error":{"code":500,"message":"Internal error encountered.","status":"INTERNAL"}} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}}]}
Keep digging
FD-2026-005 — Token expires mid-session (Entra ID pattern) FD-2026-027 — Signing-key rollover breaks token validation (Azure AD, Mar 2021) FD-2026-002 — CDN edge degradation (Fastly, June 2021) FD-2026-021 — S3 us-east-1 subsystem removal (AWS, Feb 2017) FD-2026-024 — Network config rollback storm (Cloudflare, Jun 2022) FD-2026-044 — Three-day outage from a consensus bug (Roblox, Oct 2021)