What does unlimited mean in proxy plans?
“Unlimited” removes one meter, not every capacity limit. The 106-plan unlimited audit contains 68
unlimited_bandwidthrows and 38 concurrency-priced rows. Of those 106 plans, 97 publish a usable substitute constraint and 9 do not. A concrete pair isproxyscrape-unlimited-residential-1d-100mbpsat $190 andproxyscrape-unlimited-residential-1d-1000mbpsat $1,102: both remove the GB meter for one day, but they sell different throughput ceilings. Machine-readable unlimited audit, checked from 2026-07-26T04:42:44+03:00 through 2026-07-26T04:51:46+03:00 · ProxyScrape pricing API, retrieved 2026-07-25T16:33:08.221Z
The word must be attached to a field. It can mean no transferred-GB charge while speed, threads, ports, devices, access duration or fair use still limits the plan. It must not be read as unlimited useful work.
The replacement cap is usually visible
The audit records the primary published constraint for every held plan. Its largest exact groups are:
| Substitute constraint | Audited plans | Named plan families |
|---|---|---|
| Threads plus maximum speed | 25 | 15 LitPort rows and 10 ProxyRack rows |
| Throughput tier | 21 | 18 ProxyScrape rows and 3 ProxyEmpire rows |
| Published speed range | 13 | LitPort private-device rows |
| Threads plus whitelisted source IPs | 8 | Storm Proxies backconnect rows |
| Port, access duration and rotation controls | 8 | HydraProxy mobile rows |
The counts come from cap_field in the 106-row audit. Each audited row preserves its plan ID, source URL, evidence quote and check time. Machine-readable unlimited audit, checked from 2026-07-26T04:42:44+03:00 through 2026-07-26T04:51:46+03:00
The 21 throughput-tier rows show the simplest replacement. ProxyScrape publishes 18 combinations across one, seven and 30 days and six speed tiers. ProxyEmpire contributes daily, weekly and monthly rows with a selected throughput tier. In each case, transferred GB can be unmetered while capacity per second remains purchased. ProxyScrape source · ProxyEmpire source, both checked 2026-07-26T04:42:44+03:00
A thread limit is not an IP count
proxyrack-unlimited-residential-500-threads publishes 500 threads and unmetered transfer without publishing an IP count. litport-mobile-us-shared-device-month publishes 100 threads and a $49.99 monthly checkout, again without an IP count. The buyer can compare parallel-work ceilings, but cannot convert either row into a purchased address count. ProxyRack source · LitPort source, both retrieved 2026-07-25T16:03:55Z
hydraproxy-usa-mobile-standard-30d moves the boundary again. It publishes one port, 30-day access, a $59.95 checkout and unlimited concurrent connections. Unlimited connections do not remove the single-port or time boundary. HydraProxy source, retrieved 2026-07-25T17:34:30.296Z
Nine plans do not publish enough to size
The audit marks nine rows incomplete: geonode-unlimited-residential-monthly; two ProxyEmpire dedicated mobile rows; infatica-unlimited-residential-robots-disallowed; four ThorData high-bandwidth duration rows; and pia-s5-unlimited-residential-daily. Machine-readable unlimited audit, checked from 2026-07-26T04:42:44+03:00 through 2026-07-26T04:51:46+03:00
The reasons are different. GeoNode publishes a port and throughput ladder but acknowledges a concurrency limit without giving its number. The two ProxyEmpire mobile rows invoke carrier fair use without a numerical ceiling or post-ceiling treatment. Infatica’s dedicated path was not read because its robots policy disallowed it. ThorData leaves purchased bandwidth to a custom configuration. PIA publishes a one-day term but not the standard plan’s numerical throughput or concurrency ceiling. GeoNode on the provider’s page, checked 2026-07-26T04:51:46+03:00 · ProxyEmpire on the provider’s page · Infatica robots.txt, checked 2026-07-26T04:42:44+03:00 · ThorData on the provider’s page · PIA on the provider’s page, checked 2026-07-26T04:51:46+03:00
None of those missing numbers can be interpreted as no limit. A plan with an unpublished fair-use threshold is less calculable than one with a high but explicit cap.
How to read an unlimited offer
Ask five field-specific questions before checkout:
- Is transferred data unmetered, or does service merely continue with paid overage on the provider’s page?
- What numerical throughput, thread, session or port ceiling replaces the GB meter?
- What billing period or access duration ends the entitlement?
- Does fair use have a numerical threshold, measurement window and published consequence?
- Does the limit apply per IP, port, device, plan or account?
ProxyMesh shows why the first question matters. proxymesh-world-proxy-addon is held in the audit, but its use counts against the required parent plan’s 50 or 100 GB allowance and continues with paid overage. The audit therefore records included GB and concurrent sessions as the actual constraints instead of calling the add-on unmetered. ProxyMesh pricing docs, checked 2026-07-26T04:51:46+03:00
The practical definition is narrow: unlimited describes the meter the vendor removed. Compare the cap that remains. When that cap is not published, the plan cannot be sized from public evidence, regardless of how large the word looks on the pricing page.