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.

12:00 November 24, 4714 BC (Gregorian Calendar)

Beginning of the Julian Day system.

• https://en.wikipedia.org/wiki/Julian_day

epoch for HCL Domino / Notes

12:00 January 1, 4713 BC (Julian Calendar)

Beginning of the Julian Day system.

• https://en.wikipedia.org/wiki/Julian_day

epoch for HCL Domino / Notes

January 1, 45 BC

Julian Calendar takes effect.

• https://en.wikipedia.org/wiki/Julian_calendar

January 1, 1 AD

• https://en.wikipedia.org/wiki/Rata_Die

.NET DateTime

Year 24

Year 2024 confused with year 24.

• “m/d/24” instead of “m/d/2024”

March 1, 4 AD

Earliest date that Julian calendar and Gregorian calendar calculations are historically accurate.

January 1, 100 AD

LotusScript counts days from January 1, 100 AD.

• https://help.hcl-software.com/dom_designer/14.5.0/basic/LSAZ_DATES.html

October 4, 1582

Gregorian Calendar (Catholic) takes effect.

Pope Gregory XIII decreed Thursday, October 4, 1582, was followed by Friday, October 15.

October 5, 1582 to October 14, 1582

October 5, 1582 to October 14, 1582 were skipped when switching from Julian calendar to Gregorian Calendar (Catholic).

Java GregorianCalendar class skips these dates by default.

• https://docs.oracle.com/javase/8/docs/api/java/util/GregorianCalendar.html

October 15, 1582

First date that Gregorian Calendar (Catholic) is continuous.

Base for Versions 1 and 6 UUIDs.

• https://en.wikipedia.org/wiki/Universally_unique_identifier#Versions_1_and_6_(date-time_and_MAC_address)

Lilian Date

January 1, 1601

FILETIME structure in Windows starts counting from January 1, 1601.

• base for FILETIME structure

• Why is the Win32 epoch January 1, 1601?

The Gregorian calendar operates on a 400-year cycle, and 1601 is the first year of the cycle that was active at the time Windows NT was being designed.

September 2, 1752

Great Britain declared that September 2, 1752, would be followed by September 14, 1752 when switching from Julian calendar to Gregorian Calendar.

September 3, 1752 to September 13, 1752

September 3, 1752 to September 13, 1752 were skipped when switching from Julian calendar to Gregorian calendar (Great Britain).

• https://www.mentalfloss.com/article/51370/why-our-calendars-skipped-11-days-1752

• Error “Unable to interpret time or date” when entering specific dates from the year 1752

September 14, 1752

First date that Gregorian Calendar (Great Britain) is continuous.

January 1, 1753

SQL Server datetime starts counting from January 1, 1753.

• https://learn.microsoft.com/en-us/sql/t-sql/data-types/datetime-transact-sql?view=sql-server-ver16

• https://www.itprotoday.com/early-versions/inside-datetime-data

September 22, 1792

Start of French Revolutionary calendar.

January 1, 1800

SSA’s Master Beneficiary Records format

Date of Birth in some of these records is stored as days since January 1, 1800.

• https://omb.report/icr/200704-0960-012/doc/2576801

12:00 November 16, 1858

November 16, 1858 is the base of the Reduced Julian Day system.

November 17, 1858

November 17, 1858 is the base of the Modified Julian Day system.

Julian Day 2,400,000 is November 17, 1858.

The Modified Julian Day uses the following formula:

MJD = JD - 2,400,000.5

• Why is Wednesday, November 17, 1858 the base time for OpenVMS?

• https://news.ycombinator.com/item?id=21967830

December 29, 1873

Mars Sol Date

1885

time.minWall default Go is 1885.

• https://dev.to/ymotongpoo/easter-eggs-in-go-source-code-2l02

December 30, 1899

• WHY 30TH DECEMBER 1899?

December 31, 1899 (January 0, 1900)

Excel stores dates and times as a number representing the number of days since 1900-Jan-0.

The number 1 represents 1900-Jan-1

• http://www.cpearson.com/excel/datetime.htm

• https://www.explainxkcd.com/wiki/index.php/2676:_Historical_Dates

December 31, 1899 is the base of the Dublin Julian Day system.

• https://www.quadratichq.com/blog/cursed-excel-datetime-math

January 1, 1900

SQL Server

