/ Register

Learn about Centmin Mod LEMP Stack today
Register Now

Cloudflare Cloudflare Workers Runtime API issues

Discussion in 'VPS Provider Network Status' started by eva2000, Aug 4, 2026 at 1:34 AM.

Previous Thread Next Thread
Loading...
  1. Aug 4, 2026 at 1:34 AM #1
    eva2000

    eva2000 Administrator Staff Member

    59,396
    12,517
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,153
    Local Time:
    8:43 PM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    Aug 3, 15:21 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.

    Aug 3, 15:13 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.

    Continue reading...
     
Previous Thread Next Thread
Loading...

.