Cloudflare experienced a minor incident on August 3, 2026 affecting Workers, lasting 15h 59m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 03, 2026, 03:13 PM UTC
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 03, 2026, 03:21 PM UTC
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 04, 2026, 07:00 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 04, 2026, 07:12 AM UTC
This incident has been resolved.