minoridentified

Cloudflare outage on 2026-08-03: Cloudflare Workers Runtime API issues

Started
Resolved
Not yet resolved
Duration
Ongoing

Latest update from 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.

Cloudflare's own report for this incident

Was your service affected by this Cloudflare outage?

PingView checks your endpoints every minute from four regions and keeps screenshot evidence, so you can tell a vendor outage apart from your own regression.

Start monitoring free

Other Cloudflare incidents

See the full Cloudflare outage history