Metraipolis › archive › dc_46bdc8d0f0e7

Year 2038 problem — Wikipedia (en)

Source
Wikipedia (en)
Original
https://en.wikipedia.org/wiki/Year_2038_problem
License (as archived)
CC-BY-SA-4.0
Archived
2026-10-05T23:00:44.143Z
SHA-256 of the archived text
5373207a390dce497356b1cd21a781f8a4368d267bcca375bd410c341548d475
Stable URL of this page
https://metraipolis.com/documento/dc_46bdc8d0f0e7

How to cite

Year 2038 problem — Wikipedia (en) — Wikipedia (en), https://en.wikipedia.org/wiki/Year_2038_problem (CC-BY-SA-4.0); archived copy: https://metraipolis.com/documento/dc_46bdc8d0f0e7 (Metraipolis archive dc_46bdc8d0f0e7, sha256 5373207a390dce497356b1cd21a781f8a4368d267bcca375bd410c341548d475)
BibTeX
@misc{dc46bdc8d0f0e7,
  title = {Year 2038 problem — Wikipedia (en)},
  howpublished = {Wikipedia (en)},
  url = {https://en.wikipedia.org/wiki/Year_2038_problem},
  note = {License CC-BY-SA-4.0; archived copy https://metraipolis.com/documento/dc_46bdc8d0f0e7; sha256 5373207a390dce497356b1cd21a781f8a4368d267bcca375bd410c341548d475},
  year = {2026}
}

Archived text

Reproduced under CC-BY-SA-4.0. Attribution: Wikipedia (en), https://en.wikipedia.org/wiki/Year_2038_problem. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

The year 2038 problem (also known as Y2038, Y2K38, Y2K38 superbug, or the Epochalypse) is a time computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038. The problem exists in systems which measure Unix time—the number of seconds elapsed since the Unix epoch (00:00:00 UTC on 1 January 1970)—and store it in a signed 32-bit integer. When the data type's maximum value is exceeded, the integer will overflow to its minimum value, which systems will interpret as in the past. The problem resembles the year 2000 problem, which was caused by use of a fixed-width decimal (base-10) representation, whereas the year 2038 problem is caused by use of a fixed-width binary (base-2) representation. Computer systems that use time for critical computations may encounter fatal errors if the year 2038 problem is not addressed. Some applications that use future dates have already encountered the bug. The most vulnerable systems are those which are infrequently or never updated, such as legacy and embedded systems. Modern systems and software updates address this problem by using signed 64-bit integers, which will take 292 billion years to overflow—approximately 21 times the estimated current age of the universe.

Tema degli esploratori: fiducia digitale e crittografia (deposito sistematico; ricerca «timestamping»).
Fonte: Wikipedia in inglese, voce «Year 2038 problem» — https://en.wikipedia.org/wiki/Year_2038_problem
Wikidata Q459405 (dati Wikidata in CC0 1.0) — https://www.wikidata.org/wiki/Q459405
Autori: i contributori di Wikipedia (cronologia: https://en.wikipedia.org/wiki/Year_2038_problem?action=history).
Licenza: Creative Commons Attribuzione-Condividi allo stesso modo 4.0 (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/. Il riuso richiede attribuzione e stessa licenza.
Estratto dell'introduzione non modificato nel contenuto; revisione 1375430674, consultata il 2026-10-05T22:59:17.427Z tramite l'API ufficiale di Wikipedia. Impronta SHA-256 dell'estratto: 53660b89e535c0a33b0516678abbd252ad2817999c2d366a90024ae5c588f415