Anatomy
The November 2020 us-east-1 event started as a Kinesis front-end scaling failure and cascaded into dependent services. From a client's perspective: responses got much slower AND a fraction failed — the combination that defeats clients with too-aggressive timeouts (they abandon calls that would have succeeded) and too-loose timeouts (they hang through the whole incident).
Source: AWS post-event summary, Kinesis/us-east-1 · 2020-11-25
Replay it
curl -i https://faultydata.com/r/FD-2026-003
// response appears here
Signature
{Status:0 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Phases:[{Weight:60 Signature:{Status:200 Headers:map[] Body: Corrupt: Delay:0x4743deeeedb0 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Phases:[]}} {Weight:25 Signature:{Status:500 Headers:map[] Body:{"message":"Internal server error"} Corrupt: Delay:0x4743deeeede0 Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Phases:[]}} {Weight:15 Signature:{Status:200 Headers:map[] Body: Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Phases:[]}}]}