Modern software, embedded systems, and critical infrastructure depend on accurate and reliable timekeeping. Yet hidden limitations in how systems represent, process, and exchange time can create serious vulnerabilities as Y2036, Y2038, Y2106, and other rollover boundaries approach.
Y2038.com helps organizations identify, assess, and mitigate these risks through AI-assisted analysis tools, technical research, engineering expertise, and readiness assessment services.
Our work includes open-source tools for analyzing source code and technical documents, as well as active participation in developing industry standards for systematic time-rollover readiness.
We can help identify potential time-rollover vulnerabilities, evaluate system readiness, and develop practical mitigation strategies through expert-led assessments supported by AI-assisted analysis.
Y2038.com develops open-source, AI-assisted tools to help identify potential time-related vulnerabilities in source code and technical documentation. These tools support systematic assessment of Y2036, Y2038, Y2106, and related time-rollover risks.
Our Time Assurance Code Scanner (TACS) is an open-source, AI-assisted tool that analyzes C/C++ source code to identify potential time-related vulnerabilities, including representation limits, unsafe conversions, and rollover risks. It supports analysis of complex codebases without requiring compilation, helping developers assess Y2036, Y2038, Y2106, and other time rollover risks.
Our Time Assurance Document Scanner (TADS) is an open-source, AI-assisted tool that analyzes technical documents, specifications, and standards to identify potential time-related vulnerabilities, ambiguities, and readiness gaps. It helps engineers and organizations evaluate temporal requirements and representation boundaries that may expose systems to Y2036, Y2038, Y2106, and other time rollover risks.
TACS and TADS are freely available, open-source tools under active development. Automated findings are intended to support engineering assessment and should be reviewed and validated before making risk or mitigation decisions.
Y2038.com actively supports the development of industry standards and collaborative initiatives to address time-related vulnerabilities across software, embedded systems, and critical infrastructure.
Our Founder and CEO, John Lange, serves as Chair of the IEEE Standards Association P4150 Working Group, which is developing a recommended practice for assessing system readiness for Y2036, Y2038, and Y2106 time-rollover risks. This effort aims to establish systematic, evidence-based approaches to identifying vulnerabilities, evaluating readiness, and guiding mitigation.
Our broader industry engagement includes participation in the FIRST.org Time Special Interest Group and contributions to international cybersecurity standards activities within ITU-T Study Group 17, helping advance awareness, technical collaboration, and coordinated approaches to time-related risk management. ITU-T recently published the initial version of XSTP.epoch which provides global coordination requirements for 2038-class rollover events
Dedicated to articles on Y2038-related topics, products, and services.
Y2036 Countdown: The NTP Rollover is Now 10 Years Away Today marks an important milestone:
Y2038 Is 12 Years Away. Here Is Why It Matters. Today is January 19, 2026.
Y2038 Readiness Update – What’s Ready and What Isn’t in 2025 Abstract Y2038 is
Learn about the Y2038 problem, which systems may be affected, and why time-rollover readiness matters. Visit our FAQ page for more detailed information.
If you have other questions, please contact us.
Y2038 refers to an issue related to the way time is handled by computers. Time is often represented as the number of seconds since Jan 1, 1970. Whenever a 32-bit signed integer is used for this, the maximum value that can be represented is +/- ~68 years, 19 days from the epoch, which corresponds to Jan 19, 2038. What happens after that is system dependent, but generally not good. A computer may act as if its time got reset to Dec 1901, or possibly to the epoch of Jan 1, 1970. It may give unexpected results or crash.
Basically, any software that uses time in any way may potentially have Y2038 issues. While only a small percentage of each software component is typically affected, this is still enough to cause many problems. Embedded systems with 32-bit cores and computers running 32-bit versions of Linux and Windows and are particularly at risk, but even 64-bit computer systems may have problems. In 64-bit computer systems, time can be represented in 64-bit integers, but Y2038 issues may still exist in applications, device drivers, databases, storage systems, and network protocols.
Virtually every programming language is potentially affected by Y2038. While “C” was the initial computer language in which the problem was introduced, most other programming languages adopted the same representation for current time. Many development platforms follow the conventions established on the given platform. For example, Mac applications (prior to OSX) are susceptible to the Mac’s Y2038-like issue in the year 2040, regardless of the language used to write the application.
There may be several reasons. One reason is of course that the Y2038 event seems so far off. Being over 20 years away, there is no sense of immediate urgency to fix anything. However, this is the same type of thinking that was partly responsible for the creation of the Y2038 issue to begin with.
Another reason you may not have heard about Y2038 is probably due to the extensive media coverage that preceded Y2K. Perhaps in part due to the heightened awareness by mainstream media, the Y2K issue was almost fully mitigated prior to Jan 1, 2000. When Jan. 1, 2000 arrived, there were no catastrophes, and there was a public sense that the Y2K event had been over-hyped. In fact, it is likely that the extensive Y2K media coverage forced businesses to thoroughly and proactively address it. (Chances are, media coverage will similarly increase before 2038).
Yet another reason may be a general lack of understanding of Y2038. Y2K was fairly easy to understand, but Y2038 requires a deeper understanding about the digital representation of time in computers.
We respect your privacy. No spam, no sharing, no selling. Just valuable updates from us to you.
Copyright Y2038.com LLC – All rights reserved.