The Year 2038 problem is a documented software-design failure in systems that store Unix time—the seconds since 00:00:00 UTC on 1 January 1970—in signed 32-bit integers. At 03:14:07 UTC on 19 January 2038, the value reaches 2,147,483,647. One second later it overflows to −2,147,483,648, which systems can interpret as 20:45:52 UTC on 13 December 1901. Applications that use dates for authentication, scheduling, databases, logging, or safety-related control could therefore calculate failures or process events in the wrong order.
The risk is concentrated in legacy and embedded equipment that is difficult to update, including some transportation, communications, networking, and industrial systems. An early manifestation appeared in AOLserver in May 2006: a one-billion-second default timeout generated dates beyond the 2038 limit, causing requests to resolve to dates in the past until operators changed the configuration. The source also records failures in Oracle Access Management on 17 March 2022 and reports that Microsoft Exchange anti-malware functions broke on 1 January 2022 after a timestamp-parsing error; Microsoft published an automated fix on 5 January. Modern 64-bit systems generally use signed 64-bit timestamps, but incompatible data structures and residual 32-bit code mean remediation requires testing or replacement rather than a universal patch.