Cloudflare Workers Runtime API issues

Summary

Cloudflare Workers Runtime API issues

This incident has been resolved.

• Started

  Aug 3, 2026 · 3:13 PM

• Resolved

  Aug 4, 2026 · 7:12 AM

• Duration

  15h 59m

• Severity

  Minor

• ◐

  Investigating

  Aug 3 · 3:13 PM Cloudflare

  Cloudflare is aware of an issue with the latest Workers Runtime API release that exposes native Temporal with clock stuck at epoch 0. Updates to follow.

• ◆

  Identified

  Aug 3 · 3:21 PM Cloudflare

  Workers runtime: Temporal global exposed with an incorrect clock Since 2026-07-30, the Workers runtime has exposed a global Temporal object that was not intended to be available. Its clock is wrong: Temporal.Now reports 1970-01-01 rather than the current time. Date and Date.now() are unaffected and report the correct time. This can affect Workers that install a Temporal polyfill only when no native Temporal is detected. On those Workers, the polyfill stopped being installed and time-dependent logic began computing against 1970 — for example, tokens minted with an issue time of 0 and an expiry in 1970, incorrect TTLs, or incorrect date arithmetic. No error is raised when this happens.

• ◉

  Monitoring

  Aug 4 · 7:00 AM Cloudflare

  A fix has been implemented and we are monitoring the results.

• ✓

  Resolved

  Aug 4 · 7:12 AM Cloudflare

  This incident has been resolved.