Network Latency Calculator
Estimate propagation delay over a distance and medium.
Results update as you type.
How it works
A network latency calculator estimates the propagation delay, the time a signal takes to travel a given distance through a transmission medium such as fibre-optic cable, copper, or open air. This is the floor on latency set by physics: no amount of bandwidth or optimisation can beat the speed at which a signal physically crosses the distance, which is why geography fundamentally limits how fast two points can communicate. Understanding this delay matters for anyone designing distributed systems, choosing data-centre locations, or troubleshooting slow connections. It explains why a server across the world always feels less responsive than one nearby, why content delivery networks place servers close to users, and why real-time applications like gaming and video calls are so sensitive to distance. Separating the physics-imposed minimum from other delays helps you know when latency can be improved and when it cannot. The calculation works because signals in cable travel slower than light in a vacuum by a factor related to the material's refractive index, roughly 1.47 for fibre and about 1.5 for copper. Dividing the vacuum speed of light by that factor gives the effective speed, and distance divided by effective speed gives the one-way time, doubled for the round trip. Real latency adds routing, switching, queuing, and processing delays on top, so this is the theoretical best case. Network architects and engineers use a latency calculator to reason about the geographic limits of performance.
one-way (ms) = distance ÷ (speed of light ÷ medium factor) × 1000
Light travels at about 299,792 kilometres per second in a vacuum, but slows in a physical medium by a factor tied to its refractive index, so the effective speed is the vacuum speed divided by that factor. Distance divided by this effective speed gives the one-way time in seconds, multiplied by 1,000 for milliseconds. Round-trip time doubles it, since a signal must travel there and back. The method captures the unavoidable delay set by physics alone.
Source:Speed of light and refractive index (physics)
We review all our tools from time to time to ensure accuracy.
Worked example
How to use this calculator
- 1
Enter your values
Enter distance and transmission medium.
- 2
Adjust the options
Fine-tune any options to match your situation.
- 3
Read your result
One-way latency updates instantly as you type — no button to press.
Frequently asked questions
Why is latency higher than the speed of light suggests?
Signals in fibre or copper travel slower than light in a vacuum, typically around two-thirds the vacuum speed, because the medium's refractive index slows them. On top of that physics floor, real networks add delays from routers switching packets, queues under load, and processing at each hop, plus the fact that cables rarely follow the shortest straight-line path. This calculator estimates only the propagation floor, so measured ping is always somewhat higher.
What is the difference between one-way and round-trip time?
One-way latency is the time for a signal to travel from source to destination. Round-trip time, or RTT, is the time for it to go there and come back, which is what tools like ping measure. RTT is roughly double the one-way delay for a symmetric path. Many interactive applications care about RTT because a request and its response must both complete before the user sees a result.
Which medium factor should I choose?
Use fibre optic, about 1.47, for modern long-haul and internet backbone links, which are overwhelmingly fibre. Choose copper, about 1.5, for older wired connections like traditional Ethernet over twisted pair. Select vacuum or radio, 1.0, for line-of-sight wireless, satellite, or free-space signals that travel at essentially the full speed of light. The factor reflects how much the medium slows the signal relative to light in a vacuum.
How does distance affect application performance?
Because propagation delay scales linearly with distance, faraway servers add unavoidable latency to every interaction. This is why a video call or online game with a distant server feels laggy, and why content delivery networks cache data near users. For chatty protocols that require many round trips, distance compounds, since each exchange pays the delay again. Placing services close to users is often the single most effective latency improvement available.
Can I reduce propagation latency?
You cannot beat the physics for a given distance and medium, but you can shorten the effective distance or improve the path. Moving servers closer to users, using content delivery networks and edge computing, and choosing more direct network routes all cut propagation delay. Reducing the number of round trips an application needs also helps, since fewer exchanges mean the distance penalty is paid fewer times. The medium itself offers little room, as fibre is already near optimal.