Unix Rollover Checker
See Year 2038, Y2K, NTP era, GPS week, and 64-bit time limits with exact UTC dates.
Unix epoch rollovers, Year 2038, and related time limits
This reference table lists well-known time-storage overflow and rollover instants: signed and
unsigned 32-bit Unix seconds, the Year 2000 two-digit year issue, NTP era boundaries, legacy
GPS week counters, 64-bit time_t, JavaScript Date limits, and
Windows FILETIME range. Change the reference instant to see how far each event is from your
chosen date.
Why these dates matter
- 2038-01-19: Signed 32-bit
time_toverflows in many C libraries. - 2106-02-07: Unsigned 32-bit second counters stop instead of going negative.
- 2036-02-07: NTP 32-bit era rollover (seconds since 1900-01-01).
- 2038-11-21: 10-bit GPS week counter wrap (legacy receivers).
For live timestamp conversion, use the Epoch Unix Timestamp Converter or Unix Nanoseconds Converter.
Frequently Asked Questions
Is Year 2038 still a problem?
Modern servers use 64-bit time_t, but embedded devices, old binaries, and legacy schemas with 32-bit integers can still fail after the 2038 instant. This table helps you plan migrations and test fixtures.
Why are some rows approximate?
FILETIME and far-future 64-bit limits are shown with rounded calendar years because the exact human-readable date is not meaningful for engineering decisions.
Does the tool call an API?
No. All dates are computed locally from fixed constants and your reference ISO input.