How the Internet Actually Works
Packets, routers, and DNS — explained plainly while you type.
The internet connects three billion people, but most of us have no idea how it actually works. This article explains the real mechanics — no jargon, no oversimplification. Type each section to work through it.
Part 1
Part 1: It's Not a Cloud
Let's clear up the biggest misconception first.
Part 1 of 1
The internet is not a cloud. It is not wireless. At its core, it is millions of kilometers of physical cables buried under oceans and streets. When you load a webpage, your request travels through copper wire, fiber optic glass, and a dozen machines before reaching a server on the other side of the world. The wireless part only covers the last few meters, from your router to your phone.
WPM 0
Accuracy 100%
Progress 0%
Streak 0 🔥
Speed Target: 38 WPM
▼
⏱️ Start typing...
Part 2
Part 2: Packets — Breaking Data Into Pieces
Why your files get chopped up before they travel.
Part 1 of 1
Your computer does not send files as a single block. It splits everything into small chunks called packets, each around 1,500 bytes. Each packet gets a header stamped with the destination address, a sequence number, and error-checking data. They leave your machine independently, possibly taking different routes across the network, and reassemble at the destination. If one packet gets lost, only that piece needs to be resent.
WPM 0
Accuracy 100%
Progress 0%
Streak 0 🔥
Speed Target: 38 WPM
▼
⏱️ Start typing...
Part 3
Part 3: Routers — The Traffic Directors
Routers do one job, and they do it billions of times a day.
Part 1 of 1
A router reads the destination address on each packet and decides where to send it next. Your home router is the simplest kind: it forwards packets between your devices and your ISP. The internet backbone has routers that handle millions of packets per second, constantly consulting routing tables to find the fastest path. When a cable is cut or a server goes down, routers reroute traffic around the problem in milliseconds.
WPM 0
Accuracy 100%
Progress 0%
Streak 0 🔥
Speed Target: 38 WPM
▼
⏱️ Start typing...
Part 4
Part 4: DNS — The Internet's Phone Book
Turning human-readable names into machine-readable numbers.
Part 1 of 1
Every device on the internet has a numerical IP address. Humans are bad at remembering numbers like 142.250.80.46, so DNS translates domain names into IP addresses. When you type a website name into your browser, your computer asks a DNS resolver for the matching IP address. This lookup usually takes under 20 milliseconds. Without DNS, you would need to memorize the IP address of every site you visit.
WPM 0
Accuracy 100%
Progress 0%
Streak 0 🔥
Speed Target: 38 WPM
▼
⏱️ Start typing...
Part 5
Part 5: What Happens in One Second
A fast summary of everything that fires when you press Enter.
Part 1 of 1
When you press Enter on a URL, your browser checks its cache, then asks DNS for the IP address, then sends a connection request to that server using TCP. The server responds, your browser downloads the HTML, requests any linked CSS and JavaScript files, and renders the page. A typical page load triggers dozens of these exchanges. All of it happens in under two seconds, across possibly fifteen countries, because of the engineering decisions made in the 1970s.
WPM 0
Accuracy 100%
Progress 0%
Streak 0 🔥
Speed Target: 40 WPM
▼
⏱️ Start typing...
Article Complete!
You now know more about internet infrastructure than most people who use it every day.
ADVERTISEMENT
336×280