Y2038 readiness · SCADA · industrial control · embedded systems

Time runs out of numbers on January 19th 2038.

Year2038.net is a specialist consultancy for the 32-bit clock overflow. We find the time_t hiding in your controllers, firmware, embedded systems, network infrastructure and communication protocols. We design the fix while there is still time to validate it.

Last valid second — 03:14:07 UTC, Tue 19 Jan 2038 Wrap destination — 20:45:52 UTC, Fri 13 Dec 1901 At risk — RTUs, PLCs, DCS, MCU timers, historians

The short version

Unix counts seconds from 00:00:00 UTC on 1 January 1970. In the original implementations that count was stored in a time_t: a signed 32-bit integer. The largest value it can hold is 2,147,483,647 seconds — 03:14:07 UTC on Tuesday, 19 January 2038. One second later the counter overflows, clocks snap back to 20:45:52 UTC on 13 December 1901, and every time-dependent mechanism in the system starts reasoning about the wrong century.

This is not Y2K. There is no date format to patch with a string rewrite. It is a hard arithmetic overflow, and it propagates through every mechanism that does time math in 32 bits: scheduling, timeouts, certificate expiry, log ordering, alarm prioritization, motor-sync loops.

The systems that kept 32-bit time are precisely the systems that cannot be swapped out on a whim. An RTU commissioned in 2015 is engineered to run water, power, and pipelines into the 2040s. Firmware validation cycles take three to ten years. Some devices have never touched a network at all. The data centers quietly went 64-bit; many deployed embedded devices have never been updated.

We treat Y2038 as what it is: a systemic infrastructure risk, not a software bug. The remediation runway is measured in years, and it started many years ago. Given the vast scale of the problem in millions of discrete embedded systems, there is limited time remaining until January 2038.

Capabilities

What we actually do

Engagements are scoped per site or per fleet, and staffed by engineers who have stood in the control room during the change window, not auditors with a checklist.

  1. 01

    Timekeeping audits

    A full sweep of controllers, RTUs, sensors, and supervisory servers: We search for every time_t, every 32-bit register, every protocol field that touches the clock.

  2. 02

    Obsolescence mapping

    Which devices have a vendor path to 2038, which have been abandoned by their OEM, and what each of those answers costs you.

  3. 03

    Remediation design

    Firmware patches, epoch shifts, dual-mode clocks, or hardware replacement, sequenced around maintenance windows you actually have.

  4. 04

    Time-warp validation

    We roll test systems past 03:14:07 UTC on 19 January 2038 and watch them break in the lab, so the live plant never has to.

  5. 05

    Compliance evidence

    Documentation packs for IEC 62443, ISO 26262, IEC 61131-3, and NIST SP 800-82 audits, Y2038 handled before the auditor asks.

  6. 06

    Migration support

    Phased replacement, parallel systems, and rollback plans, executed on site or through the serial port into the air-gapped corner.

The counter won't wait for the budget cycle.

Upgrading or replacing vast fleets of embeded devices takes many years. Start while 2038 is still a deadline, not a post-mortem.