Network Travel

 

    When pinging the different sites, the path to google.com in the U.S.; to Yahoo.com in Japan; and to Amazon.com in Egypt they all show the same ping statistics. They all show the packets sent equaling four, received equaling four with zero percent loss for each site. This means that each site when pinged is showing successfully. The difference in each site’s test is seen in the round-trip times for each. The roundtrip times or RTT in these ping commands show the time it took for the data packet to be sent to the different destinations plus the time it took for an acknowledgment of those packets being received. All three sites pinged show different millisecond times:

• US Google showed 9ms minimum and maximum and average times.
• Yahoo in Japan showed 183ms minimum and 193 maximum and 190ms average times.
• Amazon in Egypt showed 102ms minimum; 104ms maximum and 102ms average times.

    These differences in millisecond times show that the U.S. ping results show that access to the server and site address is operating at optimum performance pinging under 100milliseconds. Japan’s site and Egypt’s site show that the addresses can be reached but their performance would likely be affected during navigation of the site. The high millisecond results could be caused by packet losses, high network usage from other devices or actual hardware problems with the modem, router or even the server.

    The traceroutes for each site yield the same results as the ping results. For the international sites you can see where each site shows a drop in its connections while traveling through the different servers. The asterisk shows the times when the route was interrupted or not responding timing out to the server. One possible reason this is happening is that some routers don’t allow for traceroute requests. Another reason could be the network is congested not allowing for route activity. Both the ping and traceroute commands can be used to troubleshot internet connection. One way you can test internet issues is by using wireless verse wired connections and running a ping command on both. The one that shows quicker millisecond times is the fastest route to get to the site. Using trace routes can show the different hops between the computers and show a different path that may be the cause of slower traffic on the site. It can also point to the device that is causing the network issue.