A Request That Travels the World in Milliseconds
When you type a URL into your browser and press Enter, a remarkable chain of events unfolds — one involving your home router, your Internet Service Provider, a global network of physical cables and routers, data centres possibly thousands of kilometres away, and multiple layers of software protocols — all completing a round trip in the time it takes to blink. Here's how it actually works.
Step 1: Your Browser Asks "Where Is That?"
A web address like example.com is human-friendly. Computers communicate using numerical IP addresses (like 93.184.216.34). Your browser doesn't know the IP address for a site it hasn't visited recently, so it asks a DNS server (Domain Name System) — essentially the internet's phone book — to look it up.
Your ISP typically operates DNS servers, though you can also use public ones. The DNS server returns the IP address, and your browser now knows where to send your request.
Step 2: The Physical Journey Begins
Your data travels outward from your device as electrical signals (through cables), light pulses (through fibre optics), or radio waves (over WiFi or mobile networks). It passes through your router, then your ISP's infrastructure, then into the broader internet backbone.
The "backbone" of the internet is a physical reality: thousands of kilometres of undersea cables running across ocean floors, connecting continents. As of the mid-2020s, well over 400 submarine cable systems connect the world's landmasses. The overwhelming majority of international internet traffic travels through these cables — not satellites, as is commonly assumed.
Step 3: Packets, Not Streams
Your request isn't sent as one continuous message. It's broken into small chunks called packets, each labelled with where it came from and where it's going. These packets can travel via different routes and arrive out of order — the receiving computer reassembles them. This approach, called packet switching, makes the network robust: if one route is congested or broken, packets simply take another.
Step 4: Routing — The Internet's Navigation System
Hundreds of thousands of specialised computers called routers form the skeleton of the internet. Each router maintains a routing table — a constantly updated map of the best paths to reach different parts of the network. As your packets pass through the network, each router makes a decision: "Which direction is closest to the destination?" and sends the packet onward. This process repeats dozens of times across the globe in fractions of a second.
Step 5: The Server Responds
Your packets arrive at a web server — a computer (or more likely a cluster of computers in a data centre) running software designed to handle web requests. The server reads your request, retrieves the relevant files (HTML, images, scripts), and sends them back as packets following the same process in reverse.
Step 6: Your Browser Assembles the Page
Your browser receives the packets, reassembles them in order, and then interprets the HTML, CSS, and JavaScript to render the page you see. What looks like a seamless experience is actually the result of dozens of separate requests — for the HTML structure, each image, each stylesheet, and each script — all happening nearly simultaneously.
The Protocols That Hold It Together
| Protocol | What It Does |
|---|---|
| TCP/IP | Governs how packets are addressed, sent, and reassembled |
| DNS | Translates domain names into IP addresses |
| HTTP/HTTPS | Defines how browsers and servers communicate; HTTPS adds encryption |
| BGP | Border Gateway Protocol — how routers share routing information across the whole internet |
A Surprisingly Fragile Wonder
The internet feels like an invisible, ethereal thing — but it is fundamentally physical infrastructure, dependent on cables, data centres, and electricity. Its resilience comes not from any single robust system, but from decentralisation and redundancy. That design philosophy, baked in from the beginning, is exactly why it has scaled from a handful of connected computers to billions of devices — and why it keeps working even when parts of it break.