Choose the IP behaviour your job needs, then compare how you pay. Allocated addresses can suit fixed-IP requirements; rotating pools can suit changing exits. Neither determines the billing model. Compare traffic allowances, connection limits and cost per usable result before buying a larger package.
Count the right thing. Allocated IPs, pool size, simultaneous connections and transferred GB describe different limits.
Choose continuity first. A sticky session requests the same exit; it does not replace an assigned fixed address.
Compare the whole job. Include minimum purchases, traffic allowances, retries and usable results, rather than comparing headline prices alone.
Trial before scaling. Test your actual client, target and location requirements with a small budget.
Buying bulk residential proxies or datacenter access involves two decisions: what addresses the job needs, and how the service charges for them. A fixed IP can carry a per-GB charge. A rotating pool can come with a monthly traffic bundle. Separate those decisions before comparing prices.
What does “bulk proxies” actually mean?
A bulk proxy offer might sell an allocated list of addresses, rotating-pool access or a traffic package. “Bulk” is not a specification. Ask which of these quantities the offer describes:
- Allocated IPs: addresses assigned to your account. Confirm whether they are exclusive and how long the assignment lasts.
- Pool size: possible exits across the service. It does not establish availability in your chosen location.
- Concurrent connections: connections allowed at once. It does not establish how many distinct exits you receive.
- Traffic allowance: data included or purchased. It does not translate into a fixed number of pages.
- Session duration: continuity requested or contracted. Check what happens if the exit becomes unavailable.
A package of 100 allocated addresses is different from permission to open 100 connections through a rotating service.
When buying allocated IPs makes sense
Choose allocated addresses when the address itself is a requirement, such as an integration that must connect from a known source IP.
Confirm assignment duration, exclusivity, replacement rules and traffic charges. “Dedicated,” “static” and “exclusive” should have explicit meanings in the offer; do not assume they promise the same thing.
A static IP also does not preserve a website login by itself. Your application still needs its cookies and authentication state.
When paying per GB makes sense
Traffic pricing can fit jobs where you can estimate data use, including regional checks and permitted public-page research. Verify the required address behaviour separately.
Estimated traffic charge = counted GB × the selected tier's price per GB.
Use counted traffic rather than page-body size alone. Headers, uploads, protocol traffic and browser media can affect usage. Check the provider's metering rules, minimum top-up, expiry and any monthly commitment before budgeting.
Compare monthly and per-GB charges
Suppose an allocated-address offer costs $2 per IP per month. Fifty IPs cost $100 per month. For this example, assume its included traffic covers the workload and there are no additional traffic charges. This is a hypothetical offer, not a competitor quote.
At $2.50 per GB, a usage-priced service would charge:
- 10 GB: $25.
- 40 GB: $100.
- 100 GB: $250.
The charges match at 40 GB, calculated as $100 ÷ $2.50/GB. This is an arithmetic crossover, not a recommendation. Both offers must satisfy the same address type, location, continuity and capacity requirements for the comparison to help.
If the monthly plan includes too little traffic, add its overage charges. If the other offer cannot provide required fixed addresses, its lower total cannot make it suitable. Examples exclude taxes and other fees.
Measure cost per usable result
A lower price per GB can still produce a more expensive completed job if retries and unusable responses consume more traffic.
Define success before a trial. For a regional catalogue check, success might require the expected product fields for the intended country. HTTP 200 alone is insufficient if the response is a challenge page or the wrong content.
Proxy cost per 1,000 usable results = proxy spend ÷ usable results × 1,000.
Hypothetically, $12 of proxy usage producing 8,000 usable results costs $1.50 per 1,000 results. This excludes compute and labour; include them when comparing total operating costs.
Test the same permitted task with the same client settings and success definition. Record traffic, retries, usable results and elapsed time.
Do you need 100 IPs, or 100 connections?
Start with the workload. At a steady 10 requests per second and an average two-second request duration, about 20 requests are in flight on average: 10 × 2.
That is not a complete connection-limit calculation. One-request-per-connection clients need connections for those requests; multiplexing can use fewer, while idle pooled connections can raise the open-connection count. Traffic bursts and slower requests also need headroom.
Nor does 20 in-flight requests imply 20 unique exits. Several connections can share an exit. Verify the provider's limit and your client's actual connection count, and respect the target's rules before increasing throughput.
Where PrivateByte fits
PrivateByte sells traffic-priced rotating access. It does not promise an allocated bundle of permanent IPs. Published rates checked on 14 November 2026 include:
| Tier | USD per GB | Relevant limit |
|---|---|---|
| Datacenter Rotating | $0.75 | US-only beta; no timed sessions |
| Essential residential | $1.50 | Country targeting; best-effort sessions |
| Standard residential | $2.50 | Country targeting; timed-session requests |
These are retail usage rates, not prices per IP or successful result. Review the current tier details and confirm suitability before adding credit, especially if your job needs an unchanged address.
For the next decision, read rotating versus sticky proxies or datacenter versus residential proxies.
Before buying a larger proxy package
Write down these requirements and confirm them during a small trial:
- Address requirement: allocated or rotating; shared or exclusive; country or more specific location.
- Continuity: how long an exit must remain unchanged, and what happens if it changes.
- Capacity: permitted simultaneous connections, any throughput limits and client compatibility.
- Billing: what counts as traffic, minimum purchase, expiry, renewal and overage rules.
- Acceptance: the fields or page content that make a result usable, plus a retry limit and spending cap.
- Recovery: replacement or refund terms, and how your application handles an unavailable exit.
Buy the smallest package that can validate those requirements. Scale after the trial demonstrates that the service fits the job.
Common questions
Does a million-IP pool give me a million proxies? It describes an advertised pool, not a million allocated addresses. Ask how availability, targeting, concurrency and usage limits affect what your account can access. A pool-size claim alone does not establish how many distinct exits your job will receive.
Can I buy 100 fixed residential IPs from PrivateByte? PrivateByte's listed rotating tiers do not provide a guaranteed bundle of fixed residential addresses. A sticky-session request is not equivalent to that product. Confirm a fixed-address requirement before adding credit.
How many GB do I need for a million requests? Measure counted bytes across a representative batch, including retries, then multiply the average by one million. A request count alone cannot establish traffic because response sizes and connection behaviour vary. See our request-cost measurements for dated examples and their limitations.
Are allocated IPs always cheaper at high volume? No. Their traffic allowance, extra charges and suitability for the task determine whether the monthly price is useful. Compare equivalent requirements and the cost of usable results, rather than treating an IP count as an unlimited traffic package.
Does a sticky session guarantee a fixed IP? Not on PrivateByte's rotating residential service. A session requests continuity, but the exit can change when availability changes. A job that cannot tolerate an address change needs a service that explicitly provides the required assignment terms.