Bandwidth allocation is the amount of data transfer, usually measured in gigabytes, that a proxy plan includes for a billing period. Every request and response through the proxy counts toward this total.
The provider tracks the total size of data sent and received through the proxy for each account. As users make requests, the data used is subtracted from the remaining allocation for that billing cycle. Once the allocation runs out, the provider may throttle speed, block further use, or charge extra fees depending on the terms of the plan. Larger files like images and videos use up bandwidth much faster than simple text-based page requests.
This is largely a plan and configuration choice, not a technical limitation.
USER-bandwidth-allocation-session-task01Everything lives in the username -- add "bandwidth-allocation" to any proxy credential to apply bandwidth allocation to a single task. Swap "task01" for a new label to spin up an independent, isolated identity.
KnoxProxy sticky sessions persist up to 30 minutes on residential (60 on mobile), and the window refreshes with activity.
Each session or connection label gets its own exit, so parallel identities never collide.
This costs nothing beyond bandwidth -- successful responses are billed, not the session or connection itself.
Run as many parallel sessions or connections as the job needs -- concurrency is not capped on any plan.
A user scraping product pages with images might use 5 GB of bandwidth allocation in a day, compared to under 1 GB for scraping text-only pages.
Underestimating bandwidth needs can lead to unexpected overage charges or service interruptions mid-project. Reviewing typical data use for a project helps buyers choose a plan with the right bandwidth allocation.
Bandwidth Allocation is a plan-level or configuration-level concept that determines how proxy resources get allocated across your jobs. It is a billing and management concern, not a protocol detail.
Most providers either throttle connection speed, pause the service entirely until the next billing cycle, or automatically charge for additional data used beyond the cap. The exact response depends on the specific rules of the plan, so it is worth checking the terms before a large project starts.
Yes, most plans reset bandwidth allocation at the start of each new billing cycle, regardless of how much data was left unused the month before. Some providers, however, offer rollover options that carry unused data forward, so it is worth checking this detail before committing to a large plan.
Ready to put this into practice? View Pricing Plans
Test with real targets -- instant activation, no sales call, 14-day money-back guarantee.