Skip to main content
Calcimator

Network Latency Calculator

Calculate round-trip time from hops, distance, processing delays, and queuing. Includes VoIP quality assessment and TCP throughput estimate.

About this calculator

This calculator breaks round-trip latency into its four physical components and adds them up per hop. Propagation delay is distance divided by the speed of light in fiber — it uses a 0.67 velocity factor (light travels at roughly two-thirds its vacuum speed in glass fiber), so a 500 km path adds about 2.5 ms one-way no matter how fast your equipment is. Transmission delay is how long it takes to push one packet's bits onto the wire (packet size in bits divided by link speed), and the calculator applies it once per hop, assuming every hop re-serializes the full packet at the same size and link speed — a simplification, since real paths mix link speeds. Processing and queuing delay are per-hop constants you supply, multiplied by hop count.

All four are summed into one-way latency, then doubled for round-trip time, which assumes a symmetric path — real networks often have asymmetric routing. Jitter is a rough estimate (20% of total queuing delay), not a statistical measurement. VoIP quality follows the one-way delay guideline in ITU-T Recommendation G.114, "One-way transmission time": delay under 150 ms one-way is acceptable for general voice traffic, and under 100 ms is considered good, effectively imperceptible to users. TCP throughput uses the Mathis formula (throughput ≈ MSS / (RTT × √loss)) at an assumed fixed 0.1% packet loss — change conditions and this number moves a lot, so treat it as an illustrative estimate of how latency and loss cap throughput, not a live measurement.

Inputs

km
ms
ms
bytes
Mbps

Results

One-Way Latency

6.05 ms

Round-Trip Time (RTT)

12.1 ms

Propagation Delay2.49 ms
Total Processing Delay1 ms
Total Queuing Delay2.5 ms
Total Transmission Delay0.06 ms
Estimated Jitter0.5 ms
TCP Throughput (0.1% loss)30.5 Mbps
VoIP Quality (0-2)2

Figures current as of 2003. Source: ITU-T Recommendation G.114, "One-way transmission time," International Telecommunication Union Telecommunication Standardization Sector

How to Use This Calculator
  1. Enter Total Distance, Number of Hops, and Processing Delay per Hop.
  2. Set Queuing Delay per Hop, Packet Size, and Link Speed.
  3. Review One-Way Latency (ms) and Round-Trip Time (RTT) (ms).
  4. Use Propagation Delay (ms) and Total Processing Delay (ms) to inform your decision.
  5. Use the chart to visualize the results and explore different scenarios by adjusting inputs.

How the result changes with Number of Hops

Number of HopsOne-Way LatencyRound-Trip Time (RTT)
2.54.27 ms8.54 ms
3.755.16 ms10.32 ms
7.57.83 ms15.66 ms
1311.75 ms23.49 ms

What each input means

Total Distance
Total physical distance of the network path in kilometers
Number of Hops
Number of routers/switches in the path
Processing Delay per Hop
Router/switch processing time per hop (0.1-0.5 ms typical)
Queuing Delay per Hop
Average queuing delay at each hop (depends on congestion level)
Packet Size
Packet size in bytes (1500 = standard Ethernet MTU)
Link Speed
Bottleneck link speed in Mbps

How this is calculated

Formula

Latency = Propagation + Processing + Queuing + Transmission

Worked example, using the default values

  1. Identify Input Parameters
    4 parameters
    Total Distance = 500, Number of Hops = 5, Processing Delay per Hop = 0.2, Queuing Delay per Hop = 0.5 = 6 input(s) provided
  2. Calculate One-Way Latency
    One-Way Latency
    6.05 = 6.05
  3. Calculate Round-Trip Time
    Round-Trip Time
    12.1 = 12.1
  4. Calculate Propagation Delay
    Propagation Delay
    2.49 = 2.49
  5. Calculate Total Processing Delay
    Total Processing Delay
    1 = 1

Figures and sources

Engine last updated . Checked against 1 independently-derived test — how we verify calculators. Built by Paul Gunder, a software engineer, not a licensed financial, medical, or legal professional.

Frequently Asked Questions

Why does propagation delay use a 0.67 velocity factor instead of the speed of light in a vacuum?

Light travels slower inside glass fiber than in a vacuum because of the fiber's refractive index, and 0.67 (about two-thirds of c) is the standard approximation used for typical single-mode fiber. The calculator multiplies the vacuum speed of light by this factor before dividing distance by it, which is why even a theoretically instant network still carries a fixed physical delay per kilometer of fiber.

Why is transmission delay multiplied by the number of hops instead of applied just once?

Every hop that forwards the packet has to receive and re-transmit the full packet onto its outgoing link before passing it along, so the calculator adds one transmission delay per hop rather than treating it as a one-time cost at the source. This assumes every hop is at the same link speed and packet size as your inputs, which real mixed-speed paths won't always match exactly.

Why does TCP throughput drop so sharply when I increase either RTT or packet loss?

The calculator uses the Mathis formula, throughput ≈ MSS / (RTT × √loss), where RTT sits in the denominator directly and loss enters as a square root — so doubling RTT halves the throughput estimate, while quadrupling the loss rate only cuts throughput in half (since √4 = 2). This captures why long, lossy paths punish TCP performance far more than short, clean ones.

What's the difference between one-way latency and RTT here, and why is RTT just double the one-way figure?

One-way latency sums propagation, processing, queuing, and transmission delay for a single direction of travel, and the calculator doubles that total to get round-trip time, implicitly assuming the return path is identical in distance, hop count, and congestion. Real networks often route asymmetrically, so an RTT you measure with a ping may differ from this doubled estimate even when your inputs are accurate.

The questions that sit next to this one — chosen by subject, including calculators filed under a different category.

More in Technology & Computing.