How Data Travels the Internet: Packets, Routing & Hops
Every time you click a link, your request is chopped into tiny packets that race across the world hop by hop and are reassembled at the far end. Here is how data travels the internet, from your device to a distant server and back again.
When you load a web page, it feels instant and whole — as if the page simply appeared. Behind that illusion, the way data travels the internet is surprisingly physical and step-by-step. Your message is split into small pieces, each piece is addressed and sent out on its own, routers pass those pieces along one link at a time, and the destination stitches everything back together. Understanding this journey demystifies almost everything else about networking.
Nothing moves in one piece: meet the packet
The internet does not send whole files. Instead it uses packet switching: your data is broken into many small units called packets. A single photo might become hundreds of them.
Each packet carries two things. First, a slice of the actual data — a few hundred to about 1,500 bytes of it. Second, a header full of delivery information, most importantly the source IP address (where the packet came from) and the destination IP address (where it is going). If you are unsure what those addresses are, our guide to IP Animals and the wider web can help, and you can always check your own on the front page of the zoo.
Splitting data this way is what makes the internet resilient. If one packet is lost or a link fails, only that small piece needs to be resent, and other packets can flow around the problem by taking a different route.
The internet has no fixed "line" between you and a server. Each packet is addressed and forwarded independently, so two packets from the same click can take completely different paths and still arrive at the same place.
From your device to the first router
Before a packet can travel anywhere, your device needs to know where it is going. A name like example.com is not an address a router understands, so your computer first performs a DNS lookup to translate that name into an IP address such as 93.184.216.34.
With a destination address in hand, your device checks whether that address is on your local network. It usually is not, so the packet is handed to your default gateway — your home router. The router is the doorway between your private home network and the public internet, and it is the first of many that will handle your packet.
Hop by hop: how routing actually works
From your router, the packet enters your Internet Service Provider's network and begins a relay race. At every stage it arrives at a router, which reads the destination IP address, consults its routing table, and forwards the packet out of whichever port moves it closer to its goal. Each of these steps is called a hop.
No single router knows the whole path. Each one only knows the next best step, a little like asking for directions town by town rather than being handed a complete map. This is the genius of the design: the network can be enormous and constantly changing, yet every router only has to make one local decision.
A typical journey across the internet involves somewhere between about 10 and 30 hops. You can watch this happen yourself with tools like traceroute, which reveals each router your packets pass through and how long each hop takes.
| Stage | What handles it | What it does |
|---|---|---|
| Your device | Operating system | Splits data into packets, adds source and destination IP addresses |
| Home network | Router | Sends packets toward the internet through your gateway |
| Access network | ISP routers | Carry packets from your neighbourhood toward the internet core |
| The core | Backbone routers & peering points | Forward packets between large networks across cities and oceans |
| Destination network | Server's router | Delivers packets to the correct server |
Crossing the world through the internet's core
Big networks connect to one another at internet exchange points and through private links, where they agree to pass each other's traffic. The rules for how these thousands of independent networks share routing information are set by the Border Gateway Protocol (BGP), the system that effectively lets the whole internet agree on how to reach any address.
Physically, your packets may travel down fibre-optic cables, across continents, and even through undersea cables spanning entire oceans. Signals in fibre move at roughly two-thirds the speed of light, which is why a request to a server on another continent still returns in a fraction of a second, despite the astonishing distance involved.
Reliability: making sure nothing goes missing
Packets can be dropped, delayed, or delivered out of order. Whether that matters depends on the transport protocol in use. Most web traffic relies on TCP, which numbers every packet, waits for acknowledgements, and re-sends anything that goes missing. TCP also reassembles packets into the correct order, so the page you receive is identical to the one that was sent even if the pieces arrived in a jumble.
Other traffic, such as live video and voice calls, often uses UDP, which skips those guarantees in exchange for speed. A momentary glitch in a call is preferable to the whole conversation pausing while a lost packet is resent.
The return trip and the bigger picture
When your packets reach their destination server, the server reads your request, prepares a response, and sends its own stream of packets back to your IP address. Those packets make their own hop-by-hop journey home, possibly by an entirely different route, and your device reassembles them into the page you see.
This whole choreography — addressing, packetising, routing, and reassembly — maps neatly onto the layered model of networking described in the OSI model. Each layer has one job, and together they turn a simple click into a global relay that finishes before you have even blinked.
Frequently asked questions
What is a packet?
A packet is a small chunk of data wrapped in addressing information. Rather than send a whole file or web page as one lump, the internet breaks it into many packets, each carrying a piece of the data plus the source and destination IP addresses needed to deliver it.
What does a hop mean on the internet?
A hop is one step in a packet's journey — the move from one router to the next. A packet crossing the internet typically passes through somewhere between about 10 and 30 hops before it reaches its destination.
Do all my packets take the same route?
Not necessarily. Each router makes its own forwarding decision, so packets from the same connection can follow different paths and even arrive out of order. TCP puts them back into the correct order at the destination.
How fast does data travel across the internet?
Signals move through fibre at roughly two-thirds the speed of light, so a packet can cross a continent in tens of milliseconds. Most of the delay you notice comes from the number of hops, queueing at busy routers, and the physical distance involved.