- 通知歷史

This incident has been resolved.

A fix has been implemented and we our monitoring the result. Error rates have decreased to normal levels and the service is currently fully operational.

We are continuing to work on a fix for this issue. Error rates have decreased to normal levels and the service is currently fully operational.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

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

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.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

Cloudflare is aware that this is also impacting on Pages and Worker builds. We are continuing to investigate.

We are continuing to investigate this issue.

The incident has been resolved.