Reading room / Coordination
Setting a pace for requests
A rate limit controls how often an action can happen within a period of time. A request may be valid on its own and still exceed a rule about frequency.
General educational information
A rule needs a scope
A system might count requests from an account, a client or a network address. It also needs a time window and a response when the threshold is reached. These choices affect who shares a limit and how quickly activity can resume.
A hypothetical example
Imagine a demonstration application allowing five requests in a minute. A sixth request arrives before that window ends. The application declines it temporarily. These numbers illustrate a rule only; they do not describe this website or any company system. A different rule might allow a short burst.
Capacity and fairness
Limiting repeated actions can reduce strain and discourage some automated abuse. It can also affect ordinary users. Several people may share a network address, while one automated client may use several addresses. The counting method therefore influences both usefulness and unintended restrictions.
A limit is one control
Rate limiting does not establish a requester’s identity or decide whether an individual action is authorized. It also cannot solve every form of unwanted traffic. When evaluating a rule, ask what is counted, over which interval, and what happens at the threshold. A clear explanation helps someone distinguish temporary throttling from an invalid request or a permanent access decision.
Further reading: Cloudflare: what is rate limiting?.