Traveling Through a Network

Ping and Traceroute - 

I first Pinged Google, with the following results - 

I chose not to add more ping request and went with the standard Window's 4, and my results are pretty speedy, between 5ms and 8ms.  Next I chose to ping BBC.uk.co, and the results were about the same, between 5ms and 8ms as seen below - 

And last I tried pinging Japantimes.co.jp with no results, and request timed put messages presented - this can be

for different reasons like the site is down, they don't accept ping packets, etc. 

Next I moved onto the TraceRT command, starting with 8.8.8.8 and these are my results - my only had 1 hop, and 2 destinations  with very low MS numbers- 

Below are my attempts to tracert both BBC news and Japan Times - 

As you can see both attempts only took 2 hops and relatively low times as well.

Ping and Tracert send small packets of information to the end destination, and the results are returned either in MS or by timing out. As you can see, my results are very uninteresting... all of my tests returned 1/2 hop(s) and very low times.  Unfortunately I believe this is due to how I am currently operating on my network, but that would be for a different conversation as I am based in the east coast, I would have expected to see different results had I not been on my network.  These packets basically travels from your home network wrapped up in a header and a footer, which tells the computers/routers what kind of information is inside and how to filter, where it is going and where it comes from, and how it fits with other possible data.  The data takes the best possible route, and travel from machine to machine until they reach their final destination.  Once there the machine reassembles the information and the data completes its journey.  As previously stated, ping and tracert can fail for several reasons, they could fail due to your connection, they could also fail because the end destination is experiencing network issues.  They could also fail is the destination is behind a firewall, or they have the port locked and not receiving unsolicited messages.  These tests could help diagnose network issues by showing which step is the message failing, if you even have a connection etc.