Year 2038 Problem (Y2K38)
technicalEmbed This Widget
Add the script tag and a data attribute to embed this widget.
<script src="https://cdn.jsdelivr.net/npm/timefyi-embed@1/dist/embed.min.js" defer></script>
<div data-timefyi="glossary" data-slug="y2k38"></div>Embed via iframe for maximum compatibility.
<iframe src="https://timefyi.com/iframe/glossary/y2k38/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://timefyi.com/glossary/y2k38/Add a dynamic SVG badge to your README or docs.
[](https://timefyi.com/glossary/y2k38/)Use the native HTML custom element.
<script src="https://cdn.jsdelivr.net/npm/timefyi-embed@1/dist/embed.min.js" defer></script>
<timefyi-glossary slug="y2k38"></timefyi-glossary>Definition
A potential computing bug where 32-bit signed integer Unix timestamps will overflow on January 19, 2038, 03:14:07 UTC. Systems using 32-bit time_t will wrap to a negative value, interpreted as 1901.