📍 Mumbai to Virginia⏱️ 247 milliseconds🔄 12 devices
Prologue
A Click in Mumbai
📍 Andheri East, Mumbai • 2:34 PM IST
Priya's finger touches the trackpad. A click. Such a small thing — a butterfly wing's worth of pressure, a circuit closing for 50 milliseconds. And yet, this tiny gesture sets in motion a journey that will span continents, pass through dozens of machines, and travel at nearly the speed of light.
She wants to see GitHub's homepage. That's all. A simple request. But to fulfill it, her laptop must reach across 13,000 kilometers of ocean, fiber, and silicon to a server in Ashburn, Virginia. And in that journey lies the entire architecture of the modern internet.
This is the story of that journey. Not from the outside — from the inside. We will become the packet. We will feel the transformation as we're wrapped in headers, shot through cables, examined by gatekeepers, and finally unwrapped at our destination.
Our name is PKT-7842. We carry a simple message: GET / HTTP/1.1. And we have 250 milliseconds to deliver it.
The clock starts now.
◆
Chapter 1
Birth in the NIC
📍 Priya's Laptop • T + 0.1 ms
I begin as nothing more than an idea — a string of characters in Chrome's memory. GET / HTTP/1.1. A polite request to please send the homepage.
But ideas can't travel on wires. To leave this laptop, I must become physical. I must be transformed into something that can ride electromagnetic waves through the air.
My first stop: the Network Interface Card.
🎴
Network Interface Card (NIC)
Intel Wi-Fi 6E AX211 • Priya's Laptop
Layer 1 & 2
The NIC is a translator, a bridge between the world of software and the world of physics. It takes my digital self and prepares me for the physical journey ahead.
"Ah, a new packet. Let me see... you're headed for 140.82.121.3. That's not on our local network — you'll need to go through the router. First, let me dress you properly for travel."
What the NIC Does to Me
1Wraps me in an 802.11 frame — adds the source MAC address (this laptop's identity: a4:83:e7:2f:5b:c1) and destination MAC (the access point: d8:07:b6:c2:4a:e1)
2Calculates a checksum (FCS) — a mathematical fingerprint to verify I'm not corrupted during travel
3Converts me to radio waves — encodes my bits as Wi-Fi signals at 6 GHz, using OFDM modulation
4Transmits — broadcasts me through the antenna at 6 billion oscillations per second
My IdentityPKT-7842
Source MACa4:83:e7:2f:5b:c1
Dest MACd8:07:b6:c2:4a:e1 (AP)
SignalWi-Fi 6E • 6 GHz • 160 MHz channel
I feel myself changing. I'm no longer just data — I'm a ripple in the electromagnetic field, a pattern of waves radiating outward from the laptop's antenna at 300,000 kilometers per second.
I've been alive for 0.1 milliseconds.
The NIC's Secret Power
Modern NICs are incredibly sophisticated. They don't just send and receive — they offload work from the CPU. This Intel AX211 can calculate checksums in hardware, segment large transfers, handle encryption, and manage multiple simultaneous streams. Priya's CPU never touches most of this work.
Chapter 2
The Access Point Crossing
📍 Living Room Ceiling • T + 0.3 ms
I fly through the air, invisible, a ghost made of radio waves. Other signals surround me — Bluetooth from a smartwatch, another Wi-Fi network from the neighbors, microwave interference from the kitchen. The 6 GHz band is cleaner, less crowded. I slip through the noise.
Then I hit something. A receiver. An antenna mounted on a white box stuck to the ceiling. The Access Point.
📶
Wireless Access Point
TP-Link AX5400 • Tri-Band Wi-Fi 6E
Layer 2
The access point is a translator between two worlds — wireless and wired. It speaks both 802.11 (Wi-Fi) and 802.3 (Ethernet). Its job is to convert me from radio waves back into electrical signals.
"Incoming frame on radio interface. Let me decode... source a4:83:e7:2f:5b:c1, destination d8:07:b6:c2:4a:e1. That's me! The payload is addressed to b8:27:eb:4c:ea:1d — the router. Converting to Ethernet frame and forwarding."
Translation Process
1Receives my radio signal — captures the electromagnetic waves with its antenna
2Demodulates — extracts the digital bits from the analog signal
3Validates the frame — checks the FCS, decrypts WPA3 encryption
4Creates 802.3 Ethernet frame — rewraps me for wired travel with new destination MAC (router)
5Sends down the wire — transmits electrical signals through Cat6 cable
I feel myself transform. No longer waves in the air — now I'm pulses of voltage in a copper wire. The sensation is different. More constrained. The wire is a tunnel, and I race through it at 70% the speed of light.
Chapter 3
The Switch's Decision
📍 Home Network Closet • T + 0.5 ms
The cable leads to a small box with blinking lights — the network switch. This is a crossroads. Multiple devices connect here: the access point, Priya's desktop, a smart TV, a NAS. The switch decides who gets to talk to whom.
🔀
Network Switch
Netgear GS308 • 8-Port Gigabit
Layer 2
Unlike a hub (which blindly broadcasts everything everywhere), a switch is intelligent. It maintains a table mapping MAC addresses to ports. It knows exactly where each device is connected. It only sends frames where they need to go.
"Frame on port 3. Destination MAC b8:27:eb:4c:ea:1d. Let me check my MAC address table... found it. That's port 1 — the router. Forwarding exclusively to port 1. No need to bother the TV or the NAS with this."
MAC Table Entryb8:27:eb:4c:ea:1d → Port 1
DecisionForward to Port 1 only
Processing Time3.2 microseconds
The switch's decision happens in microseconds. Hardware circuits called ASICs perform the lookup — no software, no CPU, just raw silicon logic. Millions of frames per second flow through without breaking a sweat.
I emerge from port 1. Ahead of me: the router.
Why Switches Replaced Hubs
In the old days, hubs broadcast every frame to every port. If you had 8 devices on a 100 Mbps hub, they shared that bandwidth — and every device saw everyone else's traffic. Switches changed everything. Each port gets full bandwidth. Traffic is private. Collisions are eliminated. This is why modern networks are so much faster and more secure.
Chapter 4
The Router's Transformation
📍 Home Router • T + 0.8 ms
The router. This is different. The switch only looked at my MAC address — my local identity. The router looks deeper. It opens me up and reads my IP address — my global identity.
🌐
Home Router
ASUS RT-AX86U Pro • Gateway to the Internet
Layer 3
The router connects different networks. Priya's home network uses private IP addresses (192.168.1.x). But the internet doesn't know those addresses. The router must translate — and it does something remarkable.
"Let me examine this packet. Source IP: 192.168.1.105. Destination IP: 140.82.121.3. That destination isn't local — it's GitHub in Virginia. This needs to go out to the internet. But first... I must perform NAT."
The Router's Deep Work
1Strips the Ethernet frame — removes the local MAC addresses
2Reads the IP header — sees destination 140.82.121.3
3Performs NAT — replaces my private source IP (192.168.1.105) with the public IP (103.21.45.78)
4Records the translation — remembers that port 52431 belongs to 192.168.1.105, so replies can find their way back
5Decrements TTL — reduces my "time to live" counter from 64 to 63
6Creates new Ethernet frame — with the ONT's MAC as destination
Before NAT192.168.1.105:52431 → 140.82.121.3:443
After NAT103.21.45.78:52431 → 140.82.121.3:443
TTL64 → 63
I feel myself changing profoundly. My identity has been altered. I'm no longer from 192.168.1.105 — to the outside world, I'm from 103.21.45.78. The router has given me a new passport for international travel.
🚀
I leave the safety of Priya's home network. Ahead lies the vast infrastructure of the internet — ISP networks, backbone routers, undersea cables. My journey across the world begins.
T + 1.2 ms • ENTERING ISP NETWORK
Chapter 5
The Fiber Gateway
📍 Fiber ONT • T + 1.5 ms
The router hands me off to the Optical Network Terminal (ONT) — the device that connects Priya's home to the fiber optic network. It's like a modem, but for fiber instead of cable or DSL.
📡
Fiber ONT
Jio Fiber ONT • GPON Technology
Layer 1 & 2
The ONT converts electrical signals into pulses of light. It's the boundary between copper and glass, between electrons and photons.
"Ethernet frame received. Converting to optical signal. Encoding for GPON upstream transmission at 1310nm wavelength. Safe travels, little packet — you're about to become light."
Electrical to Optical
1Receives Ethernet — electrical signals on copper
2Encapsulates in GPON frame — adds fiber-specific headers
3Converts to light — laser diode pulses at 1310nm (upstream)
4Transmits — sends light pulses through fiber to ISP's OLT
I become light. No longer electricity, no longer radio waves — pure photons, racing through a glass fiber thinner than a human hair at 200,000 kilometers per second.
Chapter 6
Through the ISP's Kingdom
📍 Jio Network • T + 3 ms
The fiber leads to a massive building — the ISP's Point of Presence (PoP). Inside: racks of equipment, blinking lights, the hum of cooling fans. Thousands of packets from thousands of homes converge here.
🏙️
ISP Edge Router
Cisco ASR 9000 • Carrier Grade
Layer 3
This router is nothing like Priya's home router. This is a beast — processing millions of packets per second from tens of thousands of customers. It runs BGP (Border Gateway Protocol), exchanging routing information with routers around the world.
"Packet for 140.82.121.3. Let me check my routing table... 950,000 routes learned via BGP. GitHub's network is AS36459. Best path: via our peering with Tata Communications. Forwarding to Mumbai Internet Exchange."
The ISP router knows the entire map of the internet — which networks exist, how to reach them, which paths are fastest. It learned this through BGP, the protocol that glues the internet together.
I'm forwarded to the Mumbai Internet Exchange (NIXI) — a building where ISPs and content providers connect directly to exchange traffic.
Chapter 7
Across the Ocean
📍 International Backbone • T + 15 ms
The exchange routes me to a submarine cable. Not just any cable — the SEA-ME-WE 6, a fiber optic artery running along the ocean floor from Mumbai to Marseille to America.
🌊
Submarine Cable System
SEA-ME-WE 6 • Undersea Fiber
Layer 1
I plunge into the Arabian Sea. Around me, other packets — millions of them — stream through parallel fibers. We're traveling at 200,000 km/s through a cable no thicker than a garden hose, buried in the mud of the ocean floor.
Every 80 kilometers, I pass through an optical amplifier — a small capsule on the sea floor that boosts my signal without converting me back to electricity. These repeaters are powered by a single wire running the length of the cable, carrying thousands of volts.
I cross the Atlantic. Past the Azores. Past Bermuda. The journey takes 70 milliseconds — the time it takes light to travel 14,000 kilometers through glass.
I surface in Virginia Beach, where the cable meets land. From there, fiber runs inland to a place called Ashburn — Data Center Alley, home to more internet infrastructure than anywhere else on Earth.
🏰
I approach GitHub's data center. But between me and the servers stand the guardians — machines designed to protect, filter, and direct traffic. I must prove I'm worthy of entry.
T + 142 ms • ASHBURN, VIRGINIA
Chapter 8
The Guardian
📍 GitHub Data Center Edge • T + 145 ms
The data center looms ahead — a massive building, windowless, surrounded by generators and cooling systems. But I can't just walk in. First, I must pass the firewall.
🛡️
Next-Generation Firewall
Palo Alto PA-7000 • Perimeter Security
Layer 3-7
The firewall is a gatekeeper. It doesn't just look at my addresses — it examines my contents, my intent, my history. Is this a legitimate web request? Or an attack disguised as one?
"Incoming packet. Let me examine you carefully...
Source IP: 103.21.45.78 — checking reputation database... clean, no known malicious activity.
Destination port: 443 — HTTPS, encrypted web traffic. Allowed by policy.
Protocol analysis: TCP handshake already established. This is a data packet for an active connection. Checking state table... found. Session is valid.
Deep packet inspection: Encrypted TLS 1.3. Can't see contents, but the handshake was legitimate.
Verdict: PERMIT. Forwarding to internal network."
Firewall Inspection
1Stateful inspection — verifies I belong to an established, legitimate connection
2IP reputation check — confirms my source isn't a known attacker
3Policy matching — checks that HTTPS traffic to web servers is allowed
4Threat detection — scans for attack patterns, malware signatures
I pass the inspection. The firewall stamps me as approved and sends me deeper into the network.
What the Firewall Could Have Done
If I had been malicious — a DDoS packet, a SQL injection attempt, a port scan — the firewall would have dropped me silently. No error message, no response. Just... nothing. From the attacker's perspective, it would seem like GitHub doesn't exist. That's the power of a firewall: making threats disappear into the void.
Chapter 9
The Distributor
📍 GitHub Load Balancer Tier • T + 148 ms
Past the firewall, I encounter another machine — the load balancer. GitHub doesn't run on one server. It runs on thousands. The load balancer decides which one will serve me.
⚖️
Load Balancer
GLB (GitHub Load Balancer) • Layer 7
Layer 4 & 7
The load balancer presents a single IP address (140.82.121.3) to the world, but behind it are hundreds of web servers. It distributes incoming requests among them, ensuring no single server gets overwhelmed.
"New HTTPS request for github.com. Let me check server health...
Server web-prod-1: 45% CPU, 3,200 connections — healthy
Server web-prod-2: 62% CPU, 4,100 connections — healthy
Server web-prod-3: 23% CPU, 1,800 connections — healthy ✓
Using least-connections algorithm. Routing to web-prod-3."
Load Balancing Decision
1Terminates TLS — decrypts my HTTPS wrapper (it has the private key)
2Reads HTTP request — understands I want "GET /"
3Selects server — chooses web-prod-3 based on current load
4Re-encrypts — wraps me in TLS again for internal transport
5Forwards — sends me to the chosen web server
The load balancer does something remarkable: it opened my encrypted envelope, read my request, made an intelligent decision, then resealed me. To the outside world, it looks like one server. Inside, it's an army.
Chapter 10
Journey's End
📍 Web Server web-prod-3 • T + 152 ms
I arrive. After 13,000 kilometers, 12 devices, and 152 milliseconds, I finally reach my destination: a server blade in a rack in Ashburn, Virginia. Its NIC receives me. The journey ends — and a new one begins.
🖥️
Web Server
GitHub web-prod-3 • Application Server
Layer 7
The server's NIC receives me. The operating system's network stack decapsulates me layer by layer. TCP reassembles me with my fellow packets. Finally, the application — GitHub's web server — receives the complete HTTP request.
"HTTP request received: GET / HTTP/1.1
Host: github.com
User-Agent: Chrome/120
4TLS layer decrypts — unwraps the encrypted payload
5Application receives — web server gets "GET / HTTP/1.1"
I'm home. I've been stripped of every layer that dressed me for travel. What remains is pure: the message Priya's browser sent. GET / HTTP/1.1. Please send the homepage.
The server complies. It builds a response — HTML, CSS, JavaScript, images. It wraps this response in new layers, addresses it back to Priya, and sends it on the reverse journey.
95 milliseconds later, Priya sees the GitHub homepage.
Total round trip: 247 milliseconds. Less than the blink of an eye.
Epilogue
The Machines That Make It Possible
📍 Everywhere • Always
I was just one packet. One of 500 billion sent today. Every second, trillions of packets make journeys like mine — through NICs and switches, routers and firewalls, across oceans and continents.
The machines I passed through each had a role:
The NIC
"I translate between software and physics. I give you your identity — your MAC address — and convert your thoughts into signals."
The Access Point
"I bridge wireless and wired worlds. I speak both languages so you can roam free."
The Switch
"I know who's connected where. I forward you only to who needs to see you. No wasted bandwidth, no eavesdropping."
The Router
"I connect worlds. I translate your local address for global travel. I know the map of the entire internet."
The Firewall
"I protect. I decide who enters and who is cast into the void. I remember every conversation, watching for threats."
The Load Balancer
"I distribute. I make one address become a thousand servers. I ensure no machine is overwhelmed."
Each device operates at a specific layer of the network stack. Each has specialized hardware optimized for its task. Together, they form the infrastructure that makes modern life possible — email and streaming, banking and social media, remote work and online education.
The next time you click a link, remember: you're not just making a request. You're launching a traveler on an epic journey through the machines of the internet. In the quarter-second it takes, that packet passes through more sophisticated technology than existed in all of human history before 1960.