Pinging And Tracerouting From Sites All Over The World


Post 4 - Check out my interesting find on pinging different websites around the world!

 

Part 1: Ping Activity


I tested my theory on ping command on three sites: google.com (US), amazon.co.uk (UK), flashscore.co.za (South Africa).

google ping test


google.com: Sent = 4, Received = 4, Lost = 0

amazon ping test

amazon.co.uk: Sent = 4, Received = 4, Lost = 0

flashcore ping test

flashscore.co.za: Sent = 4, Received = 4, Lost = 0


Part 2: Traceroute Activity


Tested traceroute command on three sites: google.com (US),  amazon.co.uk (UK), flashscore.co.za (South Africa).

google.com: 0 packets lost, 1 unsuccessful hop, reached destination.

amazon.co.uk: 5 packets lost, 1 unsuccessful hop, reached destination.

flashscore.co.za: 0 packets lost, 1 unsuccessful hop, reached destination.


Part 3: Traveling Through a Network


When comparing the ping activity of the three selected sites, it was surprising to see that the flashscore.co.za representing South Africa exhibited similar speeds to google.com in the United States. All sites followed standard routing procedures, beginning with the home router and then passing through Comcast servers after initial communications from the home router. Notably, the route from flashscore.co.za involved fewer servers to reach its destination. This could be attributed to the varying levels of traffic managed by google.com and amazon.co.uk compared to flashscore.co.za. As per statistics provided by semrush.com, a free website traffic checker, in February 2025, google.com traffic reached over 139.92 billion hits, amazon.co.uk received 435.86 million hits, and flashscore.co.za garnered approximately 3.25 million hits. Google and Amazon require numerous servers to accommodate this extraordinary traffic volume, whereas flashscore.co.za might need significantly fewer servers.


A factor not previously mentioned is the process of load balancing the servers. Load balancing involves distributing network traffic across multiple servers to optimize performance, enhance reliability, and improve application availability by preventing any single server from becoming overloaded. This technique is applied in certain areas to maintain functionality for both google.com and amazon.co.uk, ensuring users experience minimal disruption. If server crashes occur, it could deter users due to frustration and perceived unreliability.


The traceroute and ping commands are instrumental in verifying communication and destinations. Ping commands allow for confirmation of device communication with the server. An absence of successful ping responses indicates no active communication, suggesting the device is non-functional. Traceroute commands can identify the problematic location or server causing issues, which may not necessarily be the home router but potentially an intermediate server encountering downtime or rerouting, leading to slower connection times.  This is a great tool for discovering the problem area.


Several potential issues may cause ping and traceroute commands to time out, including:


From ping Issues:


The device may not be connected to a live switch port.

The device could be outdated or at the end of its lifecycle.

The switch port or device router might be powered off or similarly outdated.

There may be no communication with the ISP server due to maintenance or inclement weather.

Human error resulting from incorrect IP address or site spelling.

Private or different VLAN.

From traceroute Issues:


The server for the website may be down.

The server's response time may exceed the TTL limit, preventing communication.

The domain may be unavailable.

Firewall Restrictions.

Comments

Popular posts from this blog

Network Security - The History And Future

My Thoughts On Nike's SNKR.com App

How Computers Play A Part In My Profession Of Healthcare