Learning how packets travel across the internet gave me a clearer picture of what happens every time I type in a website or send a message. Using the ping and traceroute commands, I was able to see not just whether a site responded but also how far data traveled and how many devices it passed through along the way.
A ping sends a small packet to a server and measures how long it takes to return. Pinging Google gave me an average of 10 milliseconds, which is extremely fast. The Australian site abc.net.au averaged 13 milliseconds, also quick because it likely used a content delivery server closer to me instead of sending packets all the way to Australia. In contrast, rakuten.co.jp in Japan had an average of 191 milliseconds, reflecting both the greater distance and the number of networks the packets had to cross.
Traceroute for Google:
Traceroute for ABC AU:
Traceroute for Rakuten JP:
The traceroute results helped explain why the ping times were different. Google’s path showed several backbone routers before timing out, which is normal because many networks block traceroute replies. The path to abc.net.au completed in nine hops with a few timeouts, confirming the packets still reached the destination. Rakuten required nineteen hops, and the jump in response time after leaving U.S. networks showed the extra distance of the trans-Pacific route.
From these results, I learned that roundtrip time is strongly related to geographical distance but is also shaped by how networks are designed. Australia’s fast response was probably due to cached servers in the United States, while Japan’s connection required a true overseas path, which added latency.
These tools are also very useful for troubleshooting. Ping confirms if a host is reachable and whether packet loss is happening. Traceroute identifies where along the path delays or failures occur. Both can explain why a connection feels slow or why a site may not load. Timeouts can happen for different reasons, including firewalls blocking ICMP requests, routers that are configured not to respond, or congestion and hardware issues along the path.
Exploring how data travels across the network showed me how much happens behind the scenes every time I connect online. What feels like a simple click is actually a packet journeying across routers, networks, and sometimes even oceans before reaching its destination and returning with a reply.
0 comments