Cloudflare Workers Runtime API issues
受影響
系統出現問題 從 3:13 PM 至 7:00 AM, 運行正常 從 7:00 AM 至 7:12 AM
系統出現問題 從 3:13 PM 至 7:00 AM, 運行正常 從 7:00 AM 至 7:12 AM
- 已解決 · UTC
This incident has been resolved.
- 監視中 · UTC
A fix has been implemented and we are monitoring the results.
- 已確認問題 · 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.
- 調查中 · 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.

