Travelling Through The Network!

 For another assignment, I had to use the ping and traceroute commands in the terminal to see the connectivity between three websites.

The ones I chose are as follows:

1. Google (google.com)

2. Apple (apple.com)

3. Amazon (amazon.com)

In all honesty, the results for these ended up being fairly similar between Google and Apple, both responding within 20 milliseconds (ms), and both of their traceroute tests were pretty simple and were over pretty soon after they began. 

Amazon, though, had a fairly different result. 

The ping test ranged up to 55 ms, and the traceroute test took the longest to complete, with many "Request timed out" messages before it finally ended. 

A bit of full transparency: My fiancé was working from home while doing these tests, so the results varying could be because of that, but unfortunately I have no way of saying for sure.

Why Does It Matter?

The ping and traceroute commands are probably the first thing an IT Specialist thinks about when they hear that the internet is having an issue, and very quickly provides insight on whether the website is having the issue, or if it is the internet equipment having the issue, and can decide next steps on how to resolve the issue. 

Ping Test Results!

Traceroute Results!