Ping Activity
(Websites Reviewed)
www.google.com
For the Google Website, the results were that a total of 4 packets were sent, 4 received, and zero packets lost.
Amazon.com.au
The next site that I pinged was the Australian amazon site. For this site the results were 4 packets sent, 4 packets received, and 0 packets lost. The round trip time for pinging this site was 61ms average.
Ifeng.com
Ifeng.com is a Chinese website that is one of the tope 20 most popular websites in China. The results of this ping were initially similar to the others with 4 packets sent, 4 received, and 0 packets lost. However, the amount time it took for the ping results was considerably longer with 203ms on average.
Traceroute Activity
I found both the ping and the traceroute commands to be quite interesting. Ping was interesting because it can be used to determine if a website is experiencing latency issue from internal or external sources. Traceroute provides more detail in explaining where the sources of latency issues might be. Both ping and traceroute showed similar results in terms of the ms time that each site experienced to make a round trip. I hypothesis that this is do to physical distance from the ping location to the destination and it takes a certain amount of time for the signal to make the round trip. I believe that traceroute commands can be used to troubleshoot internet issues because it can specify the actual location of latency or problem. This can help IT professionals to exclude their own hardware or software as being the potential cause. The ping command is similar because it can be used to identify if a specific site is having latency issues. A potential time out can be caused by one of the hop locations having internet issues. Another potential cause can be from weather in the case of certain internet providers causing barriers with connectivity.
No comments:
Post a Comment