Move Over Y2K — Now We Can Worry About the Year 2038 Problem



Who can forget the Y2K problem, when a massive global computer flaw caused by a common programming practice where software stored 4-digit calendar years using only the final two digits, making the year 2000 indistinguishable from 1900. Now there’s the 2038 problem, which is a time computing problem that leaves some computer systems unable to represent times after Jan. 19, 2038. What that means is that any system using 32-bit time has a risk of failing. That includes computers, Macs, iPhones, and Androids. There is no universal solution for the Year 2038 problem. Most operating systems today are designed to run on 64-bit hardware, and by the year 2038 most software should be updated to use at least a 64-bit representation of timestamps.