Cloudflare had two separate incidents on 25 September, one of them running 14 hours and 48 minutes against Durable Objects, the other a shorter problem affecting Compression rule edits in the dashboard. Both were on Cloudflare's side and both are now resolved.
Started
00:03 UTC
Duration
Lasted 14h 48m
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, Rules, Durable Objects
What happened?
The day's first incident started at 00:03 UTC as an issue with Workflows instances getting stuck in a Queued state. Cloudflare said a fix had been implemented and they were monitoring by 01:31, but at 02:32 they reported a related problem, an increase of errors for Durable Objects, and reopened investigation. That second phase ran until 08:48, when Cloudflare again said a fix was implemented and they were monitoring results. Taken together, the Durable Objects incident spans 14 hours and 48 minutes from first report to last update, though the record shows two distinct problem statements rather than one continuous failure described the same way throughout. A separate, shorter incident began at 04:58 UTC, affecting the dashboard's ability to edit or create Compression rules. Cloudflare was explicit that existing Compression rules kept working, this was limited to the editing flow. That incident moved through investigating, identified and monitoring states in under two hours, closing by 06:26. Three components appear on Cloudflare's own status list for the day: Cloudflare Sites and Services, Durable Objects, and Rules. No user reports were filed during either window on this page. Cloudflare has not published a post-mortem for either incident, and neither update explains what caused the Durable Objects errors or the rule-editing fault at the code or infrastructure level.
Learning
UptimeRobot's own probes against Cloudflare's API control, DNS and edge data endpoints stayed at 100% uptime over the past 24 hours, 7 days and 30 days, and none of them registered this incident. That is not a contradiction. Durable Objects is a specific compute primitive and the Compression rule editor is a specific dashboard function, neither of which sits on the basic reachability paths that uptime checks typically watch. A product built on Workflows or Durable Objects could have been stuck or erroring for most of a day while every external check of Cloudflare's edge came back green, because the edge was up and the problem was inside a particular service running behind it. This is the general shape of these failures: the front door works, the room you actually needed is the one that's broken. Watching your own endpoints tells you your product is down, it does not tell you whether the fault is yours or the provider's underlying service. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
