🔁
🧪 Simulate
LV2 · Toolooo Standard
Explore → See → Understand → ActUnderstand it. Feature Level describes the depth of the tool experience.

Retry Storm Simulator

Watch retries turn a normal traffic spike into a server-crushing storm — and see how backoff and jitter fix it.

EngineeringBackendReliabilityArchitecture
100 req/s
30%
Advanced: max retries & jitter
3

Simulating a 5-second outage: the server fails every request for the first 5 seconds, then recovers. Watch what happens to already-failed requests still trying to retry.

0s1s2s3s4s5s6s7s8s9s10s11s12s13s14s15s16s17s18s19s
Original trafficRetry trafficOriginal rate baseline
Same traffic & failure rate — with vs. without backoff
No backoff (current)
142 req/s
peak load, live chart above
With backoff + jitter
130 req/s
peak load, same inputs
Peak load on server
142 req/s
Amplification
1.4×
vs. original traffic
Successful requests
~99 req/s
of ~100 req/s during the outage
Never succeed
~1 req/s
still failing after 3 retries
Wasted retry attempts
~15
retries from requests that never succeeded
What happened
Peak load stays close to normal at 142 req/s (1.4× baseline).
Why
At this failure rate, retries aren't compounding into a storm yet — but raise the failure rate and immediate retries stack on top of each other fast.
Try
With backoff + jitter, peak load would be about 130 req/s instead of 142 req/s — roughly 1.1× lower. Turn on exponential backoff above to see it.

Understand Retry Storm Simulator

What this tool helps you understand

Set an original request rate and a failure rate, then watch traffic amplify in real time as failed requests retry immediately. Switch on exponential backoff and jitter and watch the same storm settle into something the server can actually survive. The consequence is visualized, not just calculated.

When to use it

Use Retry Storm Simulator when engineering, backend, and reliability work raises questions about retry storm, retry amplification, and exponential backoff and you need a concrete view before making the next move.

How to read the result

Compare the shape and direction of different scenarios. The useful signal is how the result changes when an input changes, rather than one isolated number.

Assumptions and limits

The traffic model simplifies failure and retry behavior. It is designed to compare immediate retry, backoff, and jitter patterns; it is not a production load test.