Pings and Trace Routes

Comparison on google.com

When pinging google 4 packets were sent and received with 0% loss.

When completing the trace on google I experienced 1 time out.  Trace was completed and the trace showed how the information traveled from my home location to Cincinnati Road Runner clear through to google.  The travel had a total of 21 hops with one of those failing.  My hopes traveled through 3 cities that I can tell Cincinnati, Chicago, and New York.

After google.com I pinged google.au.  Again, 4 packets were sent and received with no issues.

The trace route for google.au was a bit different.  Below you can see that this trace only took 16 hops, none of which failed.  You can see the travel to the Midwest, then through tbone.rr, and ending up at akamaitechnologies.com.

The next site I pinged was ebay.com.au.  This again had 4 packets sent; however, all packets failed on this attempt.

When conducting the trace router on ebay.com.au the trace router started in the Midwest, passing through Chicago, then landed at ebay.com.  After landing at email all other hops timed out. The total hops on this trace router was 30.

For the traceroute, this identifies if a server can be reached and the timing it takes to reach the server.  This can be utilized for troubleshooting to ensure that you can connect to a specific server.  For the ping, you can check to see if you can connect to a specific server through your current network.