Using ping to Test Connectivity

What ping Does

ping is one of the simplest and most widely used network troubleshooting tools - it sends a small ICMP echo request to a target address and waits for an echo reply, confirming whether that target is reachable at all and roughly how long the round trip takes.

$ ping example.com

Reply from 93.184.216.34: bytes=32 time=14ms
Reply from 93.184.216.34: bytes=32 time=15ms
Reply from 93.184.216.34: bytes=32 time=13ms

What a Successful Ping Actually Confirms

  • The target device is powered on and reachable over the network.
  • Basic connectivity exists along the path between you and the target.
  • The approximate round-trip time (latency) to reach it.

What a Failed Ping Could Mean

A ping failure doesn't always mean the target is truly down - it might have a firewall specifically configured to block ICMP traffic (a common, deliberate security practice), while still being perfectly reachable for actual web or application traffic on a different protocol.

What Ping Cannot Tell You

Ping only confirms basic reachability - it says nothing about whether a specific application or service (like a website's HTTP server) is actually running and working correctly on that device. A server can respond to ping perfectly while its web server software is completely broken.

Why Ping Is Usually the First Troubleshooting Step

Because it's quick and simple, ping is typically the very first tool reached for when diagnosing "I can't connect to X" - confirming basic reachability before investigating anything more specific or complicated, like the actual path traffic takes (covered in the next note, on traceroute).

Written by Lorens Mishra

Software Engineer Notes Management System Administrator

Discussion

0 comments
Sign in to join the discussion.

No comments yet. Be the first to say something.