Unix Time and the Year 2038 Problem, Explained

Unix time is the number of seconds since midnight UTC on January 1, 1970, and it is how most computers, phones and servers store the time. The “Year 2038 problem” comes from older systems that keep this number in a signed 32-bit integer, which can count no higher than 2,147,483,647. That limit is reached at 03:14:07 UTC on Tuesday, January 19, 2038, which is 10:14:07 PM on Monday, January 18 in New York and 7:14:07 PM in Los Angeles. One second later, an unfixed 32-bit counter wraps around to December 13, 1901. Before that, a rounder milestone arrives soon: Unix time passes 1,800,000,000 on January 15, 2027, at 08:00 UTC. This guide explains how Unix time works, shows the rollover in your time zone, and lists the milestones to come. Every date here was computed two ways. Facts are as of November 2026.

At a glance

  • Unix time 0 = 00:00:00 UTC, January 1, 1970 (the “epoch”).
  • Signed 32-bit limit: 2,147,483,647 = 2038-01-19 03:14:07 UTC. That is 4,090 days after November 8, 2026.
  • After the limit, a signed 32-bit value wraps to −2,147,483,648 = 1901-12-13 20:45:52 UTC.
  • Unsigned 32-bit lasts until 2106-02-07 06:28:15 UTC; 64-bit lasts about 292 billion years.
  • Next round number: 1,800,000,000 on January 15, 2027, 08:00 UTC.

What Unix time is

The POSIX standard, which defines Unix systems, describes “seconds since the Epoch” as “A value that approximates the number of seconds that have elapsed since the Epoch.” It gives an exact formula that turns a UTC date and time into that number, and it adds one important rule: “each and every day shall be accounted for by exactly 86400 seconds.” So Unix time ignores leap seconds. It is the same number everywhere on Earth at the same moment: time zones only change how it is displayed.

That makes Unix time ideal for computers. Comparing two moments is a subtraction, sorting is trivial, and there is no confusion about time zones or daylight saving time. Your phone converts it to local time using the IANA time zone database only when it shows you a clock, as our time zone converter does.

Why 2038?

A signed 32-bit integer holds values from −2,147,483,648 to 2,147,483,647 (that is, −231 to 231−1). Counting seconds from 1970, the top value is reached 68 years and a few days later. One more second and the number “overflows”: the highest bit flips and the value becomes the most negative number, which a 32-bit system reads as a date in 1901. Software that relies on such a counter may show wrong dates, sort records in the wrong order, reject certificates as expired or not yet valid, or crash.

Storage Largest Unix time Date and time (UTC)
Signed 32-bit 2,147,483,647 Tuesday, January 19, 2038, 03:14:07
Signed 32-bit, one second later (wraps) −2,147,483,648 Friday, December 13, 1901, 20:45:52
Unsigned 32-bit 4,294,967,295 Sunday, February 7, 2106, 06:28:15
Signed 64-bit 9,223,372,036,854,775,807 About 292 billion years from now

The fix is to store time in 64 bits, which pushes the limit far beyond the lifetime of the Sun. Current 64-bit operating systems generally use a 64-bit time value already. The risk is in long-lived 32-bit systems: embedded controllers, older industrial and medical equipment, file formats and databases that defined a 32-bit time field years ago. Because many of these systems calculate dates in the future (loans, contracts, certificates, schedules), some meet the 2038 limit long before 2038.

When the 2038 rollover happens in your time zone

The rollover is one instant, 03:14:07 UTC on January 19, 2038. Computed with today’s time zone rules (which could change before 2038):

City Last valid second (local time)
Los Angeles Monday, January 18, 2038, 7:14:07 PM (PST)
Vancouver Monday, January 18, 2038, 8:14:07 PM (UTC−7)
New York, Toronto Monday, January 18, 2038, 10:14:07 PM (EST)
London Tuesday, January 19, 2038, 3:14:07 AM (GMT)
Paris, Berlin Tuesday, January 19, 2038, 4:14:07 AM (CET)
India Tuesday, January 19, 2038, 8:44:07 AM (IST)
Tokyo Tuesday, January 19, 2038, 12:14:07 PM (JST)
Sydney Tuesday, January 19, 2038, 2:14:07 PM (AEDT)