Use smalldatetime to store dates in the range from January 1, 1900, through June 6, 2079.

https://www.itprotoday.com/early-versions/inside-datetime-data

February 29, 1900

This is because Excel behaves as if the date 1900-Feb-29 existed. It did not.

• http://www.cpearson.com/excel/datetime.htm

December 13, 1901

Year 2038 Problem will manifest as showing date as December 13, 1901.

The next second this counter can represent is 20:45:52 UTC on December 13, 1901.

• https://www.theregister.com/2024/02/09/it_incident_report_the_clock/

In[21]:= DatePlus[{1970, 1, 1}, {-2^31, "Second"}]

Out[21]= {1901, 12, 13, 20, 45, 52}

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.

• http://www.cpearson.com/excel/datetime.htm

January 1, 1904

old Macintosh epoch.

• Why Do Older Macs Reset to 1904?

1912

Start of Taiwan calendar.

• http://phys.org/news/2010-06-y2k-style-bug-looms-taiwan.html

• https://en.wikipedia.org/wiki/Republic_of_China_calendar

December 31, 1927

• Why is subtracting these two times (in 1927) giving a strange result?

January 1, 1950

January 1, 1950 is the base of the CNES Julian Day system.

January 1, 1958

January 1, 1958 is the base of the CCSDS Julian Day system.

May 24, 1968

May 24, 1968 is the base of the Truncated Julian Day system.

December 31, 1969

January 1, 1970

Unix epoch

• Unix epoch

• http://arstechnica.com/apple/2016/02/64-bit-iphones-and-ipads-get-stuck-in-a-loop-when-set-to-january-1-1970/

• https://www.explainxkcd.com/wiki/index.php/2676:_Historical_Dates

JavaScript Date

EXT4 File Timestamps

January 1, 1971

• original Unix epoch

January 4, 1975

On 4 January 1975, the 12-bit field that had been used for dates in the DECsystem-10 operating systems overflowed.

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1975

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.

• https://devblogs.microsoft.com/oldnewthing/20160209-00/?p=93002

1978

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1978

January 1, 1980

Epoch for Apollo Computer’s Domain/OS operating system

January 6, 1980

GPS epoch

September 18, 1989

2^16 days since January 1 1900

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1989

September 18, 1993

• Sierra’s Macintosh Timebomb
• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1993

firstDIVUWithA8C0Overflows = 12 * 60 * 60 * 16^^10000

January 1 1904 (old Macintosh epoch) + firstDIVUWithA8C0Overflows = September 18 1993

October 29, 1995

Daylight Saving Time change loop

• http://rachelbythebay.com/w/2020/10/07/wintime/

November 2, 1997

In Apollo Computer’s Domain/OS operating system, absolute time was stored as a signed 48-bit integer representing the number of 4-microsecond units since 1 January 1980. This value overflowed on 2 November 1997, rendering unpatched systems unusable.

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[1]:= DatePlus[{1980, 1, 1}, {(4 * 2^47)/10^6, "Second"}]

Out[1]= {1997, 11, 2, 14, 59, 13.4213}

• https://web.archive.org/web/19970625170249/http://www.interworks.org/Tech/apollonov2/

• https://web.archive.org/web/20230523005757/https://jim.rees.org/apollo-archive/date-bug

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1997

1999

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_1999

2000

Y2K

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2000

January 1, 2000

January 1, 2000 is the base of the Modified JD2000 system.

January 1, 2001

• https://www.netmeister.org/blog/epoch.html

September 9, 2001

• Unix Tick Tocks to a Billion

• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2001

• http://rachelbythebay.com/w/2024/02/07/feedback/

January 2, 2006

• This magic time is Monday, January 2, 15:04:05, 2006

• https://go.dev/src/time/format.go

May 13, 2006

• http://taint.org/2006/07/20/171844a.html

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 = 12 * 60 * 60 * 16^^10000

January 1 1904 (old Macintosh epoch) + firstDIVUWithA8C0Overflows = September 18 1993

September 18 1993 + 5000 days = May 28 2007

December 2, 2007

Sunday December 2 is beginning of GPS week 432

592 weeks before next GPS week rollover

• https://acurazine.com/forums/3g-tl-audio-bluetooth-electronics-navigation-94/navi-dash-clock-sync-megathread-update-all-should-fixed-now-630065/

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.

• http://rachelbythebay.com/w/2016/02/21/malloc/

