When I click a link, I used to picture the internet as a kind of cloud floating above my house. The truth is much more physical, and much more interesting. The internet gets to my house through cables, boxes, and a chain of handoffs, each one doing a small, specific job. Once I understood that chain, slow evenings and strange error messages started to make sense.
It starts with a name
Every website I visit has a name I can remember, but computers do not use names to find each other. They use numbers called IP addresses. So the first step is translation. When I type an address, my computer asks a Domain Name System, or DNS, server what number belongs to that name. Think of DNS as a phone book for the internet: I look up a name, and I get the number I need to call. That answer is usually remembered for a short time, which is why a second visit can feel faster.
My home network is a small neighborhood
Inside my house, my devices form a small local network. Each one gets a local address, and my router keeps track of who is who. When my laptop asks for a page, it does not shout directly to the whole internet. It sends the request to the router, which is the front door of my home network. The router also does a useful piece of translation: it lets many devices share the single public address my internet provider gives my house, and it remembers which reply belongs to which device.
The last mile is the hard part
From the router, the signal leaves my house through what engineers call the last mile. This is the final stretch to my internet service provider, or ISP, and it is often the hardest part to build. It might travel through a fiber-optic cable, a cable-television line, a telephone line, or a wireless link. Fiber carries signals as pulses of light through thin glass strands, which is why it can move a great deal of data quickly. Older copper lines use electrical signals and are more limited by distance and interference. Whatever the medium, this is the stretch most likely to be affected by roadworks, weather, or an overloaded local connection.
My ISP is the on-ramp
My ISP runs the larger network beyond my street. It connects homes and businesses in my area, then hands their traffic onward to bigger networks. Those bigger networks carry data across regions and, through undersea cables, across oceans. Data does not travel as one continuous stream. It is broken into packets, like letters in separate envelopes, each labeled with where it came from and where it is going. Routers along the way read those labels and pass each packet toward its destination, choosing routes that are available at that moment. At the far end, the packets are reassembled in order.
What a router really does
I used to think a router was just a box that made Wi-Fi. Wi-Fi is only the radio part, and in many homes it is handled by the same box. The router itself is a traffic manager. It receives packets, checks their destinations, and decides the next hop. It also runs a firewall, in the simple sense that it does not welcome unsolicited traffic from outside. It keeps a table of active connections so replies can find their way back to the right phone, laptop, or television. When my connection feels slow, the router is often not the villain; it is simply passing on a delay that began further upstream, or sharing a limited link among many hungry devices.
Why speed is not one number
Advertised speeds describe a maximum under good conditions, not a promise for every moment. My connection is shared in places, slowed by distance, and affected by the server at the other end. A video can buffer because the server is busy, because a link along the route is congested, or because my own home network is crowded. Latency also matters. That is the time a small request takes to go and return, measured in a fraction of a second. For browsing and video calls, low latency can matter more than a headline download speed.
So what happens when I click?
Put together, the journey looks like this. My device asks DNS for the site’s address. It sends packets to my router. The router sends them through the last mile to my ISP. Larger networks carry them to the site’s servers. The servers reply, and the packets travel back along a similar path. My router sorts them out and hands them to the right device. Then my browser assembles the page. It feels instant, but it is really a relay race, with many hands passing small, carefully labeled pieces of data. That is why the internet feels like magic, and why it sometimes, quite understandably, stumbles.