The First Computer Bug Was a Real Moth

If you have ever stared at a misbehaving circuit at two in the morning, muttering about the "bug" you cannot find, you are part of a lineage that runs back to a very literal insect. On September 9, 1947, engineers working on Harvard's Mark II computer opened up the machine, found a moth wedged inside a relay, and taped it into their logbook. The note beside it reads: "First actual case of bug being found." It is one of the most charming artifacts in the history of computing, and it carries a surprisingly practical lesson for anyone who builds connected hardware today.

What actually happened in 1947

The Mark II was an electromechanical monster: a room-sized calculator built from thousands of relays, switches that physically clacked open and closed to represent ones and zeros. On that September day the machine was producing errors, and the operators -- part of the U.S. Navy computing effort that Grace Hopper worked in -- traced the fault to Relay #70 in Panel F. Inside was a moth, its wings shorting across the contacts. They removed it, taped it into the logbook at 15:45, and recorded the now-famous line. That page, moth still attached, lives today in the Smithsonian's National Museum of American History.

Hopper loved telling the story for the rest of her career, which is why her name is forever attached to it. She is often credited with coining "bug" and "debugging" because of that moth, but the honest history is a little different, and the difference is the interesting part.

The word "bug" was already old

Engineers had been calling faults "bugs" for decades before 1947. Thomas Edison used the term in an 1878 letter to describe the little glitches and "difficulties" that show up when a new invention meets the real world. By the early twentieth century "bug" was common shop-floor slang among electrical and telephone engineers. So the moth did not invent the word. What made the logbook entry so memorable is the joke buried in it: "first actual case of bug being found" is funny precisely because the team already used "bug" to mean an abstract fault. Here, for once, the bug was a literal one you could hold in your fingers.

That distinction between the abstract fault and the physical cause is exactly what makes the story worth keeping around.

Why this still matters for IoT and embedded work

Modern IoT development lives in the same gap the Mark II operators fell into. When a connected sensor node starts dropping readings, the instinct is to assume a software bug -- a logic error in the firmware, a bad edge case in the parser, a race condition in the task scheduler. Often that is right. But embedded systems are physical in a way that pure software is not, and the fault is frequently something the compiler will never see: a cold solder joint, a floating input pin that needs a . We are happy to help you find the moth.