~ / about
$cat README

About & methodology

epoch2038.com is an independent reference on the Year 2038 problem: what breaks when 32-bit Unix time overflows at 03:14:07 UTC on 19 January 2038, what is already fixed, and what to do about the rest. It also covers related date limits (GPS week rollover, the NTP 2036 era, 2106) and what the Y2K effort teaches.

How entries are researched

What the register labels mean

At riskFails at or before its deadline unless something is changed.
DependsSafe only with a particular version, build or setting. Check yours.
Different deadlineNot hit in 2038, but has another date limit.
Not affectedNot affected by the 2038 overflow. The reason is given.
ConfirmedVendor advisory, CVE, documented limit or demonstrated failure.
LikelyClass-level assessment: typical stacks and lifetimes put it at risk, but no public failure for a specific product yet.

Corrections

If you have evidence that changes an entry, such as an advisory, a fix, a test result or a vendor statement, please email info@epoch2038.com with a link to the source. Corrections are made on the evidence, whoever sends them.

Independence and funding

The site is free to read. It may be funded by sponsorship and by help enquiries, including referrals to specialists. Neither affects what the register says. Sponsors are listed openly, sponsor links are marked as sponsored, and any entry about a sponsor's own products says so.

Privacy

This site sets no cookies and loads no advertising or tracking scripts. Pages load one font from Google Fonts. If you email us, your message is used only to reply to you.