Throughput
The rate data actually moves, not the link's headline rate.
Definitions only — a term explained here is not a service we sell.
Throughput is the rate at which data actually crosses a link in a given direction over a measured window. It is lower than the link rate because of protocol overhead, contention, loss and the sender's window.
Why it matters
A headline rate describes the interface, not the experience. Two links with the same headline rate can deliver different throughput because the path, the number of users and the traffic shape differ.
The path a rate is measured over
40 ms
| Value | What it means |
|---|---|
| 5 ms | Same metro |
| 20 ms | Regional path |
| 40 ms | Regional path |
| 80 ms | Intercontinental path |
| 150 ms | Queues or a long path |
Text description
The ruler shows round-trip time, not throughput. It is here because the path sets what a rate measurement includes: a longer path, a congested queue and a small window all lower the delivered rate.
What to check
Measure in both directions, at peak and off-peak, with the traffic shape you care about. Ask for the window, the protocol and the number of flows. The latency term and the jitter term cover the other two measurements.