Provider
CloudflareIncident detail
Cloudflare Workers Runtime API issues
Resolved incidentMinor1 affected service
Timeline window
to
Outage alerts
Get alerted the next time Cloudflare breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Cloudflare posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
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
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
A fix has been implemented and we are monitoring the results.
Resolved
This incident has been resolved.
Keep exploring
More from Cloudflare
Neighboring incidents on Cloudflare's timeline and the rest of their record on OutageDeck.