PART 1: 

 

PART 2: 

PART 3: 

I have a caching problem. At least with some websites commonly used such as google.com. My ping results to common websites are good while trace routes are too quick as it is cached in the nearest router owned by AT&T.

Ping is a good tool to use to test if a website or network location is up and available. It measures total time for response from the location and any dropped packets. While trace route shows the path that a packet takes through the network. It can be used to troubleshoot a problem reaching a particular site that you know is up but are unable to reach. For example, one time we were having some sort of network issue and couldn't access most websites. Our pings out using IP addresses were good showing the network was working but we were unable to pull up websites. So we moved to trace routes. This showed a problem reaching our external DNS server. The hop before the server was consistently timing out. It turned out that the switch used had went bad and was causing outages all over.