It's Unix Epoch Time. Unix based systems keep time by storing the number of seconds since the Unix Epoch began, which is defined (arbitrarily) as Jan 1st 1970. This is why you will often see the glitched date Dec 31st 1969, which represents the number -1, usually a sign of missing datetime data.
There's a Y2K for Epoch time called the 2038 problem. This is the year when the number of seconds since the Unix Epoch began exceeds the maximum storage space many older systems allocate to time tracking. This being a 32-bit integer or 2^31 − 1 (2,147,483,647). The exact time this will happen is 03:14:07 UTC on 19 January 2038.
The fix is to use a 64-bit integer to store time, in which case you should not have any issue for the next 300 billion years.
It's Unix Epoch Time. Unix based systems keep time by storing the number of seconds since the Unix Epoch began, which is defined (arbitrarily) as Jan 1st 1970. This is why you will often see the glitched date Dec 31st 1969, which represents the number -1, usually a sign of missing datetime data.
There's a Y2K for Epoch time called the 2038 problem. This is the year when the number of seconds since the Unix Epoch began exceeds the maximum storage space many older systems allocate to time tracking. This being a 32-bit integer or 2^31 − 1 (2,147,483,647). The exact time this will happen is 03:14:07 UTC on 19 January 2038.
The fix is to use a 64-bit integer to store time, in which case you should not have any issue for the next 300 billion years.