In North America the problem strikes on the evening of Monday, January 18. Want to watch it approach? Our countdown can count down to any date and time.

Unix time milestones

Round Unix numbers are a small tradition among programmers. The 1 billion mark passed on September 9, 2001, at 01:46:40 UTC. The next ones:

Unix time UTC New York Vancouver
1,800,000,000 Friday, January 15, 2027, 08:00:00 3:00:00 AM, Jan 15 1:00:00 AM, Jan 15
1,900,000,000 Sunday, March 17, 2030, 17:46:40 1:46:40 PM, Mar 17 10:46:40 AM, Mar 17
2,000,000,000 Wednesday, May 18, 2033, 03:33:20 11:33:20 PM, May 17 8:33:20 PM, May 17
2,147,483,647 Tuesday, January 19, 2038, 03:14:07 10:14:07 PM, Jan 18 8:14:07 PM, Jan 18

For scale: at midnight UTC on January 1, 2027, Unix time will be 1,798,761,600.

How to read and convert Unix time

  • Get the current value: on Linux or macOS, the command date +%s; in JavaScript, Math.floor(Date.now() / 1000); in Python, int(time.time()).
  • Seconds or milliseconds? A 10-digit number (like 1,800,000,000) is seconds. A 13-digit number is milliseconds, used by JavaScript and many APIs: divide by 1,000.
  • Convert to a date: on Linux, date -u -d @1800000000 prints Fri Jan 15 08:00:00 UTC 2027.
  • By hand: divide by 86,400 to get whole days since January 1, 1970; the remainder is seconds into that UTC day. 1,800,000,000 ÷ 86,400 = 20,833 days and 28,800 seconds (8 hours).
  • Show it in local time: apply the UTC offset only at the end. Use a city time zone rather than a fixed offset, so daylight saving time is handled.

Unix time, leap seconds and the 2027 change

Because POSIX counts every day as exactly 86,400 seconds, Unix time cannot represent a leap second (23:59:60). Systems either repeat a second or spread it out. That headache ends soon: the world’s measurement conference decided in October 2026 that “continuous UTC will become effective on 20 May 2027”, with no further leap seconds. After that date, Unix time and UTC should stay in step without special handling. The 2038 limit is unaffected: it is purely a question of how many bits store the number.

Is the Year 2038 problem like Y2K?

In one way yes: both come from a shortcut in how dates were stored (two-digit years for Y2K, 32-bit seconds for 2038), and both have a fixed deadline that is easy to test. The difference is where the risk sits. Y2K was mostly in business software that could be found and patched. The 2038 problem is often in devices and file formats that are hard to update, so the work is in finding them early. The practical check for any system is simple: set a test clock past 2038-01-19 03:14:07 UTC and see whether dates still sort and display correctly.

How we computed this

Each date was computed from the Unix value with Python’s datetime and checked a second way by implementing the POSIX “seconds since the Epoch” formula directly and with the GNU date command. Local times use the IANA tz database version 2026e, which assumes today’s rules continue.

Sources

Frequently asked questions

What is the Year 2038 problem?

Systems that store Unix time in a signed 32-bit integer run out of room at 03:14:07 UTC on January 19, 2038, and wrap around to a date in 1901.

What exact time does the 2038 problem happen?

The last valid second is 03:14:07 UTC on Tuesday, January 19, 2038. That is Monday, January 18 at 10:14:07 PM in New York and 7:14:07 PM in Los Angeles.

Will my phone or computer be affected?

A current 64-bit phone or computer generally keeps time in 64 bits, so its own clock is not expected to hit the 2038 limit. Apps, file formats, databases and older 32-bit devices that still store time in 32 bits can be affected.

What is Unix time right now?

About 1.79 billion seconds in November 2026. It passes 1,800,000,000 on January 15, 2027, at 08:00 UTC.

Does Unix time include leap seconds?

No. POSIX counts every day as exactly 86,400 seconds, so the 27 leap seconds since 1972 are not counted.

Is Unix time different in each time zone?

No. It is the same number worldwide at the same moment. Only the local display differs.

Similar Posts