December 31, 2008

The bug would be triggered on the last day of any leap year

• http://bit-player.org/2009/the-zune-bug

• https://lkml.org/lkml/2009/1/2/373

2010

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2010

• http://it.slashdot.org/story/10/01/06/0343252/Y201K

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

Sunday December 12 is beginning of GPS week 590

434 weeks before next GPS week rollover

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=15&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

2011

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_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://news.ycombinator.com/item?id=4188412

• http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today

• http://news.ycombinator.com/item?id=4182642

• 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/

• http://arstechnica.com/apple/2013/01/ask-ars-why-will-apples-do-not-disturb-bug-fix-itself-next-week/

March 10, 2013

Daylight Saving Time begins on Sunday March 10, 2013

• http://www.nist.gov/pml/div688/grp40/wwvb.cfm

• http://blog.appliedis.com/2013/03/06/beware-daylight-saving-time-transitions-in-dot-net/

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

Sunday August 11 is beginning of GPS week 729

ALSO 295 weeks before next GPS week rollover

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

End of 2014

ISO week vs. Gregorian week

• https://www.theguardian.com/technology/2014/dec/29/twitter-2015-date-bug

September 5, 2015

If system used by Apollo workstation was unsigned

In[3]:= DateList[{1980, 1, 1}];
DatePlus[%, Quantity[(4*2^48)/10^6, "Second"]]

Out[4]= {2015, 9, 5, 5, 58, 26.8426}

January 1, 2016

• https://news.ycombinator.com/item?id=10825774

August 16, 2017

1024 weeks since January 1, 1998

• https://jalopnik.com/hondas-and-acuras-from-1999-2004-had-their-clocks-fail-1798427017

September 17, 2017

Sunday September 17 is beginning of GPS week 943

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

December 2017

“Month 13 is out of bounds”

• https://mjtsai.com/blog/2017/12/06/month-13-is-out-of-bounds/

August 19, 2018

Sunday August 19 is beginning of GPS week 991

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

September 16, 2018

Sunday September 16 is beginning of GPS week 995

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

October 6, 2018

• https://www.macrumors.com/2018/10/08/apple-watch-series-4-daylight-saving-time-bug/

October 21, 2018

GPS Week Number reached 1,000

• https://blog.fosketts.net/2019/04/06/gps-time-rollover-failures-keep-happening-but-theyre-almost-done/

• https://news.ycombinator.com/item?id=19593227

March 17, 2019

Sunday March 17 is beginning of GPS week 1021

3 weeks before next GPS week rollover

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=753&dispmid=965

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

April 6, 2019

Last day before GPS rollover

• https://en.wikipedia.org/wiki/GPS_Week_Number_Rollover

• https://twitter.com/ChinaAvReview/status/1114802018919411712

• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Second_GPS_rollover

April 7, 2019

Sunday April 7 is beginning of GPS week 0

April 30, 2019

• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Japanese_calendar_transition

November 3, 2019

Sunday November 3 is beginning of GPS week 30

• http://rachelbythebay.com/w/2019/10/03/roll/

• https://news.ycombinator.com/item?id=21155040

• https://techship.com/news/gps-week-roll-over-issue-during-epoch-restart/

End of 2019

ISO week vs. Gregorian week

• https://www.reddit.com/r/videos/comments/ehnz3q/why_its_already_2020/

January 1, 2020

Y2K20

• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Classic_Mac_OS

• https://twitter.com/jefposk/status/1213258774938415104

• https://twitter.com/nick_guerrera/status/1394435349980405762

• This Year’s Y2K20 Bug Came Directly From ‘A Lazy Fix’ to the Y2K Bug

• https://kotaku.com/due-to-a-y2k-like-bug-wwe-2k20-is-almost-unplayable-in-1840760479?utm_campaign=Socialflow_Kotaku_Twitter

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2020

• https://www.reddit.com/r/mildlyinteresting/comments/laij6n/we_id_sign_y2ks_20_years_after_the_new_millennium/

February 29, 2020

2020 leap day bugs

• https://news.ycombinator.com/item?id=22452065

December 20, 2020

Sunday December 20 is beginning of GPS week 89

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=753&dispmid=965

• https://acurazine.com/forums/3g-tl-audio-bluetooth-electronics-navigation-94/navi-dash-clock-sync-megathread-update-all-should-fixed-now-630065/

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

