The number of proxies you need depends on four variables: your request volume, rotation interval, target site sensitivity, and concurrency requirements. For web scraping with ISP proxies, the baseline formula is: number of IPs = (requests per hour) / (safe requests per IP per hour) x 1.25 safety factor. Against moderately protected sites, "safe requests per IP per hour" is typically 50-100 for ISP proxies and 200-500 for datacenter proxies on unprotected targets. A scraping operation processing 100,000 pages per day needs approximately 50-85 ISP proxies or 5-10 GB of residential bandwidth (Hex Proxies sizing data, April 2026).
Quick Answer
| Use Case | Proxy Type | Sizing Rule | Example at Scale |
|---|---|---|---|
| Web scraping (protected sites) | ISP | 1 IP per 50–100 req/hr | 100K pages/day → 50–85 IPs |
| Web scraping (unprotected) | ISP or Datacenter | 1 IP per 200–500 req/hr | 100K pages/day → 10–25 IPs |
| Social media management | ISP (dedicated) | 1 IP per account | 50 accounts → 50 IPs |
| Sneaker bots | ISP (dedicated) | 1 IP per site per session | 5 sites, 3 sessions → 15 IPs |
| Ad verification | Residential | Bandwidth-based: 0.5–1 GB per 1K checks | 10K daily checks → 5–10 GB/day |
| SEO monitoring | Residential or ISP | 1 IP per 100–200 SERP checks/hr | 50K SERPs/day → 15–25 IPs or 3–5 GB |
| Price monitoring | ISP | 1 IP per 100–150 req/hr | 500K prices/day → 150–210 IPs |
| Account management | ISP (dedicated) | 1 IP per account | 200 accounts → 200 IPs |
Bottom line: For most use cases, start with the table above, add a 25% safety buffer, and scale up based on actual success rate data. Over-provisioning by 25% is cheaper than under-provisioning and hitting rate limits.
The Universal Sizing Formula
Every proxy sizing calculation reduces to one equation:
Required IPs = (Total Requests per Hour / Safe Requests per IP per Hour) x Safety Factor
The three variables:
Total Requests per Hour
This is your workload divided by your operating window. If you need to scrape 100,000 pages in 24 hours, that is 4,167 requests per hour. If you need to scrape the same 100,000 pages in 8 hours (business hours only), that is 12,500 requests per hour — requiring 3x more proxies.
Tip: Spreading your workload over a longer window reduces the number of proxies needed linearly. If cost is a constraint, extend your scraping window before buying more IPs.
Safe Requests per IP per Hour
This is the maximum number of requests you can send from a single IP before the target site starts throttling, CAPTCHA-ing, or blocking. It varies dramatically by target:
| Target Type | ISP Proxy (Safe Rate) | Residential Proxy (Safe Rate) | Datacenter Proxy (Safe Rate) |
|---|---|---|---|
| Unprotected API/site | 200–500 req/hr | 300–800 req/hr | 500–2,000 req/hr |
| Light protection (basic WAF) | 100–200 req/hr | 150–400 req/hr | 50–150 req/hr |
| Moderate protection (Cloudflare standard) | 50–100 req/hr | 80–200 req/hr | 10–30 req/hr |
| Heavy protection (Cloudflare Enterprise, Akamai) | 20–50 req/hr | 30–80 req/hr | 5–15 req/hr |
Why ISP safe rates are lower than residential per-IP: ISP proxies are static — the same IP makes all requests. Anti-bot systems track request frequency per IP. Residential proxies rotate, so each IP only makes a few requests before being replaced. But you do not need to calculate pool sizes for residential — you buy bandwidth, not IPs.
Safety Factor
Always multiply your calculated proxy count by 1.2-1.3 (20-30% buffer). This accounts for: - IP cooling periods (some IPs need rest after heavy use) - Target-side rate limit changes (sites tighten limits without notice) - Traffic spikes above your baseline - IP replacement (if a provider needs to swap a flagged IP)
Sizing by Use Case
Web Scraping
Web scraping is the most common proxy use case and the most variable in sizing because target site defenses range from nonexistent to extremely aggressive.
Scenario: 100,000 product pages per day from a Cloudflare-protected e-commerce site
Using ISP proxies with moderate protection (50-100 safe req/IP/hr):
- Operating window: 20 hours (leave 4 hours for off-peak processing)
- Requests per hour: 100,000 / 20 = 5,000 req/hr
- IPs needed: 5,000 / 75 (midpoint) = 67 IPs
- With 25% buffer: 67 x 1.25 = 84 ISP proxies
- Monthly cost at Hex Proxies: 84 x $2.25/IP = Using residential proxies (bandwidth-based):
- Average page size: 1.5 MB
- Total bandwidth: 100,000 x 1.5 MB x 1.08 (8% retry overhead) = 158.4 GB/day
- Monthly bandwidth: 158.4 x 30 = 4,752 GB
- Monthly cost at $4.50/GB: $21,384/month ISP proxies are 113x cheaper than residential for this workload. The breakeven favoring residential only occurs when you need IPs from 50+ countries simultaneously or your target specifically blocks all ISP-range IPs. Scenario: 10,000 pages per day from lightly protected sites Using ISP proxies (150 safe req/IP/hr):
- Requests per hour: 10,000 / 20 = 500 req/hr
- IPs needed: 500 / 150 = 3.3 → round up to 4
- With buffer: 4 x 1.25 = 5 ISP proxies
- Monthly cost: 5 x $2.25 = Key insight: Small-scale scraping requires surprisingly few proxies. Five ISP proxies can handle 10,000 daily pages against most targets. Social media platforms (Instagram, TikTok, LinkedIn, X/Twitter) fingerprint accounts by IP address. Using one IP for multiple accounts is the fastest way to trigger account linking and mass bans. The rule is absolute: 1 dedicated ISP proxy per account. Why ISP over residential: Social media accounts need the same IP consistently (sticky sessions). Residential proxies rotate IPs, which looks suspicious to platforms that expect consistent login locations. ISP proxies provide permanent sticky IPs that mimic a real user's stable home connection. Additional considerations:
- Instagram: Same IP for all account activity. Warm new accounts gradually (3-5 days of light activity before automation).
- TikTok: More lenient on IP changes but still flags rapid account switching. One IP per account is safest.
- LinkedIn: Strictest platform. One IP per account, consistent login times, gradual activity increase.
- X/Twitter: Moderate enforcement. One IP per account recommended, but shared residential IPs work for read-only monitoring. Sneaker bot proxy sizing depends on the number of target sites, concurrent release sessions, and the intensity of anti-bot protection on each platform. Sizing formula: IPs = (number of sites) x (sessions per site) x (tasks per session / safe tasks per IP) Typical requirement:
- 1 proxy per checkout task per site
- Most botters run 3-10 tasks per release
- Each task needs its own IP to avoid cart conflicts Why ISP proxies dominate sneaker botting: Speed matters (limited releases sell out in seconds), sticky sessions are required (maintaining cart state through checkout), and unlimited bandwidth prevents cost anxiety during critical drops. Ad verification requires checking ad placements from diverse geographic locations. This is one of the few use cases where residential proxies are the clear winner because:
- You need IPs from many countries/cities to verify geo-targeted ads
- Each check is a single page load (no session state needed)
- The rotating pool handles IP diversity automatically Sizing (bandwidth-based):
- Average ad verification page load: 2-4 MB (includes ad creative, tracking pixels)
- 1,000 checks ≈ 2-4 GB of bandwidth
- 10,000 daily checks ≈ 20-40 GB/day Cost optimization: Render ads in headless browsers with image loading disabled to reduce bandwidth by 60-70%. Many ad verification tools support this natively. SEO monitoring requires checking search engine results pages (SERPs) from various locations without triggering Google's bot detection. Sizing approaches: Option 1: ISP proxies (for focused monitoring)
- Google allows approximately 100-200 searches per IP per hour before CAPTCHA triggers
- 50,000 daily SERP checks / 20 hours = 2,500 checks/hr
- IPs needed: 2,500 / 150 = 17, with buffer = 21 ISP proxies
- Monthly cost: 21 x $2.25 = $47.25/month Option 2: Residential proxies (for geo-diverse monitoring)
- Average SERP page: 0.8-1.2 MB
- 50,000 checks x 1 MB = 50 GB/day = 1,500 GB/month
- Monthly cost: 1,500 x $4.50 = $6,750/month ISP proxies are the clear winner for SEO monitoring unless you specifically need SERPs from 50+ countries, in which case residential's geo-diversity justifies the premium. Decision rule: If you need the same IP for more than 30 minutes or need to associate specific IPs with specific accounts, use dedicated ISP proxies. If you need IPs from 30+ countries or only send 1-5 requests per IP, use residential rotating pools. Assumptions: 1.5 MB average page, Cloudflare-protected targets, 20-hour daily scraping window, Hex Proxies pricing ($2.08/IP ISP, $4.50/GB residential). Hex Proxies simplifies proxy sizing with transparent pricing and tools designed to prevent over- or under-provisioning. What this means for sizing decisions: The most cost-effective approach for most customers: start with the recommended count from the sizing table, monitor success rates for the first week, and adjust. Over 90% of customers find their sweet spot within the first billing cycle. Data in this guide is sourced from: How many proxies do I need for web scraping?
For ISP proxies against moderately protected sites, use 1 proxy per 50-100 requests per hour. A typical operation scraping 100,000 pages per day needs 50-85 ISP proxies. For unprotected sites, 10-25 ISP proxies handle the same volume. For residential proxies, buy bandwidth instead of counting IPs: 100,000 pages per day at 1.5 MB average requires approximately 150 GB/day. How many proxies do I need per Instagram account?
One dedicated ISP proxy per Instagram account — no exceptions. Instagram fingerprints accounts by login IP, and sharing IPs across accounts triggers account linking detection. At Hex Proxies, that is $2.08-2.25 per account per month. Warm new accounts on their dedicated IP for 3-5 days before starting automation. Can I use one proxy for multiple social media accounts?
No. All major platforms (Instagram, TikTok, LinkedIn, X/Twitter) associate accounts with IP addresses. Using one proxy for multiple accounts risks all accounts being flagged simultaneously. The only exception is read-only monitoring (checking public profiles without logging in), where shared residential proxies work. How many proxies do I need for sneaker bots?
One proxy per checkout task per site. If you are running 5 tasks on Nike and 3 on Adidas, you need 8 proxies minimum. Most serious botters maintain 25-100 ISP proxies for a rotation buffer. At $2.08-2.25/IP, a 50-proxy sneaker setup costs Should I buy more proxies than I need?
Yes, by 20-30%. Over-provisioning creates headroom for traffic spikes, allows IP cooling (resting IPs that have been used heavily), and provides backups if individual IPs get flagged. The cost of 20% more IPs is far less than the revenue impact of hitting rate limits. When should I use residential proxies instead of ISP for sizing?
Use residential when you need IPs from 30+ countries simultaneously (geo-diverse ad verification, global price monitoring), when you need millions of unique IPs (large-scale scraping that exhausts static IP pools), or when targets specifically detect and block ISP proxy ranges. For everything else, ISP proxies are more cost-effective. How do I know if I have enough proxies?
Monitor your success rate. If it is above 95%, your proxy count is adequate. Between 90-95%, you are borderline and should add 20-30% more IPs. Below 90%, you are under-provisioned — increase your proxy count by 50% or investigate whether the issue is IP quality rather than quantity. Does the number of proxies I need change over time?
Yes. Target sites update their anti-bot rules, your traffic volume may grow, and seasonal patterns (holiday shopping, sneaker releases) create spikes. Review your proxy sizing quarterly and before any known traffic increase. Hex Proxies' no-commitment model lets you scale up and down monthly. What is the minimum number of proxies for a small scraping project?
For ISP proxies, you can start with as few as 5 IPs ( How do I calculate proxy needs for multiple use cases?
Calculate each use case independently, then sum the totals. If you need 50 ISP proxies for scraping and 30 for social media, you need 80 total. Do not share proxies across use cases — a proxy used for aggressive scraping should not be used for social media account management, as the scraping activity can degrade the IP's reputation.Social Media Management
Scale ISP Proxies Needed Monthly Cost (Hex Proxies) Cost per Account 10 accounts 10 $22.50 $2.25/account 50 accounts 50 $2.25/account 200 accounts 200 $416.00 ($2.08/IP at scale) $2.08/account 500 accounts 500 $2.08/account Sneaker Bots
Scale Sites Tasks per Site ISP Proxies Needed Monthly Cost Casual 2 3 6 Intermediate 5 5 25 $56.25 Serious 10 10 100 $208.00 Professional 15 20 300 $624.00 Ad Verification
Daily Checks Monthly Bandwidth Monthly Cost (Hex Proxies) 1,000 60–120 GB $270–540 10,000 600–1,200 GB $2,700–5,400 50,000 3,000–6,000 GB SEO Monitoring
Rotating Pool vs. Dedicated IPs: When to Use Each
Factor Rotating Pool (Residential) Dedicated IPs (ISP) Sizing model Buy bandwidth (GB) Buy IP count IP management Automatic (provider handles rotation) Manual (you manage which IP does what) Session control Sticky for 1-30 min Permanent sticky Best for High-volume, geo-diverse, stateless requests Account management, session-based, speed-critical Cost efficiency Better for low-volume, geo-diverse Better for high-volume, same-region Risk Shared pool — other users affect IP quality Dedicated — your behavior alone determines IP health Cost Projections at Scale
Monthly Scale ISP Proxies ISP Cost (Hex Proxies) Residential Equivalent Residential Cost 10K pages/day 5 IPs 45 GB $202/mo 50K pages/day 30 IPs $67.50/mo 225 GB 100K pages/day 85 IPs 475 GB $2,138/mo 500K pages/day 400 IPs $832/mo 2,375 GB 1M pages/day 800 IPs 4,750 GB $21,375/mo How Hex Proxies Handles This
Methodology
Frequently Asked Questions
Tips