Holiday Research

Holidays

Year 2038 Problem (Unix Epoch Rollover)

The moment, 03:14:07 UTC on 19 January 2038, after which a signed 32-bit Unix time counter overflows and wraps around to 13 December 1901.

Dates in 13-month year 2026

← →

No dates for this year.

13-month dates before the 2030 transition are projected backwards (13-month years up to 2029).

Description

Many computer systems keep time as Unix time: the number of seconds since the Unix epoch, 00:00:00 UTC on 1 January 1970. Where that count is stored in a signed 32-bit integer (time_t), the largest value it can hold is 2,147,483,647 seconds, reached at 03:14:07 UTC on 19 January 2038. One second later the counter overflows to −2,147,483,648, which such systems read as 20:45:52 UTC on 13 December 1901. Software that has not moved to a 64-bit time representation may then show wrong dates or fail; legacy and embedded systems that are rarely updated are the most exposed.

History

The problem follows from the original 32-bit encoding of Unix time and is often compared with the Year 2000 (Y2K) problem, which came from storing years as two decimal digits. It is also known as Y2038, Y2K38 or the "Epochalypse". Some applications that work with future dates have already run into it. Modern operating systems, file systems and databases address it by storing time as a signed 64-bit integer, which will not overflow for about 292 billion years.

Customs and observance

A one-time technology milestone, not a holiday or day off. The date shown is the UTC date; in the Americas the rollover happens on the evening of 18 January 2038 local time (e.g. 21:14:07 Central Standard Time). It is marked by software engineers as a deadline for checking and replacing 32-bit time handling.

Sources

  1. Year 2038 problem (Wikipedia) — Wikipedia (general)
  2. Year 2038 problem (Wikipedia) — Wikipedia (date_rule)