Throughput is the actual amount of data successfully transferred over a network connection in a given period of time. It is usually measured in megabits or gigabits per second and reflects real-world performance rather than a theoretical maximum.
A network connection has a maximum possible speed, often advertised as bandwidth, but throughput measures what actually gets delivered once real conditions are factored in. Congestion, packet loss, distance, and hardware limits all reduce throughput below the theoretical maximum. Tools measure throughput by sending a known amount of data across the connection and timing how long the transfer takes. Because throughput can change based on network load, it is often tracked over time rather than as a single fixed number.
Most proxy users only need to understand this well enough to debug it, not configure it directly.
USER-country-de-session-task01The username carries the config: "country-de" picks the exit, "session-task01" holds it in place while Throughput does its work underneath. No separate API call or handshake -- the label is the setting.
Measure this metric without a proxy first, so you know what the gateway adds versus what was already there.
This concept governs the connection to the gateway and the gateway to the target -- check both when something looks wrong.
KnoxProxy manages this at the infrastructure layer, so most jobs only need to understand it well enough to debug.
A new ISP, VPN, or office network can change how this behaves -- confirm it again after any local network change.
A proxy user runs a speed test and finds their connection has 100 Mbps of bandwidth but only 60 Mbps of real throughput during peak hours.
Throughput tells you what performance to actually expect from a proxy connection, which matters more than the advertised maximum speed. Low throughput can slow down scraping jobs, file transfers, or streaming even if the connection is technically fast.
Bandwidth is the maximum possible data rate a connection could support, while throughput is the actual data rate achieved during real use. Throughput is almost always lower than bandwidth due to network conditions.
More users sharing the same network path can cause congestion, which slows down how quickly data actually moves even if the underlying bandwidth has not changed. This is common on shared proxy pools during peak usage times.
Ready to put this into practice? Browse Datacenter Proxies
Start a free trial and test with real targets -- no credit card, no sales call.