2021

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2021

June 20, 2021

Sunday June 20 is beginning of GPS week 115

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=753&dispmid=965

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

October 23, 2021

• Watch out for GPS weirdness on October 23

• https://www.gps.gov/support/user/rollover/

January 2, 2022

Sunday January 2 is beginning of GPS week 143

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2022

• Microsoft Exchange breaks on new year

• 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://news.ycombinator.com/item?id=29818572

• https://jalopnik.com/honda-clocks-are-stuck-20-years-in-the-past-and-this-mi-1848306970

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

March 17, 2022

• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Windows_C_runtime_library

In[163]:= 
DatePlus[{2022, 3, 17, 2, 20, 48}, {500000000, "Second"}] == 
 DatePlus[{1970, 1, 1}, {2^31, "Second"}]

Out[163]= True

May 15 2022

Sun May 15 is beginning of GPS week 162

• https://panbo.com/2022-gps-rollovers-furuno-airmar-jrc-and-who-else/

• http://www.jrc.co.jp/eng/about/news/2021/1224-1.html

September 18 2022

Sun September 18 is beginning of GPS week 180

• https://news.ycombinator.com/item?id=32700184

• https://web.archive.org/web/20230208142654/https://sync.empowerednetworks.com/keep-your-ntp-server-current/

• https://www.orolia.com/will-your-network-time-servers-be-affected-by-the-september-2022-delayed-gps-rollover/

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

March ?, 2023

Raystar 125

• https://panbo.com/2022-gps-rollovers-furuno-airmar-jrc-and-who-else/

2024

February 29, 2024

Leap day

Payment card readers at petrol pumps in New Zealand were unable to handle the leap year and were unable to properly dispense gasoline.[41] https://www.reuters.com/world/asia-pacific/leap-year-glitch-shuts-some-new-zealand-fuel-pumps-2024-02-29/

Video games EA Sports WRC and Theatrhythm Final Bar Line also suffered issues related to the leap year, with the former crashing when trying to load the game and the latter claiming that the save data was corrupted. Both games had to be set to the following day of March 1, 2024 to properly work.[42][43][44]

https://kotaku.com/final-fantasy-theatrhythm-broken-wrc-leap-day-bug-ps4-1851298039

https://www.ign.com/articles/theatrhythm-final-fantasy-on-nintendo-switch-doesnt-work-today-feb-29-seemingly-because-its-a-leap-year

https://www.ign.com/articles/ea-sports-wrc-crashing-on-start-up-today-feb-29-because-2024s-a-leap-year

March 24, 2024

Sunday March 24 is beginning of GPS week 259

Rollover date for various Furuno GPS equipment.

• https://www.furuno.co.jp/en/news/notice/notice_category.html?itemid=55&dispmid=965

• https://tomverbeure.github.io/2024/08/18/Fixing-the-Symmetricom-S200-GPS-Week-Number-Rollover-Problem.html

• https://furuno.ent.box.com/s/fva29wqbcioqvd6mqxn5rt976dkaxudj

December 13, 2024

In December 2024, a 30 year old bug was found in all versions of HCL Notes. When the server is started on or after December 13 2024, an overflow will prevent the mail router to load its configuration, and so no mail is delivered. Patches were released on the next day for all supported versions.

The date/time issue made the TimeDateDifference() internal call return incorrect results under certain conditions, and dates back to the core Notes program in 1986.

• https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0118192

• What happened on December 13, 2024?

December 31, 2024

Last day in leap year

2025

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2025

In Japan, some older computer systems using the Japanese calendar that have not been updated still count years according to the Shōwa era. The year 2025 corresponds in those systems to Shōwa 100, which can cause problems if the software assumes two digits for the year.[46]

January 1 2025

First day in year

In Spain, all Talgo AVRIL class trains stopped operating on January 1, 2025 due to a date handling bug in the battery charging module, causing delays and cancellations as passengers were relocated in other rolling stock.[47][48] A bugfix was deployed by the next day, recovering regular service.[49]

2028

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2028

• http://rachelbythebay.com/w/2021/11/05/sevenbits/

• https://news.ycombinator.com/item?id=28828853

• https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800627

• http://www.3kranger.com/HP3000/mpeix/en-mpe75/Beechglen2028/ch02s03.html

2032

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2032

February 7, 2036

