Ping Explained

Ping is the most fundamental and universally used command-line utility for testing network connectivity. It allows you to verify whether a specific IP address or domain name is reachable over the network and measures how long it takes for a message to travel to the destination and back.

The name "ping" comes from sonar technology used in submarines, where a sound pulse (a ping) is sent out, and the echo is measured to detect objects.

How Does Ping Work?

Ping operates at Layer 3 (Network Layer) of the OSI model. It relies on the Internet Control Message Protocol (ICMP). When you ping a destination, you are not establishing a TCP connection or opening a web page; you are simply sending raw network control packets.

The process works like this:

1. Echo Request: Your computer sends an ICMP Echo Request packet to the target IP address.
2. Echo Reply: If the target device is online, functioning, and not blocking ping requests, it immediately responds with an ICMP Echo Reply packet.

By timing how long it takes for the Reply to return, ping calculates the round-trip time (latency).

You can learn more about the underlying protocol in our ICMP Explained tutorial.

What Ping Proves (And What It Doesn't)

What Ping CAN Prove:

• Basic Reachability: A successful ping proves there is a valid routing path from your machine to the destination, and a valid return path back.
• DNS Resolution: If you ping google.com, the command output will first display the IP address it resolved. If the ping fails immediately saying "could not find host," you have a DNS issue, not a connectivity issue.
• Latency and Stability: It shows the time in milliseconds (ms). Consistent low times mean a healthy connection. Wildly fluctuating times or dropped packets indicate network congestion or physical layer problems.

What Ping CANNOT Prove:

• Application Health: A successful ping to a web server proves the server is online, but the actual web server software (like Apache or IIS) could be completely crashed. Ping only tests the network stack, not the application port (like Port 80 or 443).
• Security Filters: Many modern operating systems (including default Windows Firewalls) and perimeter firewalls block ICMP Echo Requests by default to prevent network discovery scanning. Therefore, a failed ping does not necessarily mean the server is offline; it might just be ignoring pings.

Understanding Ping Output

Here is an example of a successful ping on a Windows machine:

Key Metrics Explained:

• bytes=32: The size of the ICMP payload sent. Windows defaults to 32 bytes. Linux defaults to 56 bytes.
• time=14ms: The latency or round-trip time (RTT). Lower is better. Anything under 50ms is excellent for general internet use. Over 150ms will cause noticeable delay in voice/video calls.
• TTL=117: Time To Live. Every time the packet passes through a router, the TTL drops by 1. This prevents packets from looping infinitely if there is a routing error. If TTL reaches 0, the packet is discarded.

Common Ping Errors and Troubleshooting

1. Request Timed Out

This means the ICMP Echo Request was sent, but no Reply was received within the timeout period (usually 4 seconds).

Troubleshooting: The destination device might be turned off, physically disconnected, or the network route is broken. It is also highly likely a firewall is simply blocking ICMP traffic. Test with a different protocol (like opening the website in a browser) to confirm.

Read more in Packet Loss Troubleshooting.

2. Destination Host Unreachable

This message means your computer (or a router along the path) has no idea how to route the packet to the destination IP address. There is no matching entry in its routing table.

Troubleshooting: This is a local routing issue. Check if you have a valid IP address and Default Gateway. If trying to reach an internal subnet, check if the router has the correct static route or VPN tunnel established.

3. High Latency or Jitter

If the time fluctuates wildly (e.g., 20ms, 400ms, 15ms, 800ms), the network is experiencing congestion, Wi-Fi interference, or hardware failure.

Read more in Network Latency Troubleshooting.

Useful Ping Commands

Windows

• ping 8.8.8.8 -t : Ping continuously until you press Ctrl+C (great for monitoring while rebooting a router).
• ping 8.8.8.8 -n 10 : Send exactly 10 ping requests instead of the default 4.

Linux / macOS

• ping 8.8.8.8 : Linux pings continuously by default. Press Ctrl+C to stop.
• ping 8.8.8.8 -c 4 : Limit the ping to 4 counts (similar to Windows default behavior).

Quick Summary

• Ping tests basic network reachability using ICMP Echo Requests and Replies.
• It measures network latency (time in milliseconds) and packet loss.
• A successful ping proves network routing is intact, but a failed ping does not guarantee a server is offline (firewalls often block ping).
• Use Traceroute if a ping fails, to see exactly where the connection breaks.