Good to know for your journey in January 2038

Posted by Mark (Schwerin) on 12/15/25 02:09 PM

How many of us have said at least once, “If only I had known that before...”? Therefore I want to prepare all fellow travelers that IT problems can occur from 03:14:07 UTC on 19 January 2038. Why?

The so called Y2K38 (year 2038) problem is based on 32-bit system - used in a lot of computer systems - which transfers every date and time combination into a 32 digit line of 0 and 1 digits, as starting date for this the Jan 1st 1970 00:00:00 (UNIX time) was chosen. And simply said: at this above mentioned date and time the possible range of numbers in 32-digit-long 0-1-combinations will have reached its limit.

Btw: from January 2026 on in binary you will have 1100 years to prepare for the problem, this means 12 years in decimal counting.

So, if you read until here you now know it - no excuse. But until then you can earn respect on every tech party. ;-)

Source to more detailed background information: Wikipedia link

Posted by CWsocial

near San Francisco (currently in Vienna)

12/15/25 02:58 PM

6127 posts

I hope I am still traveling in 2038 to worry about this! I'm sure the airlines and TSA have upgraded their systems to 64 bit technology. Surely .... ?!? (said with sarcasm)

Posted by Windyram

Belgium

12/15/25 03:03 PM

220 posts

But until then you can earn respect on every tech party. ;-)

Really? I don't think so. They will just be laughing with you... and explain to you the migration to a 64-bit time_t remains the standard and most widely implemented solution.

We are still laughing with the Y2K believers https://americanhistory.si.edu/collections/object-groups/y2k

Posted by Mark OP

Schwerin

12/15/25 03:34 PM

4259 posts

Yes, really.

First, Y2K was a very different problem. I hope you do not think that it is similar?

Second, it does not matter if a system (machine, cloud entity) is running a 64-bit operating system, the question is in which format the time and date is saved in a software or a database.

Third, make only a guess how many software or database systems with own time and date are operated in a larger travel company or a plane or a ship. Even better: if you know a CIO or a CTO from a real big company ask him / her how many systems and interfaces exactly the company has. Look at the face in the first three seconds after question.

Fourth, all these companies and systems are very seldomly working stand-alone, so the time formats of a booking for example is handled / saved sequentially or in parallel by multiple systems of different companies / partners. Keep and eye on the interfaces and how they handle data and datasets.

Fifth: it is more than just bookings or tickets. It is all hardware piece and mean of transport, passports, credit cards, currencies, cashless payment, driving licenses, travel insurances, and so on.

Some more details available why this is not "just install a 64-bit something". The all cases end-to-end testing from a traveler is due to manifold of combinations nearly impossible - and not scope of single companies btw.

Finally: it is a real challenge that companies and their IT and Tech leads (not the same by the way) take likely very seriously in a program or project if they know their job - and of course finally they will make it, some before, some with last fixes after the date.

Posted by Windyram

Belgium

12/15/25 03:52 PM

220 posts

12 years of evolution in a world with AI ... just try to be smart and don't be a fearemonger !

Posted by Mark OP

Schwerin

12/15/25 03:56 PM

4259 posts

LOL, 30 years of IT and corporate experience.

AI or what you likely mean LLM is the cherry on the cake because LLM does not even know by itself what time is. So a good one.

Posted by TC

Atlanta

12/15/25 04:12 PM

5544 posts

Assuming I'll still be around then, that will probably be the least of my problems.