A message's journey across the internet
🏠The everyday picture
A parcel from Patna to London goes from your house to the local post office, a sorting centre, the airport, another country's sorting centre, a local office and finally a doorstep. No single vehicle makes the whole trip, but every step knows where to pass it next.
📘What it really is
When you open a website:
- Your device sends packets to your router.
- The router passes them to your ISP.
- The ISP routes them across other networks, hop by hop, each router choosing the next step.
- They reach the data centre where the website's server lives.
- The server replies, and the reply travels back, often by a different route.
This usually takes a fraction of a second. Each step adds a little latency, which is why a server in Mumbai feels faster to Indian users than one in the USA.
🖱️Try it
Windows: open Command Prompt and type tracert google.com. Mac: open Terminal and type
traceroute google.com. Each line is one hop on the journey. Note how many hops it takes, and how the times
grow. (Some hops show *, which just means that router doesn't reply to this test.)
✅Quick check
Your users are mostly in India. Should your server be in Mumbai or in the USA?
Show the answer
Mumbai (or nearby): fewer hops and less distance mean lower latency for your users.
Does your website's data travel along one fixed wire from the server to the user?
Show the answer
No. Packets pass through many routers and networks, and may take different routes.