Home / Media

In the press

When national papers write about the Year 2038 problem, the GPS week rollover, or the neighbouring clocks, the item lands here. We summarise and link. We do not reprint the piece.

Most “2038” headlines are football, Olympics or energy targets. Those stay out.

Reuters · 19 July 2024

Without backup plans, global IT outages will happen again

After the CrowdStrike outage, Reuters put the Year 2038 problem next to Y2K: signed 32-bit Unix time runs out at 03:14 GMT on 19 January 2038. Former NCSC head Ciarán Martin is quoted on how brittle administration already is when a single vendor fails.

Read at Reuters

The Guardian · 28 December 2024

Y2K, 25 years on

A look back at the millennium bug notes the 2038 overflow as the next well-known date bug. One engineer in the piece is not worried: most systems will be on 64-bit time, or will be replaced, before the wrap.

Read at The Guardian

TechCrunch · 6 April 2019

GPS rollover is today. Here’s why devices might get wacky

TechCrunch covered the 10-bit GPS week reset of 6 April 2019. That event is a cousin of Unix Y2038, not the same bug. The next legacy GPS week rollover on this site’s calendar is 20 November 2038.

Read at TechCrunch · Our GPS deadline page

The Guardian · 17 December 2014

Is the Year 2038 problem the new Y2K bug?

The paper walked through signed 32-bit time_t and said not to panic if machines are upgraded. It already flagged the useful point: systems that schedule far ahead can fail years before 19 January 2038.

Read at The Guardian · Backwards Risk

Wired · 20 July 2006

The Unix end times are upon us

Wired tied the 19 January 2038 wrap to the May 2006 AOLserver crashes. A one-billion-second timeout looked past the 32-bit horizon, the expiry date flipped into the past, and the process died. Changing the timeout fixed it.

Read at Wired · Timeline

The New York Times · 19 July 1999

Beyond 2000: further troubles lurk in the future of computing

During the Y2K run-up the Times listed later date bombs, including Y2038 on Unix: seconds since 1 January 1970 run out at 3:14:07 a.m. on 19 January 2038. It used a 30-year mortgage issued in 2009 as the reason to care decades early.

Read at The New York Times (archive)

Wired · 12 August 1998

The next millennium headache

Dennis Ritchie told Wired that by 2038, time_t would be 64-bit “assuming Unix survives.” Capers Jones compared the delay to the same reasoning that left Y2K in old code.

Read at Wired

NYT, AP and TechCrunch have not run a dedicated 2020s explainer on Unix Y2038 that we can find. When they do, it goes here with the outlet name first.

Related: What the Year 2038 problem is, timeline.