How the Internet Works

It Started with Four Computers

On October 29, 1969, a UCLA grad student named Charley Kline sat at a teletype terminal and tried to send the word “LOGIN” to a computer at Stanford Research Institute, 350 miles away. The system crashed after two letters. The internet's first message was an accidental “LO.”

That connection — between just four university computers — was ARPANET, funded by the U.S. Department of Defense. It was designed to survive a nuclear attack by routing messages through any available path, rather than a single central hub. That idea — packet switching — would become the foundation of the modern internet.

Over the next two decades, ARPANET grew from 4 nodes to thousands. Email was invented (1971). TCP/IP was adopted as the universal protocol (1983). Tim Berners-Lee proposed the World Wide Web (1989). And in 1993, the Mosaic browser made the web visual and accessible to everyone — the floodgates opened.

The Explosion

In 1995, 16 million people used the internet — fewer than the population of New York City. By 2026, that number has reached 5.56 billion — 69% of every human being alive. No technology in history has scaled this fast.

Radio took 38 years to reach 50 million users. Television took 13 years. The internet did it in 4. Facebook did it in 3.5. ChatGPT did it in 2 months. Each new wave of technology rides on the infrastructure of the last.

The Physical Internet

The internet is not in the cloud. It is underwater. Over 550 submarine cables sit on the ocean floor, carrying 99% of intercontinental data. These fiber optic cables — about the thickness of a garden hose — span 1.4 million kilometers. That's enough to wrap the Earth 35 times.

A single modern cable like Google's Grace Hopper can carry 340 terabits per second. Building one costs billions of dollars and takes years. And yes — sharks occasionally bite them. Cable operators armor the most vulnerable sections with steel wire and Kevlar-like wrapping.

On land, over 8,000 data centers worldwide house the servers that store and process everything from your emails to Netflix streams. Together, they consume about 2.5% of global electricity — more than many individual countries.

The Layer Cake

How do billions of devices all speak the same language? Through a layered system of protocols called TCP/IP. Think of it like sending a letter: you write the message (Application layer), seal it in an envelope (Transport), write the address (Internet), and hand it to the postal service (Network Access).

Each layer wraps the data from the layer above with its own header — a process called encapsulation. At the destination, each layer strips off its header and passes the data up. The beauty is that each layer only cares about its own job. HTTP doesn't know about fiber optics. Ethernet doesn't know about web pages.

Finding the Address

You type “google.com” into your browser. But computers don't understand names — they need an IP address like 142.250.80.46. The system that translates between the two is DNS — the Domain Name System, often called the “phone book of the internet.”

Your browser first checks its own cache. Then the operating system cache. If neither has the answer, a recursive resolver (usually run by your ISP) starts a chain of queries: root nameserver → .com TLD server → google.com's authoritative nameserver. The whole process takes 20–120 milliseconds — and the result is cached at every level so the next lookup is instant.

The Handshake

Before any data is exchanged, your browser and the server need to establish a connection. TCP (Transmission Control Protocol) does this with a 3-way handshake: your device sends a SYN (“I want to connect”), the server replies with SYN-ACK (“Acknowledged, let's connect”), and your device confirms with ACK (“We're connected”). This takes 10–100 milliseconds.

TCP guarantees that every packet arrives and arrives in order. If a packet is lost, TCP retransmits it. This makes it perfect for web browsing, email, and file transfers — anything where accuracy matters. For video calls and gaming, UDP skips the handshake and reliability guarantees for raw speed — a dropped frame matters less than latency.

The Journey

When you click a link, your request doesn't travel in a straight line. It hops through routers, exchange points, and submarine cables — each hop adding a few milliseconds. A single web page might require 50–100 separate packets, each potentially taking different routes, all reassembled at the destination by TCP.

A packet from New York to Tokyo travels ~10,850 km through submarine fiber optic cables under the Pacific Ocean in about 83 milliseconds. London to Sydney takes ~153 ms across 17,000 km of cable through the Mediterranean, Red Sea, and Indian Ocean. The speed of light in fiber is the fundamental limit — no amount of engineering can beat physics.

The Secret Handshake

Without encryption, anyone between you and the server — your ISP, a coffee shop Wi-Fi owner, a government — can read every byte you send. TLS (Transport Layer Security) fixes this with a clever trick: the server sends you a public key (a padlock), you lock a random secret with it, and only the server's private key can unlock it.

Once both sides share the secret, they switch to fast symmetric encryption for the rest of the conversation. This is why you see a padlock icon in your browser — it means TLS is active. Today, over 95% of web traffic uses HTTPS. The “S” stands for “Secure” — it means TLS is protecting your connection.

The Conversation

With a secure connection established, your browser sends an HTTP request — a structured text message saying: “GET /search?q=cats HTTP/2. Host: google.com.” The server processes it and sends back a response: status code (200 OK), headers (content type, caching rules), and the body (the HTML page).

But that's just the beginning. The HTML references CSS, JavaScript, images, fonts — each triggering additional HTTP requests. A typical modern web page makes 70+ separate requests totaling several megabytes. HTTP/2 and HTTP/3 can multiplex these over a single connection, but the waterfall of dependencies still defines page load performance.

GET /search?q=cats HTTP/2
Host: google.com
Accept: text/html
User-Agent: Mozilla/5.0

HTTP/2 200 OK
Content-Type: text/html; charset=UTF-8
Content-Length: 15234
Cache-Control: max-age=300

<!DOCTYPE html>
<html>...</html>

What Happens in One Second

Every single second, the internet carries more data than the entire Library of Congress contains. 99,000 Google searches. 3.8 million emails. 694,000 YouTube videos watched. 70,000 gigabytes of traffic. $443,000 in Amazon sales. All happening simultaneously, every second, around the clock.

In the 5 seconds it took you to read this paragraph, about 495,000 Google searches were completed, 19 million emails were sent, and Amazon processed over $2 million in sales. The internet isn't just a network — it's the most complex machine humanity has ever built, running at a scale that defies intuition.

The Big Picture

Every click runs a pipeline: URL → DNS → TCP → TLS → HTTP → Routers → Cables → Server → Response → Render. Ten stages. Dozens of protocols. Thousands of miles of fiber. Billions of transistors. All in 50–200 milliseconds.

The internet started as a Cold War experiment connecting four university computers. Today it connects 5.56 billion people, carries 500 terabytes per second, and underpins virtually every aspect of modern life — from commerce and communication to science and entertainment. It is, by any measure, the most transformative technology in human history.

Frequently Asked Questions