January 1 1900 + 2^32 Second == February 7 2036

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2036

• http://rachelbythebay.com/w/2020/11/26/magic/

January 19, 2038

Year 2038 Problem

• https://theyear2038problem.com/

• https://en.wikipedia.org/wiki/Year_2038_problem

• https://linux.slashdot.org/story/19/03/05/1929233/linux-51-continues-the-years-long-effort-preparing-for-year-2038

With 32 bit signed integers, Unix time will overflow on: 03:14:08 UTC January 19, 2038

• http://lwn.net/Articles/643234/

• https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.1-Year-2038-Syscalls

• Investigating why Steam started picking a random font

November 20, 2038

GPS Week rollover

February 6, 2040

old macintosh calendar expires

• https://apple.fandom.com/wiki/2040_date_limit

• https://lowendmac.com/lab/04/0115.html

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2040

September 18, 2042

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2042

2043

Microsoft Exchange update format

changing to unsigned long

• https://old.reddit.com/r/sysadmin/comments/rt91z6/exchange_2019_antimalware_bad_update/

January 19, 2048

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2048

2069

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2069

December 30, 2078

• https://www.iwpcug.org/docs/18991230.php

2079

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2079

2080

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2080

2100

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2100

2106

unsigned 32-bit count of seconds (also) since 1970

• https://news.ycombinator.com/item?id=22745295

With 2^5 = 32 bit unsigned integers, Unix time will overflow on: 06:28:16 UTC February 07, 2106

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2106

2108

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2108

2137

GPS 13-bit week rollover

• https://lobste.rs/s/tdalbi/gpsd_time_will_jump_back_1024_weeks_at

• https://www.gps.gov/support/user/rollover/

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2137

November 4, 2153

• http://rachelbythebay.com/w/2017/09/27/2153/

March 16, 2157

// Seconds field overflowed the 33 bits available when // storing a monotonic time. This will be true after // March 16, 2157.

• https://go.dev/src/time/time.go

2232

• https://www.netmeister.org/blog/epoch.html

2262

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_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.

• http://rachelbythebay.com/w/2020/11/26/magic/

2286

• https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_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.

• http://rachelbythebay.com/w/2020/11/26/magic/

3268

The next Julian Period begins in the year 3268 AD.

July 8, 3409

Since a UUID is a fixed size and contains a time field, it is possible for values to rollover (around A.D. 3400, depending on the specific algorithm used).

• https://datatracker.ietf.org/doc/html/rfc4122

Assuming signed 60-bit storage:

In[45]:= DatePlus[{1582, 10, 15, 0, 0, 0}, {Floor[16^^7ffffffffffffff/10000000], "Second"}]

Out[45]= {3409, 7, 8, 22, 40, 30}

3603

The rollover time as defined by ITU-T Rec. X.667 is 3603 AD.

• https://en.wikipedia.org/wiki/Universally_unique_identifier#Versions_1_and_6_(date-time_and_MAC_address)

Note that there is nothing special about the year 3603. Using increments of 100 nanoseconds from October 15, 1582, the rollover will occur on July 8, 3409 for signed 60-bit storage or Mar 31, 5236 for unsigned 60-bit storage.

My working theory is that the document used the “period of approximately 1600 years” and added that to the year that the document was authored (2003) to obtain the year 3603.

Sources that state the rollover will happen in 3603 are incorrect.

4000

• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Years_4000,_8000,_etc.

4147

• https://www.netmeister.org/blog/epoch.html

4501

• https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_4501

Mar 31, 5236

However some software, such as the libuuid library, treats the timestamp as unsigned, putting the rollover time in 5623 AD.

• https://en.wikipedia.org/wiki/Universally_unique_identifier#Versions_1_and_6_(date-time_and_MAC_address)

Wikipedia says rollover happens on 5623, but this is incorrect.

An edit made in 2023 incorrectly changed the article from saying 5236 to saying 5623 with the comment “Corrects rollover date when 60-bit timestamp is treated as an unsigned integer. Previous value appears to have been a typo.”

• https://en.wikipedia.org/w/index.php?title=Universally_unique_identifier&oldid=1149242116

The correct date is easily verified to be 5236.

In[53]:= DatePlus[{1582, 10, 15, 0, 0, 0}, {Floor[2^60/10000000], "Second"}]

Out[53]= {5236, 3, 31, 21, 21, 0}