Ping & Round-Trip Latency Calculator

Ping & Round-Trip Latency Calculator

Growing AI Skill PRO

Enter Calculation

Formula

RTTmin⁡(ms)=2×dvwhere{d=Distance (km)v=299.792458×Velocity Factor(km/ms)One-way=dv\begin{gathered} \text{RTT}_{\min}\ (\text{ms}) = 2 \times \frac{d}{v} \\[1.5em] \text{where}\quad \left\{ \begin{aligned} d &= \text{Distance (km)} \\ v &= 299.792458 \times \text{Velocity Factor} \ \left(\text{km/ms}\right) \\ \text{One-way} &= \frac{d}{v} \end{aligned} \right. \end{gathered}
Usage stats

Advertisement

Results

Minimum Round-Trip Latency (Ping)
9.96
milliseconds (theoretical floor)
One-way travel time 4.98 ms
Effective signal speed 200.86 km/ms

Report an error on this page

What is the Ping & Round-Trip Latency Calculator?

This tool estimates the theoretical minimum ping — the smallest possible round-trip latency — between two locations based purely on the speed of light and the distance a signal must travel. Real-world ping is always higher because of routing detours, switching, queuing, and processing delays, but this physics-based floor tells you the best latency you could ever achieve over a direct link.

How to use it

Enter the one-way distance in kilometers between the two endpoints (the straight-line or cable distance). Then set the velocity factor — the fraction of the speed of light at which your signal travels. Use about 0.67 for fiber-optic cable, and 1.0 for radio/microwave in free space (e.g. satellite or line-of-sight wireless). The calculator returns the minimum possible round-trip time in milliseconds.

The formula explained

Light travels at \(c = 299{,}792.458 \text{ km/s}\), which is \(299.792458 \text{ km/ms}\). In a medium, the effective speed is \(c \times \text{velocity factor}\). The one-way time is distance divided by that effective speed, and ping is the round trip, so we multiply by 2:

$$\text{Latency}_{ms} = \frac{\text{distance}_{km}}{(299.792458 \times vf)} \times 2$$

Advertisement
Diagram showing a signal traveling from point A to point B and back through a fiber line over a distance d
Round-trip latency: the signal travels the distance twice, there and back.

Worked example

For two cities 1,000 km apart over fiber (vf = 0.67): effective speed = \(299.792458 \times 0.67 \approx 200.86 \text{ km/ms}\). One-way time = \(1000 / 200.86 \approx 4.978 \text{ ms}\). Round-trip ping $$\approx 9.96 \text{ ms}$$ So even a perfect cable can't beat ~10 ms of ping at that distance.

Bar comparison of signal speed in vacuum versus fiber optic cable
Light in fiber travels at about 0.67c, slower than in a vacuum.

Velocity Factors by Transmission Medium

The velocity factor (VF) is the fraction of the speed of light in vacuum (c = 299.792458 km/ms) at which a signal travels through a medium. The effective speed is \(v = 299.792458 \times \text{VF}\) km/ms. The values below are typical; actual products vary by manufacturer and construction.

Medium Typical velocity factor Effective speed (km/ms)
Vacuum / free-space radio 1.0 299.79
Air (radio or free-space optics) ~0.99–1.0 ~296.8–299.8
Standard single-mode fiber ~0.67 (refractive index ~1.468) ~200.9 at 0.67; ~204 using n = 1.468
Copper twisted pair (Cat5e/Cat6) ~0.64–0.70 ~191.9–209.9
Coaxial cable ~0.66–0.85 ~197.9–254.8
Hollow-core fiber ~0.99 ~296.8

Example: for fiber at VF 0.67, \(v = 299.792458 \times 0.67 \approx 200.86\) km/ms, so light covers about 200 km each millisecond, or roughly 5 µs per kilometer one way.

Minimum Ping for Common Routes

These figures are straight-line physics floors, using \(\text{RTT}_{\min} = 2d / v\) with fiber at VF 0.67 (v ≈ 200.86 km/ms). Real cables rarely follow a great-circle path, so actual latency is higher.

Route / distance Medium Calculation Minimum RTT
100 km (regional) Fiber, VF 0.67 \(2 \times 100 / 200.86\) ~1.0 ms
1,000 km Fiber, VF 0.67 \(2 \times 1000 / 200.86\) ~10 ms
5,600 km (New York–London, approx.) Fiber, VF 0.67 \(2 \times 5600 / 200.86\) ~56 ms
10,000 km Fiber, VF 0.67 \(2 \times 10000 / 200.86\) ~100 ms
20,000 km (near antipodal) Fiber, VF 0.67 \(2 \times 20000 / 200.86\) ~199 ms (about 200 ms)
Geostationary satellite (~35,786 km altitude) Radio, VF 1.0 \(2 \times 35786 / 299.79\) ~239 ms for the path up to the satellite and back down; ~477 ms for a full request-and-reply ping (four legs, \(4 \times 35786 / 299.79\))
LEO satellite (~550 km altitude) Radio, VF 1.0 \(2 \times 550 / 299.79\) ~3.7 ms for the up-and-down hop

Satellite figures assume the satellite is directly overhead and cover only the space segment. A real satellite connection also adds the ground-station links and terrestrial network, and the slant range is longer when the satellite is not overhead.

Advertisement

Interpreting Your Result

The result is a lower bound, not a prediction. It assumes a perfectly straight path at the chosen velocity factor and nothing else. Real-world ping is typically about 1.5–3 times higher because of:

  • indirect cable routes and routing detours that make the path longer than the straight-line distance;
  • per-hop delays at routers and switches (processing, serialization, queuing);
  • congestion, wireless access links (Wi-Fi, cellular), and server processing time.

Example: a 56 ms floor for a New York–London-type route would commonly show up as roughly 85–170 ms in a measured ping. Well-optimized submarine routes can come closer to the floor than that range implies.

Rough latency tiers for applications

Measured ping General experience
Under 20 ms Excellent for online gaming
20–50 ms Good
50–100 ms Playable for most games, though it may be noticeable in fast-paced ones
Over 150 ms Noticeable lag in real-time applications

These tiers are rules of thumb and vary by application. For voice, ITU-T Recommendation G.114 advises keeping one-way delay under about 150 ms for most user applications.

Caveats

  • This calculator excludes per-hop and processing delays; it models only propagation through the medium.
  • Ping reports round-trip time, while many published targets (such as G.114) are one-way. Divide RTT by roughly 2 to compare, assuming a symmetric path.
  • If your measured ping is close to the calculated floor, there is little room for improvement from routing; if it is far above, the cause is likely route length, congestion, or the local access network.

FAQ

Why is my real ping much higher? Actual networks add hops, congestion, and processing; this is only the light-speed floor.

What velocity factor should I use? ~0.67 for typical fiber, ~0.65–0.70 for copper, and 1.0 for vacuum/free-space radio.

Should I use straight-line distance? Cables rarely run straight; using the real route length gives a more realistic estimate.

Last updated:

Most popular in Digital Life

View all Digital Life calculators