Event notifications are the affected layer
Cloudflare opened a new incident at 01:53 UTC on November 10 saying changes to Workers were temporarily not producing Event Subscription events. The company says it intentionally disabled the feature because of an ongoing issue and is working to restore it.
The new notice says changes to Workers themselves are working normally and Workers already deployed are unaffected. This is the provider’s stated scope, rather than an independent test of every application.
Check event delivery separately from a successful change
Teams depending on Event Subscription messages can check the live incident timeline and their actual event delivery. A successful Worker change alone does not establish that its corresponding subscription event arrived.
The notice does not give a restoration time or establish that missed events will be replayed. Its named components do not demonstrate a general outage of all Queue workloads.
The earlier change incident has its own timeline
Cloudflare’s November 9 notice covered creating, editing and deleting Workers: it opened at 16:15 UTC, moved to identified at 16:22 UTC and monitoring at 16:35 UTC. Cloudflare marked that incident resolved at 01:46 UTC on November 10.
The new November 10 entry specifically says changes are working normally while event generation is disabled. The two notices have separate incident IDs and timelines; neither establishes a shared root cause.
