Cloud & DevOps

What is Rate Limiting?

Quick answer

Restricting how many requests a user, device, or application can make to a service within a set time period.

Rate Limiting, explained

Rate limiting protects services from overload, abuse, and runaway costs. An API might allow each key 100 requests per minute; once the limit is reached, further requests receive an error, commonly HTTP status 429 Too Many Requests, until the window resets.

Rate limits defend against brute-force password guessing, scraping, spam, and some denial-of-service attacks. They also ensure fair use, so one heavy user does not degrade the experience for everyone else. Common algorithms include fixed windows, sliding windows, and token buckets, which allow short bursts while enforcing an average rate. Rate limiting is often implemented in API gateways, load balancers, or content delivery networks. Well-behaved clients respect limits and retry with gradually increasing delays.

Related terms

Guides that mention Rate Limiting