Try a rate limit before putting it into production

Supply a request timeline and a rate-limit policy. See which requests are accepted and when rejected requests could retry.

In your browser nothing you paste is uploaded

What to provide

The example models a short burst of requests so you can see which ones a policy permits.

algorithm: Use "token-bucket", "fixed-window", or "sliding-window".
limit: A positive integer request budget. For token buckets this is also the bucket capacity.
windowSeconds: The positive duration in seconds. Token buckets refill limit tokens over this duration.
requests: An array of nonnegative timestamps in seconds, in ascending order. Equal times represent a burst.

Input template

{
  "algorithm": "token-bucket",
  "limit": 3,
  "windowSeconds": 10,
  "requests": [0, 0, 0, 1, 5, 10]
}

Models one client and one ideal clock. Distributed counters, races, network delays, and a real server’s behavior are outside this simulation.

This checks one thing. A scan reads your whole repository and tells you what an attacker would find first.

Free scan

More tools