How to use ping and traceroute commands

Network connectivity issues can be frustrating and time-consuming to diagnose without the right tools. In particular, two essential commands – ping and traceroute – provide powerful diagnostic capabilities that every website owner, developer, and system administrator should master. Furthermore, these tools work across all major operating systems including Linux, Windows, and Mac OS X, making them universally valuable for troubleshooting connection problems, measuring network performance, and identifying exactly where connectivity issues occur.

What is the ping command and how does it work

The ping command stands for “Packet Internet Groper” and is a fundamental network diagnostic utility that tests the reachability of a host on an IP network. Essentially, it works by sending ICMP (Internet Control Message Protocol) echo request packets to the target host and waiting for an echo reply. When the remote server receives these packets, it responds with an echo message, providing valuable information about connection quality, response time, and packet loss.

Moreover, ping helps you answer critical questions: Is the server online? How fast is the connection? Are packets being lost during transmission? Consequently, these insights are invaluable for troubleshooting network issues and monitoring your hosting environment performance.

What is the traceroute command and why use it

While ping tells you if a server is reachable, traceroute shows you the exact path your data takes to reach its destination. Specifically, the traceroute command displays every router (hop) that packets pass through from your computer to the target server, along with the time each hop takes. Additionally, it identifies where connections fail or slow down, making it an essential companion to the ping command.

In practice, traceroute helps you determine whether connection issues originate from your ISP, an intermediate network, or the destination server itself. Therefore, this granular visibility is crucial for effective troubleshooting.

Using ping command on Linux

Fortunately, Linux provides a robust implementation of the ping command with extensive options for network diagnostics.

Basic ping syntax:

ping google.com
ping 8.8.8.8

In general, by default, Linux ping runs continuously until you stop it manually by pressing Ctrl+C.

Limiting the number of ping requests with -c:

ping -c 5 google.com

As a result, this sends exactly 5 packets and then stops automatically, displaying a summary of the results.

Setting the TTL (Time To Live) with -t:

ping -t 60 google.com

Consequently, this determines how many network hops a packet can traverse before being discarded.

Understanding the output:

Bytes received: Size of the data packet (typically 64 bytes)
IP address: The resolved IP address of the domain
Sequence number: Counter that increments with each packet (icmp_seq=1, 2, 3…)
TTL: Maximum number of hops before packet expiration
Response time: Round-trip time in milliseconds (time=3.04 ms)

Practical example:

ping -c 10 yourdomain.com

In this case, the command quickly tests your website’s availability with 10 packets.

Using ping command on Windows

Similarly, Windows also includes a built-in ping command, though with slightly different behavior and options.

Accessing the command prompt:

Go to Start → Programs → Accessories → Command Prompt
Or press Windows key + R, type cmd, and press Enter
Alternatively, search for “cmd” or “Command Prompt” in the Start menu

Basic Windows ping syntax:

ping webhostface.com
ping 8.8.8.8

In contrast, unlike Linux, Windows ping automatically stops after sending 4 packets by default.

Continuous ping in Windows:

ping -t google.com

Notably, the -t flag makes ping run continuously (similar to Linux default behavior). Press Ctrl+C to stop.

Specifying packet count:

ping -n 10 yourdomain.com

In particular, the -n option sets the number of echo requests to send (equivalent to -c on Linux).

What the results tell you:

Once completed, after running ping, Windows displays whether your computer can successfully connect to the target domain or IP address, along with response times and packet loss statistics.

Using ping command on Mac OS X

Alternatively, Mac OS X offers two methods for running ping tests: through Terminal (command line) or using the built-in Network Utility application.

Method 1: Using Terminal (recommended):

Open Terminal from Applications → Utilities
Or press Command + Space and type “Terminal”

ping google.com
ping -c 5 yourdomain.com

Essentially, Mac Terminal ping works identically to Linux, with the same options and behavior.

Method 2: Using Network Utility (GUI):

Go to your Applications folder
Choose Utilities and open Network Utility
Click the Ping tab
Enter the domain or IP address you want to check
Specify the number of pings (default is 10)
Click the Ping button to launch the test

As a result, the Network Utility provides a user-friendly interface for those who prefer graphical tools over command-line operations.

Using traceroute command on Linux

For this reason, when ping shows connectivity issues, traceroute helps pinpoint exactly where the problem occurs along the network path.

Basic traceroute syntax:

traceroute google.com
traceroute yourdomain.com

Essentially, traceroute displays each router hop from your computer to the destination, showing:

Hop number (sequential router count)
Router hostname and IP address
Three round-trip time measurements for each hop

Example output interpretation:

 1  192.168.1.1 (192.168.1.1)  1.234 ms  1.123 ms  1.098 ms
 2  10.0.0.1 (10.0.0.1)  5.432 ms  5.234 ms  5.198 ms
 3  * * *
 4  172.16.0.1 (172.16.0.1)  45.678 ms  45.543 ms  45.432 ms

Importantly, the asterisks (* * *) indicate that hop timed out or doesn’t respond to traceroute requests, which is common for routers configured to ignore these packets for security reasons.

Using traceroute command on Windows

On Windows systems, the operating system uses a slightly different command name: tracert instead of traceroute.

Accessing Command Prompt:

Select Start → Programs → Accessories → Command Prompt
Or type cmd in the Search programs and files field
Select cmd.exe from the results

Running tracert:

