Cloudflare Workers Runtime API issues
Components
Regions
Cloudflare Workers Runtime API issues Cloudflare operates global DNS, CDN, WAF, and edge network services. Outages here often affect many sites and APIs that sit behind their network.
identified · 3 Aug 2026, 15:21 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.
investigating · 3 Aug 2026, 15:13 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.
5
Related incidents
—
This incident (ongoing)
1h 8m
Avg. resolution time
If your product depends on Cloudflare, elevated errors during this window often come from upstream, not from your latest commit.
Open official status pageBe the first to know when we launch Pro alerts. No spam — only product updates.
Interested in
Want to know before you start debugging?
Join the waitlist for Pro alerts — we'll notify you at launch.