The 2038 problem is a hidden risk in legacy computer systems that store time as a 32-bit Unix timestamp. On 19 January 2038, this counter will overflow, causing systems to jump back to 1901.
This jump backwards is expected to cause many software systems to crash or run into an unpredictable behaviour. And this is not theoretical! It may already affect systems that calculate future dates or that have a design life beyond 2037.
In rail, where precise timing underpins safe and reliable operations, this creates a hidden but critical risk across onboard and infrastructure systems, maintenance tools, etc. The key question is not if, but where.
While the event is “still” 12 years away, it is actually tomorrow, considering that the Rail Industry, like several others, are known to be slow-moving when it comes to such massive system upgrades.
At PROSE, we help you identify affected systems, understand their interactions, and define practical mitigation strategies tailored to your operations and lifecycle. Reach out to your local contact to learn more.
Have you checked your systems yet?
