Troublesome Dates
Dates that cause trouble with computers or are significant to computers.
Issues related to dates in the far future will be collected somewhere else.
Also see Troublesome Times.
Year 24
January 1, 1601
September 3, 1752 to September 13, 1752
September 3, 1752 to September 13, 1752 were skipped when switching from Julian calendar to Gregorian calendar.
November 17, 1858
Why is Wednesday, November 17, 1858 the base time for OpenVMS?
January 0 1900 (December 30, 1899)
Excel stores dates and times as a number representing the number of days since 1900-Jan-0.
February 29, 1900
This is because Excel behaves as if the date 1900-Feb-29 existed. It did not.
December 13, 1901
The next second this counter can represent is 20:45:52 UTC on December 13, 1901.
December 31 1903 / January 0, 1904
…but Excel can also treat the date portion of a serial date as the number of days since 1904-Jan-0.
January 1, 1904
old Macintosh epoch
1912
start of Taiwan calendar
December 31, 1927
January 1, 1970 (December 31, 1969)
January 1, 1971
January 4, 1975
On 4 January 1975, the 12-bit field that had been used for dates in the DECsystem-10 operating systems overflowed.
April 4, 1975
…but the developer who fixed the bug decided to be a bit clever: He chose April 4, 1975, the date of Microsoft’s founding.
1978
January 6, 1980
GPS epoch
September 18, 1989
2^16 days since January 1 1900
September 18, 1993
- https://www.benshoof.org/blog/sierras-macintosh-timebomb
- https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1993
firstDIVUWithA8C0Overflows = 2831155200
January 1 1904 (old Macintosh epoch) + firstDIVUWithA8C0Overflows = September 18 1993
October 29, 1995
November 2, 1997
Around April First of this year reports started circulating in the Apollo Usenet newsgroup of a “date bug” in Domain/OS that would render all Apollo workstations useless after November 2, 1997.
In[178]:= DateList[{1980, 1, 1}];
DatePlus[%, Quantity[ (4*2^47)/10^6 , "Second"]]
Out[179]= {1997, 11, 2, 14, 59, 13.4213}
-
https://web.archive.org/web/19970625170249/http://www.interworks.org/Tech/apollonov2/
-
https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1997
1999
2000
Y2K
January 1, 2001
September 9, 2001
January 2, 2006
May 13, 2006
It sound like that could equate to “Sat May 13 02:27:28 BST 2006”, or 1147483648 seconds since epoch, which makes it exactly 1,000,000,000 seconds until expiry of 32 bit time. Coincidence? Seems too strange as to a computer that is not a nice round number.
March 28, 2007
- https://www.benshoof.org/blog/sierras-macintosh-timebomb
- https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2007
firstDIVUWithA8C0Overflows = 2831155200
January 1 1904 (old Macintosh epoch) + firstDIVUWithA8C0Overflows = September 18 1993
September 18 1993 + 5000 days = May 28 2007
December 1, 2007
592 weeks before next GPS week rollover
June 14, 2008
…it means that 2008-06-14 23:29:20 UTC is, in a strange sense, “HTTP time”. If you see either that number or that date (with possible adjustments for your local time zone) showing up in your life inexplicably, this might just be why.
December 31, 2008
The bug would be triggered on the last day of any leap year
2010
November 2010
-
http://venturebeat.com/2010/11/01/iphone-daylight-savings-time-alarm-bug-plagues-users-in-europe-us/
-
https://osxdaily.com/2010/11/06/the-iphone-daylight-savings-time-alarm-bug-and-how-to-fix-it/
December 12, 2010
434 weeks before next GPS week rollover
2011
January 1, 2011
-
http://www.macnn.com/articles/10/12/31/reports.of.alarm.issues.continue.to.plague.ios.4/
-
http://www.macrumors.com/2010/12/31/iphone-clock-bug-prevents-alarm-triggers-after-new-years/
June 30, 2012
June 30, 2012 leap second
-
http://arstechnica.com/business/2012/07/one-day-later-the-leap-second-v-the-internet-scorecard/
-
http://blog.wpkg.org/2012/07/01/java-leap-second-bug-30-june-1-july-2012-fix/
-
http://www.reddit.com/r/programming/comments/y3mxv/clock_monotonic_avoiding_problems_with_leap/
-
https://www.somebits.com/weblog/tech/bad/leap-second-2012.html
January 2013
-
http://arstechnica.com/apple/2013/01/apple-says-do-not-disturb-scheduling-is-broken-until-january-7/
March 10, 2013
Daylight Saving Time begins on Sunday March 10, 2013
August 11, 2013
2^32 deci-seconds from January 1, 2000
-
http://www.reddit.com/r/programming/comments/1mtsoy/nasa_officials_declared_the_deep_impact_mission/
-
https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2013
ALSO 295 weeks before next GPS week rollover
End of 2014
ISO week vs. Gregorian week
January 1, 2016
August 16, 2017
86 weeks before next GPS week rollover, but this is interesting because it is not EXACTLY on the week.
August 12 2017 is the actual point of 86 weeks before the next rollover.
So this issue is (86 weeks before the next rollover) + 4 days.
December 2017
“Month 13 is out of bounds”
October 6, 2018
October 21, 2018
GPS Week Number reached 1,000
March 16-17, 2019
3 weeks before next GPS week rollover
April 6, 2019
-
https://twitter.com/ChinaAvReview/status/1114802018919411712
-
https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Second_GPS_rollover
April 30, 2019
November 2, 2019
30 weeks after last GPS week rollover
End of 2019
ISO week vs. Gregorian week
2020
Y2K20
-
https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Classic_Mac_OS
-
https://twitter.com/nick_guerrera/status/1394435349980405762
-
This Year’s Y2K20 Bug Came Directly From ‘A Lazy Fix’ to the Y2K Bug
-
https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2020
February 29, 2020
2020 leap day bugs
December 19-20, 2020
89 weeks after last GPS week rollover
2021
June 20, 2021
115 weeks after last GPS week rollover
October 23, 2021
January 1-2, 2022
143 weeks after last GPS week rollover
-
https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2022
-
https://www.the-triton.com/2022/03/gps-week-number-rollover/
-
https://panbo.com/2022-gps-rollovers-furuno-airmar-jrc-and-who-else/
-
https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=753&dispmid=965
-
https://jalopnik.com/honda-clocks-are-stuck-20-years-in-the-past-and-this-mi-1848306970
May 14-15 2022
162 weeks after last GPS week rollover
September 17-18 2022
180 weeks after last GPS week rollover
March ?, 2023
February 29, 2024
Leap day
2025
2028
-
https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2028
-
http://www.3kranger.com/HP3000/mpeix/en-mpe75/Beechglen2028/ch02s03.html
2032
February 7, 2036
January 1 1900 + 2^32 Second == February 7 2036
January 19, 2038
With 32 bit signed integers, Unix time will overflow on: 03:14:08 UTC January 19, 2038
November 20, 2038
GPS Week rollover
February 6, 2040
old macintosh calendar expires
September 18, 2042
2043
Microsoft Exchange update format
changing to unsigned long
January 19, 2048
2069
2079
2080
2100
2106
unsigned 32-bit count of seconds (also) since 1970
With 2^5 = 32 bit unsigned integers, Unix time will overflow on: 06:28:16 UTC February 07, 2106
2108
2137
GPS 13-bit week rollover
-
https://lobste.rs/s/tdalbi/gpsd_time_will_jump_back_1024_weeks_at
-
https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2137
November 4, 2153
2232
2262
April 4, 2262
2262-04-11 23:47:16 UTC is when a system with a signed 64 bit number to store Unix time shifted left with nanoseconds added to it runs out of time.
2286
July 21, 2554
2554-07-21 23:34:33 UTC is when the same scheme but with an unsigned 64 bit number runs out of time.