Buying Guides 5 min read

How Many Proxies Do I Need? A Practical Way to Work It Out

The right number of proxies depends on requests per minute, per-IP limits and how many accounts you run. Here's the math.

How many proxies do I need is one of the most common questions buyers ask, and the honest answer is that it depends on what you're counting. If you rent static IPs one by one, the number of IPs is the thing you buy. If you use a rotating residential gateway, you don't buy IPs at all: you buy bandwidth and every request can come from a different address. This guide gives you a formula for each situation, with worked examples.

Two Ways Proxies Are Sold

  • Static lists: you pay per IP and get a fixed list. The count you buy is the count you have. Common for cheap datacenter products.
  • Rotating gateways: you pay per GB (or per hour) and connect to one endpoint that hands out IPs from a large pool. The useful questions become how many concurrent connections you run and how many distinct sessions you need.

NodeProxies residential, mobile and datacenter plans all use a gateway, so for most readers the second half of this post matters more. Our rotating proxy explainer covers how a gateway hands out IPs.

Formula 1: Scraping and Data Collection

For scraping, the number of IPs you need is driven by how many requests a target tolerates from one IP before it rate-limits you.

IPs needed = (requests per minute you want) / (safe requests per minute per IP)

Say you want 600 requests per minute and testing shows the site starts returning 429 errors above about 10 requests per minute from one IP. You need around 60 IPs active per minute. Add a margin of 30 to 50 percent because some IPs will be slower or already have history on the site, so plan for 80 to 90.

With a static list you'd buy 90 IPs. With a rotating gateway you simply send 600 requests a minute without a session parameter: each request gets a fresh IP, so no single IP comes close to the limit. You're paying for the bandwidth of those 600 requests, not for the 90 addresses.

How to find the safe per-IP rate

  1. Pick one sticky session so all requests use one IP.
  2. Send requests at a slow, fixed rate (for example one every 6 seconds) and log status codes.
  3. Increase the rate step by step until you see 429s, CAPTCHAs or 403s.
  4. Use about half of the rate where problems started as your safe figure.

The 429 too many requests guide explains what those responses mean and how to back off.

Formula 2: Managing Accounts

If you manage your own or your clients' accounts on a platform, the rule is simple: one consistent IP per account, and never share an IP between accounts that should look independent.

IPs needed = number of accounts you run at the same time

A social media manager handling 12 client accounts needs 12 separate identities. On a gateway that means 12 sticky sessions, each with its own id, for example USERNAME-session-client01-time-60 through USERNAME-session-client12-time-60. The same id returns the same IP until the time runs out. For account work, pick a session time that covers your working block and keep the country fixed with -country-xx so the location doesn't jump.

Formula 3: Browsing and Geo-Testing

If you're checking how a site looks from different countries, count the countries, not the requests. Five markets means five country settings, which on a gateway is just five usernames (-country-us, -country-gb, -country-de and so on). One plan covers all of them.

Worked Examples

  • Price monitor checking 5,000 product pages twice a day on a tolerant retailer: rotating residential, no session, concurrency of 10 to 20 threads. IP count doesn't matter; bandwidth does.
  • SEO rank tracking for 300 keywords across 3 countries: rotating residential with one country parameter per market. See proxies for SEO.
  • Agency running 20 client ad accounts: 20 sticky sessions, ideally mobile or residential, one per account, same country as the client.
  • Developer testing a signup flow from 4 countries: four usernames with country targeting and a short session each.

Concurrency Is the Number That Actually Limits You

On a gateway, the practical ceiling is how many simultaneous connections your machine and code can sustain, not how many IPs exist. A Python script with 20 threads makes 20 concurrent requests, each potentially on a different IP. Start low, watch success rate and latency, and raise the thread count only while success stays high.

Getting the Right Setup on NodeProxies

Because NodeProxies sells bandwidth, not IP slots, you don't have to guess an IP count up front. Rotating residential proxies draw from a pool of 90M+ IPs in 195+ countries; mobile proxies from 1M+ carrier IPs. Buy a small plan, measure your real per-IP limit and bandwidth, then scale on the pricing page. No contracts, and unused balance never expires.

FAQ

How many proxies do I need for web scraping?

Divide the requests per minute you want by the safe rate per IP, then add 30 to 50 percent. On a rotating gateway you don't buy that number; you just rotate on every request.

How many accounts can I run per proxy?

One. Accounts that share an IP can be linked by the platform, so give each account its own sticky session.

Is one rotating proxy enough?

Often yes. One gateway endpoint can give a new IP on every request, which replaces a long list of static proxies for most scraping jobs.

Does more proxies mean faster scraping?

Only if you also raise concurrency. More IPs let you send more requests without hitting per-IP limits, but speed comes from parallel connections.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account