What “unlimited” means in practice
There are three genuinely different products sold under the same word, and confusing them is how people overpay:
- Unlimited bandwidth, limited concurrency. The most common form. You can move as much data as you like, but only through a fixed number of simultaneous threads, sessions or ports. Your ceiling is throughput, not volume.
- Unlimited on a dedicated port. You rent an endpoint — often mobile or ISP — and use it as much as the connection physically allows. Honest and genuinely unlimited, but it is one IP, so it does not replace a rotating pool.
- “Unlimited” with a fair-use clause. Unlimited until the provider decides you are unreasonable, at which point you get throttled or asked to upgrade. Read the terms before committing.
None of these are scams. They are different shapes of the same cost problem, and the shape determines whether the plan suits your work.
The limits nobody puts on the pricing page
| What to ask | Why it decides the deal |
|---|---|
| How many concurrent threads? | The real throughput ceiling on unlimited-bandwidth plans |
| How many IPs can I touch per day? | Some pools cap unique IPs even when traffic is unlimited |
| Which countries are included? | “Unlimited” frequently means unlimited in a short geo list |
| Is it rotating or sticky? | Sticky sessions and rotation are priced differently |
| What is the minimum term? | Monthly commitment is where the risk sits if the pool underperforms |
| Is there a fair-use clause? | Determines whether “unlimited” survives contact with real usage |
If a seller will not answer the thread question with a number, that is your answer.
The break-even, in plain numbers
Per-GB residential traffic at our end of the market runs around $0.65 to $1.35 per gigabyte. Unlimited plans in 2026 typically start in the low hundreds per month. So the arithmetic is not complicated:
- Under roughly 100GB a month: per-GB wins comfortably, and with non-expiring traffic you carry the remainder forward instead of losing it.
- Several hundred gigabytes a month, consistently: unlimited starts making sense — if the thread limit supports your throughput.
- Spiky usage: per-GB wins even at high totals, because a monthly commitment charges you for the quiet weeks too.
The word doing the work in that middle bullet is consistently. Most people who think they need unlimited actually have spiky usage and would pay less on a per-GB balance that does not expire.
The expiry trap that makes unlimited look better than it is
Plenty of providers sell per-GB traffic that expires after 30 days. That single term is what pushes people toward unlimited plans: if unused gigabytes evaporate, buying volume feels wasteful and a flat monthly fee feels safer.
Remove expiry and the comparison changes completely. Traffic that stays on your balance until you use it means you can buy small, test properly, and scale when the work actually arrives — with no monthly deadline to spend against. That is how our gigabyte plans work, and it is the main reason the unlimited question matters less than the marketing suggests.
Choosing by workload
| What you are doing | Best fit |
|---|---|
| Testing a target site before committing | A few non-expiring gigabytes |
| Steady large-scale scraping | Unlimited plan, but confirm the thread count first |
| Account work and logins | Static ISP or residential IP — volume is irrelevant here |
| Heavy use of one identity | Dedicated mobile port — genuinely unmetered |
| Unpredictable, bursty projects | Per-GB balance, every time |
Whatever you buy, verify what you actually received: the IP check tool prints the autonomous system and its owner, so a hosting range sold to you as residential is obvious within seconds.