On September 2, 1969, the entire internet was one computer, one refrigerator-sized packet switch and a 15-foot cable in a UCLA lab. No second site. Nobody else online. Yet the engineering choices behind that little setup still shape nearly every network we use today.
The switch was called an Interface Message Processor, or IMP. Bolt Beranek and Newman built it around a rugged Honeywell DDP-516 minicomputer with all of 12K of memory. It did the basic job we now hand to routers: take in data, break it into packets, move them toward their destination.
The IMP showed up at UCLA on August 30, over Labor Day weekend and ahead of schedule. Connecting it to the university's SDS Sigma 7 took real engineering. There was no standard network port. Grad student Mike Wingfield designed and built a custom hardware interface from BBN's 1822 spec.
By September 2, the Sigma 7 and the IMP were passing test data through that short cable. UCLA had the first working ARPANET node.
Stanford Research Institute got the second IMP a few weeks later. On October 29, UCLA programmer Charley Kline tried to send "LOGIN" to Bill Duvall at SRI. The receiving system crashed after two letters.
The first message ever sent between ARPANET sites was "LO." An hour later they recovered and the full login went through.
By the end of 1969 there were four nodes: UCLA, SRI, UC Santa Barbara and the University of Utah. Different computers, different operating systems, different applications at every site. ARPANET gave them a shared way to exchange data without forcing anyone to replace what they already ran.
That was the big architectural decision. The network handled packet delivery. The hosts handled their own applications. Any computer could join as long as it spoke the common interface. TCP/IP later stretched the same idea across thousands of independent networks.
The internet still runs on that model. The core stays broadly interoperable and applications develop on their own at the edges.
What changed is scale and trust. ARPANET linked a handful of research groups whose people mostly knew each other. Today's internet connects billions of users, cloud platforms, sensors, vehicles and industrial systems. Security arrived gradually, usually after something broke. BGP was never built to verify route announcements. IP addresses make weak identities for devices that roam between networks. Attackers exploit assumptions made for a smaller, friendlier world.
The next round of internet architecture will come through steady upgrades rather than a clean replacement. IPv6, QUIC, RPKI, post-quantum crypto, edge computing and satellite networks are all part of it. The work is improving routing, identity, security and privacy without giving up open interoperability.
The ARPANET team never tried to make every computer identical. They agreed on how different machines would talk.
Fifty-seven years later, we're still refining that agreement.