The internet's first message was "lo" — then the system crashed
October 29, 1969: UCLA to Stanford, Charley Kline's notebook, packet switching, and how a failed LOGIN became the ancestor of everything online.
The internet's first word was "lo".
It was not a greeting, and nobody planned it. At 10:30 in the evening on October 29, 1969, a UCLA student named Charley Kline sat at a terminal trying to log into a computer 560 kilometers away at the Stanford Research Institute — the first attempt to send a message between the first two nodes of a new network called ARPANET. He typed L. He typed O. Then the system crashed.
They restarted it and completed the login: LOGIN. The first message on the ancestor of the internet was a half-word followed by a reboot. Kline logged the event in a notebook that still exists. The crash was temporary. The network was not.
Why did the Pentagon build this?
Fear, mostly, and a smarter kind of fear than science fiction suggests. In the late 1960s the US Defense Department's advanced research agency, ARPA, funded computers at universities across the country. Each machine was expensive, and researchers had to travel or mail punched cards to use someone else's. A young program manager named Larry Roberts was tasked with connecting them so people could share.
The popular myth that ARPANET was built to survive nuclear war is half-true at best. Packet switching — the idea of chopping data into small pieces that find their own paths — did come partly from Cold War thinking about networks that keep working when parts get destroyed. Paul Baran at RAND and Donald Davies in Britain independently invented versions of it. But ARPANET itself was funded to share scarce computing resources among scientists, not to outlast missiles. The nuclear-hardened story stuck because it sounds better than "professors wanted remote access to expensive mainframes".
How did packets change everything?
Before packet switching, long-distance data used dedicated circuits — like a phone call that reserved a wire for the whole conversation, even during silences. Packets flipped that: chop a message into labeled chunks, send them independently, reassemble at the far end. The line is shared. Congestion is handled by waiting, not by locking a circuit. If one path fails, packets try another.
The first ARPANET nodes used refrigerator-sized Interface Message Processors — IMPs — built by a Cambridge company called Bolt Beranek and Newman. UCLA was node one. Stanford Research Institute was node two. Within weeks, UC Santa Barbara and the University of Utah joined. By 1971 there were about fifteen nodes. Email arrived almost by accident in 1971 when Ray Tomlinson adapted a local messaging program to send between machines, choosing the @ sign to separate user from host. He later said he could not remember the first email's text — probably something forgettable — but the @ stuck forever.
What happened after "lo"?
The network grew, and so did the politics of who controlled it. In the 1970s, Vint Cerf and Bob Kahn designed TCP/IP — rules for networks to talk across different kinds of networks. On January 1, 1983, ARPANET switched over to TCP/IP in a cutover nicknamed Flag Day. That date is as close as the internet has to a birthday.
By the late 1980s ARPANET was being retired as the NSFNET and commercial networks took over. The World Wide Web arrived in 1991. Dial-up, then broadband, then phones. The original UCLA IMP is in a museum. Charley Kline's notebook is a historical artifact.
Why does a failed login still matter?
Because every Zoom call, every map load, every payment confirmation is a descendant of that broken LOGIN attempt. The design ideas — packets, no single central switch, open protocols — still run underneath TikTok and banking apps. When people say "the internet was built to be resilient", they mean this lineage: a research network that expected machines to fail, links to drop, and messages to find another way around.
The first word was incomplete. The system crashed. They tried again. That is also the story of the internet itself — unfinished, interrupted, restarted — and somehow, fifty-plus years later, still sending.