Illustrative scenarioDate not recordedIllustrative scenario

Distributed Rate Limiter Redis Key Collision & Global Lockout

Missing tenant namespace prefix in rate limiter Redis key caused single user limit to apply globally to all tenants.

Illustrative scenario, not a real incident

A composite failure pattern written by CollectSEA for learning and demos. It is NOT a documented real-world incident and has no primary source.

What happened

    Contributing factors stated by the source

    • Missing tenant namespace prefix in rate limiter Redis key caused single user limit to appl...

    The failure pattern

    Duplicate action after an ambiguous resultA request times out, the caller assumes it failed and retries, and the money moves (or the order ships) twice.How to prevent it Retry amplification and runaway resource consumptionRetries, loops or an expensive input multiply load until a partial failure becomes a full outage or a runaway bill.How to prevent it
    Watch the pattern: Duplicate action after an ambiguous result

    Related standards

    CollectSEA's mapping through this incident's failure pattern; not an official determination by the standards bodies.

    Building something similar?

    Describe your design and see every precedent that applies, with safeguards you can hand to your coding agent.

    Analyze your design

    Incidents with the same pattern