Cloudflare had two separate incidents on 26 October 2026, one hitting Workers Builds and one hitting Workers Cron Triggers. Both were faults inside Cloudflare's own systems, lasting 52 minutes and 3 hours 28 minutes.
Started
15:12 UTC
Duration
Lasted 52m
Source
IsDown
Next time
Cloudflare is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Cloudflare Sites and Services, Workers, Workers Builds
What happened?
Cloudflare's status page logged two incidents across the day, affecting Cloudflare Sites and Services, Workers Builds, and Workers, three components in total. The first began at 15:12 UTC, when Cloudflare reported increased delays running Workers builds. Cloudflare said it was working to analyse and mitigate the problem, identified a fix 25 minutes later, and deployed that fix by 15:38 UTC, with the whole incident closed out at 52 minutes. The second incident started at 21:48 UTC and concerned Workers Cron Triggers running late, being skipped, or running more than once. Cloudflare's own wording was that affected customers "may see scheduled Workers invocations that do not run on time or run more than once." That incident ran for 3 hours 28 minutes, with Cloudflare posting a monitoring update at 00:55 UTC and nothing further after that. No user reports were filed during the window on this page. Cloudflare's status page carries five updates across the two incidents, and no post-mortem has been published for either one, so the specific cause behind the build delays or the cron scheduling faults is not on the record. Over the last 90 days Cloudflare has logged 196 incidents with a median duration of 1 hour 57 minutes, so this day's longer incident ran well above that median.
Learning
If you run scheduled jobs on Workers Cron Triggers, this is the failure mode to recognise: the trigger layer itself can miss, delay, or duplicate a run while the rest of Cloudflare's edge keeps serving traffic normally. UptimeRobot's own probes against Cloudflare's API control, DNS, and edge data components stayed at 100% uptime over 24 hours and 7 days through this window, and 99.996% over 30 days, which is correct, because those probes check reachability and response, not whether a scheduled job fired on time. A cron job that silently skips or fires twice will not show up as a dropped connection or a slow response, so an external uptime check and a real scheduling fault can both be true at once. The same logic applies to the build delay incident: builds queuing up is a backend processing issue, not a reachability issue, so a check against Cloudflare's edge would show green throughout. Your own monitoring tells you whether your product is reachable and whether your own endpoints respond, but it cannot see inside Cloudflare's build queue or cron scheduler. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.