How to Use the Ping Command to Diagnose Network Problems

Ping is usually the first tool worth reaching for when something on a network isn't working — a slow site, a dropped connection, a server that seems unreachable. It sends a small packet to a target and waits for a response, telling you within seconds whether the target is reachable at all, and how long the round trip takes.

A Bit of History

Ping was written in a single night in December 1983 by Mike Muuss at the U.S. Army's Ballistic Research Laboratory, inspired by a comment from Dr. Dave Mills at a DARPA meeting about using ICMP Echo packets to measure network latency. Despite the common belief that "PING" stands for "Packet InterNet Groper," Muuss himself said the name was simply a reference to sonar — sending a pulse and listening for the echo.

How It Works

Ping uses the Internet Control Message Protocol (ICMP). Your device sends an ICMP "Echo Request" packet to the target; if it's reachable and configured to respond, it sends back an "Echo Reply" with the same sequence number. The time between sending and receiving is the round-trip time (RTT).

The ICMP packet types differ slightly between IPv4 and IPv6:

Basic Usage

On Windows (Command Prompt):

ping google.com

On Linux/macOS (Terminal):

ping google.com

You can also target an IP address directly, e.g. ping 8.8.8.8 (Google's public DNS).

Reading the Output

• Reply from [IP]: the address that responded
• Bytes=[size]: packet size, typically 32 bytes by default
• Time=[ms]: the round-trip time — lower is better
• TTL=[value]: Time To Live — the number of hops the packet can still pass through before being discarded, which roughly indicates how many routers it traveled through

At the end of a ping run, you get a summary: packets sent, packets received, percentage lost, and min/max/average RTT. Any packet loss above zero is worth investigating — it means data isn't reliably reaching its destination.

Useful Options

Examples

ping -c 5 8.8.8.8       # Linux/macOS: send 5 packets
ping -n 5 8.8.8.8        # Windows: send 5 packets
ping -l 1500 example.com # test with a larger packet size
ping -t 192.168.1.1      # continuously ping your router

What Ping Is Good For

• Basic connectivity checks: if ping fails entirely, you have a fundamental connection problem.
• Measuring latency: high RTT explains lag in gaming, video calls, or anything real-time.
• Spotting packet loss: the cause of choppy calls, buffering, and sluggish apps.
• Narrowing down DNS issues: if pinging an IP works but pinging the domain name fails, the problem is likely DNS resolution, not connectivity itself.

What Ping Can't Tell You

• It's not a bandwidth test. Ping measures latency, not speed — use a dedicated speed test for that.
• Firewalls can block it. A failed ping doesn't always mean a device is offline; ICMP is commonly blocked for security reasons.
• It tells you "if," not "why." For the actual path a packet takes and where a slowdown occurs, pair ping with traceroute.

Security Considerations

Ping's simplicity also makes it a building block for a few well-known attack patterns worth knowing about, mostly to understand why certain defenses exist:

• Ping flood: overwhelming a target with more Echo Requests than it can handle — a basic denial-of-service pattern, mitigated by firewall ICMP rate-limiting.
• Ping sweep: pinging a whole range of addresses to find which devices are active on a network, often a reconnaissance step before a more targeted attack — mitigated by disabling ICMP responses on hosts that don't need them.
• Ping of death: an old attack using malformed, oversized ICMP packets to crash outdated systems. Modern operating systems have long since patched this, but it's a good reminder of why keeping systems updated matters.