Ping is the oldest trick in network troubleshooting, and it's still one of the most useful. It answers a single question — is this host reachable, and how long does a round trip take?— but that question turns out to be the first thing worth checking whenever something feels slow or unreachable.
What a ping actually does
A ping sends an ICMP echo request packet to a target IP address and waits for an echo reply. There's no application logic involved — no HTTP, no TLS handshake, no database query. It's about as close to “is there a wire between here and there” as you can get, which is exactly what makes it useful for isolating problems. If a ping fails but a website loads fine in a browser, that's a real (if slightly odd) signal: ICMP is probably being blocked by a firewall while the actual web service is healthy.
Reading the output
Each reply line carries three numbers worth paying attention to:
- bytes — the size of the echo packet, almost always 32 or 64 bytes and rarely interesting on its own.
- time — the round-trip time in milliseconds: how long it took the packet to reach the host and the reply to come back. This is your latency number.
- TTL (time to live) — decremented by one at every router hop; a TTL that's unexpectedly low can hint at how many hops away a server is, or that something is intercepting the packet closer than expected.
At the end, the summary block reports packets sent vs. received, loss percentage, and the minimum, maximum, and average round-trip time across the whole run.
What counts as “good” latency
There's no universal threshold, but as a rough guide for a well-routed connection:
- Under 20ms — same region or a well-peered CDN edge. Feels instant.
- 20–80ms — normal for cross-country or well-routed international traffic. Fine for browsing, video calls, most gaming.
- 80–150ms — noticeable in real-time applications (fast-paced games, voice calls) but still fine for web browsing.
- 150ms+ — either a long physical distance (satellite links, far-flung intercontinental routes) or a routing problem worth investigating.
What matters more than the absolute number is consistency. A steady 60ms is a healthy connection. A ping that swings between 20ms and 300ms — high jitter — is often more disruptive than a consistently higher number, because it's unpredictable: it's what makes video calls stutter and games feel laggy even when average latency looks fine.
Packet loss
0% loss is normal and expected on a healthy connection. Occasional single-digit loss (1–2%) can happen on congested Wi-Fi or mobile networks without indicating a real problem. Sustained loss above roughly 5% is worth investigating — it causes retransmissions, stalls streaming, and is a common cause of choppy voice/video calls even when raw bandwidth looks fine.
Why a ping can time out even when a site works fine
Many servers, load balancers, and cloud firewalls deliberately drop or rate-limit ICMP traffic as a basic security measure, while leaving the actual web service (port 80/443) completely open. A failed or inconsistent ping against a site that otherwise loads normally almost always means “ICMP is filtered here,” not “the site is down.” If you need to confirm real availability, pairing a ping with a port check on the actual service port gives a fuller picture.
When to reach for a ping test
- A site or service feels slow and you want to rule network latency in or out before digging into application-level causes.
- You've just changed DNS or routing and want to confirm a host is reachable from outside your own network.
- You're debugging a flaky video call or game and want a rough read on jitter and loss, not just “my Wi-Fi feels bad.”
- You want a second opinion on reachability from a different vantage point than your own machine — our ping test runs from our server, not your browser.
Ready to try it? Head to the ping test and point it at any hostname or IP address.