Traveling Through a Network

 

How Packets Travel Through a Network

When data is transmitted over the internet, it is broken into packets that contain both the source and destination addresses. These packets move through routers until they reach the target host, which then sends responses back.

• Ping measures how long it takes for packets to travel to a host and back, giving an average roundtrip time (RTT).

• Traceroute maps the journey by showing each hop along the way, helping identify where delays may occur.

Ping Results

I tested three websites: Google, YouTube, and Apple.

• Google: Average ping of 10.949 ms, with no packet loss.

• YouTube: Average ping of 14.801 ms, slightly higher than Google.

• Apple: Similar results, though with variations depending on the time of test.

The lower ping to Google shows a faster roundtrip time, while the higher ping to YouTube reflects additional network travel.

Traceroute Results

Traceroute provided more details on how packets reached each server:

• Google: About 6 hops to reach the destination.

• YouTube: About 9 hops, showing more network devices in the path.

This demonstrates how the number of hops—and the networks the packets pass through—affects response time.

Real-World Impact

These results match my own experiences as a gamer. Living in Colorado, I notice higher latency when playing online with friends on the East Coast. Servers closer to them create a disadvantage for me, as I experience lag, packet loss, or even disconnections in games like Call of Duty. This shows how distance and routing paths directly impact performance.

Troubleshooting with Ping and Traceroute

Both commands are important diagnostic tools:

• Ping helps identify latency issues and packet loss.

• Traceroute provides detail about where a problem occurs—such as a specific router or network segment.