Skip to content
Omnikalc

Network latency calculator: how fast can a signal travel between two places?

Enter the distance, cable route factor, hops and server time to estimate the round-trip latency and compare it with the speed-of-light minimum.

Updated on
Your inputs
km

Value out of range

Value out of range

Value out of range

ms

Value out of range

ms

Value out of range

Results

Round-trip time on the network

87.0 ms

Good: fine for browsing, video calls and most games
One-way propagation delay in the fiber
37.5 ms
Time for a request, including the server
107.0 ms
Theoretical minimum round trip at the speed of light
33.4 ms
Your round trip compared with the physical minimum
2.6 ×

Even on the fastest connection, a signal cannot beat the speed of light in fiber. Distance sets a hard floor on latency, and routers and servers add to it. This calculator estimates the round-trip time between two points from the distance, the route taken by the cable, the number of hops and the server time, and compares it with the physical minimum.

How the calculation works

  • Cable path = straight-line distance × route factor
  • One-way delay = cable path ÷ 200 km per millisecond (light in fiber)
  • Round trip = 2 × one-way delay + 2 × hops × delay per hop
  • Request time = round trip + server processing
  • Physical minimum = 2 × distance ÷ 299.792 km per millisecond (light in a vacuum)

Example

Two points are 5,000 km apart and the cable runs 1.5× longer, so the path is 7,500 km and the one-way delay is 37.5 ms. With 12 hops each way at 0.5 ms, the round trip is 75 + 12 = 87 ms. Adding 20 ms of server time, a request takes 107 ms. The speed of light in a vacuum would allow 33.4 ms, so the real round trip is 2.6 times the physical minimum.

Why it matters

Latency matters for gaming, video calls, trading and any chatty application that waits for many round trips. It also explains why placing servers near users, using a content delivery network or caching can matter more than buying a faster connection.

Good to know

Real networks add queuing, Wi-Fi, cellular links and satellites, which can add tens or hundreds of milliseconds. Geostationary satellites alone add about 480 ms round trip. Use this as a floor for what is physically possible, and measure with a ping for the real value.

The bandwidth-delay product calculator shows how much data is in flight on a link, the download time calculator estimates transfer times, and the internet speed calculator checks what a plan can deliver.

Frequently asked questions

Why does distance cause latency?

Light in glass fiber travels at about two thirds of its speed in a vacuum, roughly 200,000 km per second, or 200 km per millisecond. A signal needs about 5 ms per 1,000 km of cable each way, and no amount of bandwidth can beat that.

What is the route factor?

Cables rarely run in a straight line: they follow coastlines, roads and landing stations. A factor of 1.2 to 2 is typical, which means the real path can be up to twice the straight-line distance.

What is a good ping?

Below 30 ms is excellent, up to 100 ms is fine for most uses, and above 150 ms starts to feel slow in interactive games and remote desktops. Wi-Fi and congestion add to the physical delay.

How is latency different from bandwidth?

Bandwidth is how much data per second a link can carry, while latency is how long a single packet takes to arrive. A fast connection can still feel slow if the server is far away.

Was this calculator helpful?

Thanks for your feedback!

Results are estimates provided for information purposes. They do not replace professional advice.