They designed them not to fail, not to last forever.
Voyager 1 operates on three 1970s computer systems with just 69 kilobytes of memory each—smaller than a phone photo—yet still receives and executes commands from Earth after nearly 50 years. A corrupted memory chip in 2023 disabled data transmission for five months; engineers remotely diagnosed and fixed it by dividing software into pieces and relocating code to unused memory sections.
- Voyager 1's three main computer systems each have 69 kilobytes of memory
- A memory chip failure in November 2023 corrupted about 3 percent of the Flight Data System memory
- Engineers remotely repaired the damage by April 20, 2024, dividing software into pieces and relocating code to unused memory sections
- The backup Flight Data System computer failed in 1981, leaving the spacecraft dependent on a single unit for over 40 years
Voyager 1, humanity's most distant spacecraft, successfully recovered from a memory chip failure using innovative software workarounds on its 69-kilobyte computer systems—a testament to 1970s redundancy design.
Voyager 1 is running on a computer with less memory than a single photograph on your phone. Each of its three main computer systems, all built in the 1970s, carries about 69 kilobytes of storage—roughly the size of a heavily compressed thumbnail. Nearly fifty years after launch, these machines still listen for commands from Earth and execute them, a fact that upends the assumption that hard problems require more computing power.
The spacecraft does not think with a single brain. Three separate systems divide the work. One interprets instructions from Earth and manages the spacecraft's sequences and safety protocols. Another collects and packages the science and engineering data before sending it home. The third controls the spacecraft's orientation and keeps its antenna pointed toward Earth. Together, they run a mission across more than 24 billion kilometers on memory measured in kilobytes, not gigabytes.
The designers knew that parts would fail. Suzanne Dodd, the Voyager project manager, has described a spacecraft built with "nearly everything redundant." Two spacecraft meant redundancy built in from the start. Major systems and many critical components were duplicated so the mission could continue after a failure. But redundancy has limits. Voyager 1 originally carried two Flight Data System computers. The backup failed in 1981, leaving the spacecraft dependent on a single unit. For nearly five decades, engineers have kept an aging machine running by working around failed parts, scaling up the small problem of keeping an old car alive to the immense problem of keeping the most remote machine ever made functional.
On November 14, 2023, Voyager 1 stopped sending usable information. Instead of science and engineering data, it transmitted a repeating pattern of meaningless ones and zeros. The spacecraft still received commands and appeared otherwise healthy, but its Flight Data System could no longer package information correctly. A diagnostic command sent in March 2024 produced a memory readout that let engineers identify the damage. About three percent of the Flight Data System memory had been corrupted, probably because a single memory chip had failed—damaged either by an energetic particle from space or simply deteriorated after more than 46 years of operation.
The repair ran into the same constraint that makes Voyager remarkable. Linda Spilker, the Voyager project scientist, identified the core problem plainly: "The size of the memory was the biggest challenge in this anomaly." The failed chip contained part of the software responsible for packaging data, but no single undamaged section of memory was large enough to hold all of that code. Engineers divided it into smaller pieces and searched for unused sections where each piece could be stored. They also freed space by identifying processes and data modes the spacecraft no longer needed—some created for parts of the planetary mission that ended decades earlier. The first relocated section of code was transmitted on April 18, 2024. It reached Voyager about 22.5 hours later. On April 20, the spacecraft returned readable engineering data for the first time in more than five months. A team on Earth had diagnosed a probable hardware failure in a computer more than 24 billion kilometers away, then rewritten its software to route around the damaged memory. Each meaningful test took almost two days to confirm. There was no possibility of physically examining or touching the machine.
The easy story is that engineers built things better in the 1970s. The more careful reading is about a way of thinking. John Casani, the Voyager project manager through launch, said the team "didn't design them to last 30 years or 40 years, we designed them not to fail." That distinction matters. Designing something not to fail means assuming that individual parts eventually will. It means creating alternative routes, duplicated systems, and enough flexibility for engineers to respond to problems that cannot yet be predicted. That flexibility is exactly what the 2024 repair used. Engineers divided and relocated damaged software using small margins of memory left by people who could not have known what the eventual emergency would be. They knew only that failures were possible and that the spacecraft needed room to survive them.
Voyager is now so old that every intervention carries increasing risk. Dodd has said that "all the decisions we will have to make going forward are going to require a lot more analysis and caution than they once did." The repair did not prove that Voyager's hardware is invincible. Parts have failed before, and more will fail as the spacecraft continues to age. What it proved is that a group of engineers in the 1970s built enough redundancy and flexibility into machines with only kilobytes of memory for another group of engineers, nearly half a century later, to work around a failure none of them could have predicted, aboard a spacecraft no human being will ever touch again.
Notable Quotes
The size of the memory was the biggest challenge in this anomaly.— Linda Spilker, Voyager project scientist
We didn't design them to last 30 years or 40 years, we designed them not to fail.— John Casani, Voyager project manager through launch
The Hearth Conversation Another angle on the story
Why does it matter that Voyager runs on such tiny memory? Couldn't they have just built it with more?
In the 1970s, every kilogram mattered. Every watt of power mattered. They launched with what they needed for the mission they could imagine. The real insight is that they left room for the mission they couldn't imagine.
But the backup computer failed in 1981. Doesn't that mean the redundancy failed?
It did fail. But the designers had already thought about that possibility. They built the remaining systems to keep working even after losing pieces. It's like designing a bridge that can still stand if one cable snaps.
How did they even diagnose the problem from so far away?
They sent a command asking the spacecraft to read its own memory and send back what it found. That readout showed them exactly which part was corrupted. Then they had to solve a puzzle: how do you fix software when you can't fit the whole thing in the space available?
And they just... divided it up and scattered it around?
Yes. They found unused sections of memory—code from the planetary flybys that ended in the 1980s—and moved the broken pieces there. Each test took 22.5 hours each way to confirm it worked.
That sounds incredibly risky. What if they broke something else?
It was risky. That's why Dodd says every decision now requires much more caution. The spacecraft is old. Every time you touch it, you're gambling that the intervention doesn't cause a new failure. But doing nothing meant losing the mission entirely.
So the real story is that 1970s thinking saved the mission in 2024?
Exactly. Not because the hardware was perfect, but because the designers assumed it would fail and built in the flexibility to survive failures they couldn't predict.