Delayed, missed, and duplicated Workers Cron Triggers
Cloudflare · Last saved provider status: investigating
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- investigating
- Provider impact
- minor
- Provider record created
- 23 Oct 2026, 15:27:34 UTC
- Provider record updated
- 23 Oct 2026, 16:12:49 UTC
- Explicit provider start
- 23 Oct 2026, 15:27:34 UTC
- Explicit provider end
- Not available
Affected components reported by the provider
- Workers
57srcl8zcn7c
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Cloudflare's complete published platform report and provider locations. These are provider reports, not independent network observations or evidence of an application's upstream dependencies. Workers AI, AI Gateway and Replicate have separate component views.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- investigating
We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.
Seen in a saved revision at 23 Oct 2026, 16:31:38 UTC