What I Learned About Network Connections Using Ping and Traceroute

For this activity, I used the ping and traceroute commands to see how data travels across the Internet. I tested three different websites: google.com, yahoo.co.jp, and target.co.au. The goal was to understand how devices communicate over a network and how distance and routing affect performance.

Running the ping command showed me how long it takes for data to travel from my computer to a website and back. What I noticed right away was that websites closer to my location had faster response times, while sites hosted farther away took longer. This made it clear that physical distance plays a big role in network speed. It also helped me understand why some websites feel faster than others, even when using the same internet connection.

Traceroute gave me a different perspective by showing the path the data takes to reach its destination. Instead of just seeing speed, I could see each step along the way, including the different routers the data passed through. Some routes had more stops than others, which explained why certain connections took longer. It was interesting to see that data does not always take a direct path and can move through multiple locations before reaching its final destination.

One thing that stood out was how network performance is not just about speed, but also about the path being taken. Even if two websites are far away, the number of hops and the efficiency of the route can make a difference. This helped me understand how network troubleshooting works, especially when trying to figure out where a connection issue might be happening.

There are also times when ping or traceroute can time out or return an error. Two possible reasons are that a website or router may block those requests for security purposes, or there may be a network issue somewhere along the route. A timeout can also happen if the destination server is unavailable or if the connection is interrupted.

From a real-world perspective, this connects directly to what I do at T-Mobile. When customers experience slow data or trouble connecting to certain apps or websites, tools like ping and traceroute can help identify the issue. Whether it is a network delay, a routing issue, or something on the user’s device, these tools provide a clearer picture of what is happening behind the scenes.

Overall, this activity gave me a better understanding of how networks function and how data moves across the internet. It showed me that even simple tools can provide valuable insights into performance and troubleshooting, insights I can apply both in my coursework and in real-world situations.