the story of a little packet, told in 214 milliseconds
an original story · pennycodes.org
chapter one · 0.000 ms
Born at the press of a key
The packet was born the instant Amara pressed Enter.
One moment there was nothing, and the next there was a small, determined bundle of
bits with a job to do. It knew exactly three things about itself: where it came from,
where it was going, and that it was very, very small. Five hundred and twelve bytes,
to be precise, wrapped in neat headers like a parcel wrapped in brown paper, with the
address written on the outside in a language only routers can read.
Its destination was a server on the other side of the ocean. Its mission was almost
comically modest: arrive, tap the server on the shoulder, and say are you
there?
The packet did not know what an ocean was. It would learn tonight.
chapter two · 0.4 ms
The keeper of the house
The first stop was the router in the hallway, a plastic box with four green eyes
that never slept. Every traveler leaving the house had to pass its desk.
"Destination?" the router asked, though it was already reading the address off the
packet's wrapping.
"Across the ocean," said the packet, trying to sound braver than it felt.
The router had seen millions like this one. Photographs, phone calls, half of a
video of somebody's cat. It stamped the packet's wrapping with a new return address,
the house's public one, because the world outside didn't need to know which room the
packet had come from. Then it pointed one of its antennas at the door.
"Next hop is the street cabinet. Stay in line, don't dawdle, and if you get lost,"
the router said, in the tone of something that had said this many times,
"you won't. Something else will be sent instead. That's how this works."
The packet decided not to think about that too hard.
chapter three · 9 ms
The river of light
Beneath the street, the packet became light.
This is the part nobody tells you: a packet doesn't travel through a fiber
optic cable so much as it becomes a rhythm of flashes inside a strand of glass
thinner than a hair. Off and on, off and on, ninety thousand times just to spell its
own name. The packet found it exhilarating. It raced past junction boxes and under
intersections, joined at every merge by thousands of strangers: a slice of someone's
playlist, a weather report, an entire spreadsheet traveling in forty-one pieces that
kept calling out to each other to stay together.
At the edge of the city, the ground tilted downward, and a sign in the language of
routing tables said the thing the packet had been both dreading and hoping for:
NEXT HOP: SUBMARINE CABLE, 6,400 KILOMETERS
chapter four · 12 ms
Under the whales
The ocean, it turned out, was mostly dark and entirely enormous.
The cable lay on the seabed like a sleeping serpent, armored in steel and tar,
no thicker than a garden hose. Inside it, the packet flew. Above it, somewhere in
the black, whales sang to each other across distances the packet was crossing in
the time between two notes.
Every eighty kilometers the cable swelled into a repeater, a little lighthouse on
the seafloor that caught the packet's fading flashes and threw them onward, bright
again. The packet counted them to keep calm. Fourteen. Thirty. Fifty-one.
It thought about what the router had said. If the ocean swallowed it, no one would
come looking. The laptop would simply shrug after a second of silence and send a
sibling. The packet found, to its own surprise, that this made it feel not smaller
but braver. It was allowed to be lost. Which is exactly the sort of thing that makes
anyone hold on tighter.
chapter five · 107 ms
The city that hums
The data center did not look like the end of a journey. It looked like a warehouse
that had swallowed a galaxy: aisle after aisle of black racks, each one freckled
with green and amber stars, the whole building breathing through fans in one long,
cold exhale.
The packet was checked at the door by a firewall with no sense of humor, weighed,
inspected, and waved through. A load balancer glanced at it and flicked it, with
the boredom of infinite practice, toward rack 40, server 12, where a process had
been waiting its entire life, which was four days, for exactly this kind of visitor.
The packet delivered its whole message. Are you there?
The server, which answered this question two hundred thousand times a day and had
never once found it tedious, wrote a reply on a fresh packet:
YES. I AM HERE. 64 BYTES. SEQ=1. TTL=52.
chapter six · 214 ms
The reply
The journey home is always faster in the telling.
The reply retraced the ocean, surfaced in the city, ran the river of light in
reverse, and presented itself at the hallway router, which recognized the stamp it
had made a fifth of a second earlier and knew exactly which room to deliver it to.
On the laptop screen, in a small black window, one line of text appeared. Amara
glanced at it for half a second, muttered "okay, so the network's fine," and went
back to blaming the printer.
She would never know about the whales.
But somewhere in the kernel's logs, for a little while, there was a record that a
small packet had crossed an ocean, touched another machine, and made it home,
all between two blinks of a cursor. The internet is made of nothing else: billions
of tiny journeys, every second, each one hoping only to arrive.
⌁ the end
About this story
An original story published on pennycodes.org. The technical details are real:
this is faithfully how a ping travels, give or take some poetic license about
what routers say out loud. Illustrations are hand-drawn SVG, so this entire site,
pictures included, is four small text files served from a private Amazon S3 bucket
behind CloudFront, with HTTPS and a firewall in front.