Traveling Through a Network - Did You Know?

     Are you familiar with how data travels through a network?  I wasn't until recently, and I want to share what I learned. I like to use analogies as apart of my learning style. As I went through this amazing learning process of ping and traceroute – these are very similar to how a GPS and driving direction work. 

Ping to Goggle.com

    When pinging a domain, it is looking for the correct and fastest route. While a traceroute is providing the step by step turns and detailed directions of how the information is traveling from point A to point B.  As I compare the results of the three ping commands, overall they performed and provided echo replies in a similar manner. Each ping sent 4 packets and received 4 packets back, with 0% loss. I found it interesting that the ping roundtrip times to italia.it took less time (10ms) while the ping to amazon.ca took way longer at 54ms.  A few things I considered are Google and Amazon have high traffic in common, while the website italia.it is for people wanting to gain information about traveling to Italy. The traffic on Italia.it website should be significantly less.  With less website traffic, the communication can move faster between the computers and internet files which can minimize the number of hops needed, as well has reduce the command time outs on the or packets loss on the traceroute.

Traceroute Google.com

       Once I ran the traceroute (imaged above), I was able to understand why the ping roundtrip to italia.it was much shorter. In reading the traceroute, I noticed for google.com and amazon.ca it took over 20 routers with several timing out for it to be completed. While the routers traveled for italia.it completed at 7 routers, and no time outs.   This exercise was enlightening and gave me a better understanding of how I use my system daily. If a user is having an issue with website connectivity, it can be traced or identified easily with the traceroute.  If an error is received, or the trace is not complete, you can review where the route has a problem based on the router IP address.  This can help identify if it is your home router, or the ISP router, etc. 

In the comments, share if this information is helpful in how you understand what's happening on the back end of when you are using your computers on a daily basis.