Proxy glossary

What is rate limiting?

Rate limiting is a site capping how many requests one client can make in a given time, then slowing or rejecting the rest.

Rate limiting explained

The client is usually identified by IP, sometimes by account, cookie or API key. Go over the limit and you get a 429 Too Many Requests, often with a Retry-After header that says how long to wait. Some sites skip the 429 and serve slower pages, CAPTCHAs or empty results instead.

Proxies spread requests across more IPs, which raises the total you can send before any single IP hits its limit. They do nothing for a per-account limit, and they are no excuse for hammering a small site.

Pacing fixes most of it: random sleeps between requests, exponential backoff with jitter on a 429, and fewer threads per hostname.

For example

Your script fetches fifty pages a second from one shop, and after a minute every response is a 429. At a few requests a second with backoff, the same script runs all night.

How it works at ProxyMonkey

  • Our acceptable use policy asks for a considerate rate. Volume high enough to degrade a site for its real users gets an account closed.
  • On ISP and datacenter orders, more threads are a paid add-on, so check what your order includes before you raise concurrency.
The community layer

Not sure how it applies to you?

Post what you are trying to do in Discord. Someone who has hit the same thing will explain it against your setup.

Join the Discord

4,200+monkeys in the Discord

  • Help from humans

    Post your error, get an answer. Usually in minutes, usually from someone who has hit the same wall.

  • A status bot that tells on us

    Pool health, incidents and maintenance posted automatically. Including the bad days.

  • Deals and free traffic

    Bonus GB drops, early access to new pools, and the occasional giveaway for a good bug report.

Join the Discord4,200+ monkeys, free to lurk