Why use Retry Simulator?
Client retries amplify outages when backoff is too aggressive or missing. Simulate status sequences and timeouts to see how your code would behave, then tune jitter and caps before a provider rate-limits you or amplifies an incident.
Practical tips
- Model 429 responses with Retry-After headers separately from blind 5xx loops.
- Log retry counts in production; exponential curves should plateau with a max delay.
- Compare against Rate Limit Tester results from the same endpoint.
Common questions
- Is this a load test?
- No. It is a deterministic simulator. Use Burst Simulation or Rate Limit Tester for concurrency-focused experiments.
- Does it call my real API?
- Only when you configure live fetches. Many teams start with mocked status codes.