Estimate theoretical round-trip network latency from physical distance and connection medium — fiber optic, geostationary satellite, LEO/Starlink, or mobile 4G/5G. Not a live ping — a physics-based estimate.
Select a distance and connection type to estimate latency
Network latency — the delay between sending a packet and receiving a response — is fundamentally limited by the speed of light through the physical medium a signal travels over, plus whatever processing and routing overhead the network path adds along the way. This ping calculator estimates that theoretical latency for a given distance and connection medium: terrestrial or submarine fiber optic cable, a geostationary satellite link, a Low Earth Orbit (LEO) constellation like Starlink, or a mobile 4G/5G connection, and compares round-trip ping across all four side by side.
It computes theoretical one-way and round-trip latency from physical distance and connection medium physics, applying an adjustable routing overhead multiplier to approximate real-world routing inefficiency beyond the pure speed-of-light minimum.
Network engineers planning server region placement, game server operators choosing datacenter locations, satellite internet customers understanding latency expectations, and students learning networking physics all need this distance-to-latency estimate.
Understanding the physical floor on latency helps set realistic expectations for anything sensitive to round-trip time — video calls, competitive online gaming, VoIP, real-time trading systems, or remote desktop sessions. No amount of bandwidth or server optimization can beat the speed of light: a New York-to-Tokyo round trip has a hard physical minimum well under 100ms even with a perfect, overhead-free fiber connection, and real-world ping will typically run higher once routing overhead is factored in. This lets you distinguish "my connection has unusually high latency" from "this destination is simply far away."
The physics this calculator uses for each connection type
200,000 km/s is light's effective speed in glass fiber (vacuum speed ÷ refractive index ~1.5) — the standard networking approximation for propagation delay.
The time a signal takes to physically travel through a medium — a hard latency floor set purely by distance, regardless of network optimization.
Geostationary satellites orbit at ~35,786 km, adding a fixed ~476 ms one-way delay. LEO constellations like Starlink orbit at only ~550 km, cutting that dramatically.
Real traffic passes through routers, switches, and firewalls, adding processing and queuing delay — typically 1.5× to 2× the straight-line estimate.
From picking a distance to comparing all 4 connection types
Select a preset city pair, or choose Custom distance to enter your own value in kilometers or miles.
Choose fiber optic, geostationary satellite, LEO satellite/Starlink, or mobile 4G/5G to match the connection medium you're estimating.
Fine-tune the multiplier (default 1.6×) that accounts for real-world routing inefficiency beyond the theoretical straight-line minimum.
The calculator applies the physics-based formula for your chosen connection type and distance.
Review one-way latency, round-trip ping, and how your result compares to the other three connection types at the same distance.
Using the calculator's own default scenario — New York to London, fiber, 1.6× overhead
Suppose you're estimating fiber latency between New York and London (5,570 km) at the default 1.6× routing overhead.
Explanation: Fiber's 89 ms round-trip ping for New York-London is well within the "usable" range for video calls and most online gaming, while geostationary satellite's fixed 952 ms round-trip would feel severely laggy for anything interactive — illustrating why satellite altitude matters far more than ground distance for that connection type.
What your estimated round-trip ping generally implies
| Round-Trip Ping | UX Implication | Recommended Next Step |
|---|---|---|
| Under 50 ms | Excellent — feels instantaneous | Great fit for competitive gaming, real-time trading |
| 50 – 100 ms | Good — smooth video calls and casual gaming | Suitable for most interactive applications |
| 100 – 200 ms | Noticeable but tolerable | Acceptable for browsing and streaming, not competitive gaming |
| 200 – 500 ms | Sluggish for real-time interaction | Consider a closer server region if latency-sensitive |
| Over 500 ms | Poor for anything interactive | Typical of geostationary satellite; fine for non-interactive data only |
If your estimate is much higher than a real ping test: lower the routing overhead multiplier, since your actual path may be more direct than the default assumes.
If your estimate is much lower than a real ping test: raise the overhead multiplier, or check for additional hops like VPNs, proxies, or congested peering points not modeled here.
This is a theoretical estimate, not a live measurement — always cross-check with an actual ping or traceroute for real-world decisions.
This calculator estimates theoretical latency using distance and physics, not live network measurement. Use a real ping/traceroute tool for actual current conditions.
Where estimating theoretical latency up front genuinely helps
Choose a datacenter region that minimizes latency for your target player base.
Estimate latency to users before choosing a cloud provider's region for deployment.
Understand what latency to expect from geostationary vs LEO satellite internet.
Diagnose whether call lag is likely distance-driven or a local network issue.
Estimate latency improvement from adding a CDN edge closer to users.
Understand the latency cost of geographic distance for latency-sensitive trading.
Check whether a remote desktop session over a given distance will feel responsive.
Use it in a networking course to make propagation delay and orbital altitude concrete.
Estimate inter-region latency when designing a globally distributed system.
Set realistic call quality expectations for international VoIP connections.
Determine whether high measured ping is expected given distance, or a red flag.
Re-estimate expected latency after switching server regions or ISPs.
What this ping calculator does well, and where it can't replace a live measurement
Round-trip ping at 5,570 km distance (New York–London), 1.6× overhead where applicable
| Connection Type | Round-Trip Ping | Distance-Dependent? | Best For |
|---|---|---|---|
| Fiber optic | 89.1 ms | Yes | Most general-purpose internet use |
| LEO satellite / Starlink | 41.1 ms | Slightly | Rural/remote areas without fiber access |
| Mobile 4G/5G | 124.1 ms | Yes (+ fixed overhead) | Mobile devices without fixed-line access |
| Geostationary satellite | 952 ms | No (fixed) | Areas with no other option; non-interactive data |
Summary: This ping calculator gives you an instant, free, physics-based estimate of network latency across fiber, satellite, and mobile connections, so you can set realistic expectations before choosing a server region or connection type. Pair it with the Bandwidth Calculator and DNS Propagation Estimator for a complete networking toolkit.
Common questions about ping and network latency
Official documentation to complement this calculator
Explore other tech tools