Traceroute

After some technical issues, eg- Power outages due to severe storms in the Midwest!!, i have finally came back online.
This move to the US is starting out kind off rough.
One thing you learn from being without connectivity is how dependent on the Net i actually am.
No internet = no school
= no online banking
= no bill payments
= no entertainment!
But anyway back to the job at hand.... Using traceroute.

In various employments i have partaken, traceroute was a tool i have used before. Not in any great capacity, but on the job to check connectivity issues.
For example, you could use traceroute to find out on a big network with multiple routers where your computers information routes through. Which could also lead to tell you if a particular router is not working.
For the task at hand, we had to go to a site with a hosted traceroute program. I went to the site http://centralops.net/co/
Well as you can see above in the screen capture, there was 22 hops along the way using the traceroute application.
The average time in milliseconds for a return trip from server to server is 252.3.
This the average of all three of the final columns responses.
Lastly but not least, from the traceroute tool we now discovered that the IP address for Curtain was 134.7.179.53 .

In reflection, you can see where traceroute would serve many purposes. From finding an IP address to finding the route your data travels.
The information really shows that things do a lot of work in the background for even the smallest Internet commands. These things being routers, servers and all other kind of network equipment along the way.
The internet indeed does bridge a huge gap that we are normally totally unaware of.
Now its time for me to hop of to work. Now wouldn't that look funny:)