- Cloudflare Workers Runtime API issues – Incident details

All systems operational

Cloudflare Workers Runtime API issues

Resolved
Degraded performance
Started about 2 months agoLasted about 16 hours

Affected

Third Party: Render → Singapore → Web Services - Free Tier

Degraded performance from 3:13 PM to 7:00 AM, Operational from 7:00 AM to 7:12 AM

Third Party: Cloudflare → Cloudflare Sites and Services → Workers

Degraded performance from 3:13 PM to 7:00 AM, Operational from 7:00 AM to 7:12 AM

Updates
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Monitoring
    UTC
    Monitoring

    A fix has been implemented and we are monitoring the results.

  • Identified
    UTC
    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.

  • Investigating
    UTC
    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.

雙龍體育 - Footer