The standard for tracking time as the number of seconds since **January 1, 1970** (known as the **Unix Epoch**) was adopted in the early 1970s. It was not established by a formal government agency but rather by the engineers at **Bell Labs**—specifically **Dennis Ritchie** and **Ken Thompson**—during the development of the Unix operating system.
### History and Evolution
The standard was finalized around **1973** after several earlier iterations:
* **Original Epoch (1971):** The first edition of the *Unix Programmer’s Manual* (November 3, 1971) defined time as the number of **sixtieths of a second** (60 Hz) since **January 1, 1971**.
* **The Problem:** Because the system used a 32-bit integer to track these 1/60th-second intervals, the clock would have “overflowed” (run out of numbers) in only about **2.5 years**.
* **The Solution:** To extend the system’s lifespan, the engineers changed the measurement unit from 60 Hz to **1 Hz** (one full second). At this time, they also reset the starting point to the beginning of the decade, **January 1, 1970**, to make it a more “rounded” and convenient date.
### Why January 1, 1970?
The choice of this specific date was primarily a matter of **technical convenience** rather than a significant historical milestone:
* **Longevity:** By measuring in full seconds from 1970, a 32-bit signed integer could track time for approximately **136 years** (reaching until the year 2038).
* **Neutrality:** Engineers wanted a “neutral” starting point that was close to the current time but wouldn’t overflow for a significant period.
* **Simplicity:** It represented the start of the decade in which the system was being actively developed and refined.
### Formal Standardization
While it began as an internal convention at Bell Labs, the Unix Epoch was eventually codified into international standards:
* **POSIX:** The Portable Operating System Interface (POSIX) standards, first published in **1988**, formally defined “Seconds Since the Epoch” based on the January 1, 1970, 00:00:00 UTC benchmark.
* **Widespread Adoption:** Due to the success of Unix-based systems, this method of timekeeping was adopted by most modern operating systems (including Linux and macOS), programming languages (like C and Java), and databases.