Resolved
Cloudflare · degraded service
Cloudflare Workers - Cron Trigger Activation Issues
Started 13 Oct 15:18 UTC, resolved today 00:09 UTC: it lasted 8 h 51 min.
8 h 51 min
How long it lasted, from the provider's times
4Updates posted
6Other incidents at the same timeWhat it affected
As the provider names itWhat the provider posted
Newest first- today 00:09 UTCResolvedThis incident has been resolved.
- 13 Oct 23:10 UTCMonitoringWe are continuing to monitor for any further issues.
- 13 Oct 15:19 UTCIdentifiedThe issue has been identified and a fix is being implemented.
- 13 Oct 15:18 UTCInvestigatingCloudflare is investigating issues with Workers Cron Triggers. Customers who have recently created or modified a Cron Trigger schedule may find that the schedule is not executing as expected. Pre-existing Cron Trigger schedules that have not been recently modified are not affected. We are working to identify the cause and mitigate this problem. More updates to follow shortly.
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Cloudflare Audit Logs v2 ingestion is missing multiple Cloudflare products
- GitLab.com Increase of HTTP 50X errors on GitLab.com
- Cloudflare Elevated Errors in China Network Colos
- Cloudflare Cloudflare One Clients are incorrectly challenged on some sites
- Microsoft 365 admin center Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
- Microsoft 365 admin center Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
Earlier incidents in the 14 days before
- Cloudflare: Network performance issues in Ashburn, US (IAD)Service incident · 13 Oct
- Cloudflare: Cloudflare Workers - Cron Trigger Activation IssuesService incident · 12 Oct
- Cloudflare: Cloudflare Network Performance IssuesService incident · 12 Oct
- Cloudflare: Cloudflare Workers APIService incident · 12 Oct
- Cloudflare: Network Performance Issues in SeattleService incident · 12 Oct
What changed
First observed 14 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about Cloudflare: its changes, known issues and incidents on one timeline.