When you experience slow loading times, intermittent outages, or complete inability to reach a website or server, two of the most useful diagnostic tools are traceroute and ping. These tools help you determine whether a host is reachable and where potential network issues occur along the path.
What These Tools Do
-
Ping: Tests if a remote host is available and measures round-trip time.
-
Traceroute (or tracert on Windows): Shows the path packets take from your computer to the destination, listing each “hop” along the way.
Running a Ping Test
On Windows
-
Open the Command Prompt (Start → Run → type
cmd). -
Type:
Bash ping example.comReview the output:-
Successful replies show response times in milliseconds.
-
Packet loss or no replies may indicate connectivity issues.
-
On macOS / Linux
-
Open Terminal.
-
Type:
Bash ping example.com -
Stop the test with Ctrl + C.
-
Review the statistics (packet loss, average latency).
| Note: Some servers block ping requests for security reasons. A failed ping doesn’t always mean the server is down. |
Running a Traceroute
On Windows
-
Open Command Prompt.
-
Type:
Bash tracert example.com -
Each line shows a “hop” (router or server) along the path, with response times.
-
Look for unusually high latency or timeouts (
* * *) to spot issues.
-
On macOS / Linux
-
Open Terminal.
-
Type:
Bash tracert example.comReview the hops and timings.
Using MTR (Advanced)
-
MTR (My Traceroute) combines ping and traceroute into a continuous test.
-
On Windows, use WinMTR; on Linux, install mtr.
-
It provides real-time monitoring of packet loss and latency across all hops.
