📶 Ping / Latency Calculator

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 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 on the same distance.

How It Works

For fiber optic connections, the calculator uses the standard networking approximation that light travels through glass fiber at about 200,000 km/s — roughly two-thirds of its vacuum speed, because glass has a refractive index of about 1.5. One-way propagation delay is simply distance ÷ 200,000 km/s, and round-trip ping doubles that. Because real routers, switches, and non-straight-line cable routes add delay beyond this theoretical minimum, the calculator multiplies the result by an adjustable routing overhead multiplier (default 1.6×). Geostationary satellite latency is modeled as a fixed ~476 ms one-way delay regardless of ground distance, since every signal must travel up to roughly 35,786 km altitude and back down. LEO/Starlink latency uses a much smaller fixed baseline plus a small distance-dependent factor, reflecting its much lower orbital altitude. Mobile 4G/5G latency takes the fiber-backbone estimate and adds extra delay for the local tower and radio-access-network hop.

Why It Matters

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 of roughly 108 ms 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."

Tips for Accurate Results

• Use a higher routing overhead multiplier (1.8×–2.2×) for connections that cross many network hops or international peering points, and a lower one (1.3×–1.5×) for well-optimized, direct backbone routes.
• Remember that geostationary satellite latency does not improve with a closer ground distance — the ~35,786 km trip to the satellite dominates regardless of how close the two ground stations are to each other.
• For a rough real-world sanity check, compare this estimate to an actual ping or traceroute result to the same destination — a large gap usually points to inefficient routing or a congested hop somewhere in the path.
• When entering a custom distance, use the great-circle (straight-line) distance between two points rather than driving distance, since that is what fiber routes most closely approximate.
• Mobile 4G/5G latency is highly variable in practice depending on signal strength and network load — treat the 20-50 ms overhead range as a typical baseline, not a guarantee.