tracert google.com
tracert yourdomain.com

Notably, the output shows you the complete path to reach a website and identifies what might be slowing down your connection. Additionally, it reveals where connections fail, making troubleshooting much more efficient.

Common tracert issues:

“Request timed out”: Router doesn’t respond (normal for security-hardened routers)
High latency at specific hop: Indicates congestion or issues at that router
Connection fails at specific hop: Problem occurs at or after that point

Using traceroute command on Mac OS X

Conveniently, Mac OS X provides both command-line and graphical options for running traceroute, similar to its ping implementation.

Method 1: Using Terminal (command line):

traceroute google.com
traceroute yourdomain.com

Similarly, this works identically to Linux traceroute with the same output format and options.

Method 2: Using Network Utility (GUI):

Launch Network Utility by opening Spotlight (Command + Space)
Type “Network Utility” and click the Top Hit
Alternatively: Double-click Hard Drive → Applications → Utilities → Network Utility
Click the Traceroute tab
Enter the domain name you want to trace
Click Trace to begin

Overall, the Network Utility provides a clean, easy-to-read interface for viewing the route your packets take to reach their destination.

Interpreting ping and traceroute results

Clearly, understanding what the results mean is crucial for effective troubleshooting.

Good ping indicators:

Response time under 50ms for local servers
Response under 100ms for regional servers
Latency under 200ms for international servers
0% packet loss
Consistent response times with minimal variation

Warning signs in ping results:

High response times (>200ms): Network congestion or routing issues
Packet loss: Network instability or congestion
Request timeout: Server down, firewall blocking, or network path broken
Destination host unreachable: No route to the target exists
Varying response times: Network congestion or unstable connection

Traceroute troubleshooting:

High latency at early hops: Problem with your ISP or local network
Delays at middle hops: Internet backbone or routing issues
Slow response at final hops: Problem at or near the destination server
Timeouts throughout: May indicate firewalls blocking traceroute (not necessarily a problem)
Complete failure at specific hop: Routing issue at that point in the network

Common troubleshooting scenarios

In practice, here are typical situations where these commands prove invaluable:

Scenario 1: Website is slow to load

First, run ping to check response times and packet loss
Then, run traceroute to identify where delays occur
Finally, compare results from different locations if possible

Situation 2: Cannot connect to server

Initially, test with ping to verify server is reachable
Subsequently, try pinging by IP address to rule out DNS issues
Lastly, use traceroute to see where connection fails

Case 3: Intermittent connectivity

Initially, run extended ping test (100+ packets) to identify packet loss patterns
Additionally, monitor traceroute over time to identify unstable hops
Furthermore, check if issues occur at specific times (network congestion)

Example 4: DNS problems

First, ping by domain name fails but pinging IP address works
Obviously, this indicates DNS resolution issues
Next, check your DNS settings or try alternate DNS servers (8.8.8.8)

Using online ping and traceroute tools

On the other hand, while command-line tools are powerful, online services like Pingdom and similar tools offer additional benefits:

Test from multiple global locations simultaneously
Verify if issues are local to your network or worldwide
Historical monitoring and uptime tracking
Email alerts when problems are detected
Graphical visualization of results

However, these tools complement rather than replace command-line diagnostics, which provide more control and immediate results.

Best practices for network diagnostics

Therefore, to effectively troubleshoot network issues, follow these best practices:

Start with ping to quickly verify basic connectivity
Use traceroute when ping reveals problems to identify the exact location
Test multiple targets (google.com, your server, other sites) to isolate issues
Document baseline metrics during normal operation for comparison
Consider time zones and geography when interpreting latency
Be aware of firewalls that may block ICMP packets causing false negatives
Run tests multiple times to identify patterns versus one-time anomalies
Combine with other tools like nslookup for comprehensive diagnostics

Pro tips:

Save results to files for later analysis: ping -c 100 yourdomain.com > ping-results.txt
Compare morning versus evening results to identify congestion patterns
Test from different devices to rule out local network card issues
Contact your hosting provider if traceroute shows issues near their network

New hosting plan with 80% OFF

Ready to put your network diagnostic skills to work? Upgrade to a reliable hosting plan that delivers consistent performance and low latency worldwide. Additionally, enjoy a huge 80% discount with exceptional uptime, free SSH access for advanced diagnostics, and expert support available 24/7. Furthermore, our hosting infrastructure is optimized for minimal latency and maximum reliability, ensuring your website remains fast and accessible to visitors globally. Perfect for businesses, developers, or anyone who demands professional-grade hosting performance.

Need more help?

Mastering ping and traceroute commands is essential for anyone managing websites or servers. Whether you’re troubleshooting connectivity issues, monitoring network performance, diagnosing slow loading times, or identifying routing problems, these two commands provide the diagnostic power you need across all major operating systems. By following the examples and best practices outlined in this tutorial, you’ll be able to quickly identify and resolve network issues, communicate effectively with technical support teams, and maintain optimal performance for your hosting environment.

Remember that effective network diagnostics often requires using both tools together – ping for quick connectivity checks and traceroute for detailed path analysis. Nevertheless, with practice and experience, you’ll develop intuition for interpreting results and resolving issues efficiently, making you a more capable website administrator or developer.

Discover more network diagnostic tutorials and server management guides in our knowledgebase. Master network troubleshooting on a reliable hosting account with 80% OFF the regular price now!