Time now · 4 min read
The year 2038 problem is being worked on now
Why a date more than a decade away already matters to the software and devices we use today.
On 19 January 2038, a common older way of representing time runs out of room. This is not a prophecy that every computer will stop: it is a compatibility problem that engineers are actively identifying and replacing in long-lived systems.
A number with a limit
Some systems represent an instant as the count of seconds since 1 January 1970 in a signed 32-bit integer. The largest such number corresponds to 03:14:07 UTC on 19 January 2038. One second later, an uncorrected signed 32-bit count can overflow and be interpreted as a much earlier date. The exact symptom depends on the system and its software.
Many modern environments use wider time representations and will not fail in this particular way. But older devices, firmware, file formats and interfaces may still carry the narrower assumption. A 64-bit computer can even exchange data with a legacy component that cannot represent a later date.
Why work begins before 2038
The deadline is not only relevant on the day itself. A device calculating a 15-year expiry date or storing a future appointment can reach an unrepresentable value years early. Industrial equipment and embedded devices may remain in service for decades, so replacements and tests have long lead times.
At FOSDEM 2026, open-source engineers discussed how the rollover affects software and the work needed to find remaining assumptions. Their ongoing work is a reminder that the risk is specific and testable, not a universal internet shutdown. Inventories, interface audits and boundary-date tests are more useful than panic.
The practical response
For everyday users, keep devices supported and install vendor updates, particularly for equipment you expect to use for a long time. You do not need to change your phone's date to test it; that can cause unrelated problems with certificates and accounts.
For teams maintaining software, check every place a future timestamp crosses a boundary: persistent data, file formats, network protocols, library calls and embedded firmware. Test dates on both sides of the limit, including how old and new components communicate. The lesson is broader than this one date: a time format is an engineering contract with a lifespan.
Sources & further reading
These sources provide the underlying standards or research. This guide is educational and is not medical advice.