Cloudflare's Browser Run product broke for 1h 7m on 30 October, throwing intermittent 500 errors on Quick Actions. The fault sat on Cloudflare's side and was resolved from their end, not yours.
Started
02:41 UTC
Duration
Lasted 1h 7m
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.
What happened?
Cloudflare opened an incident at 02:41 UTC titled "Increased Errors for Browser Run", saying the issue could affect multiple customers and that people trying to use Browser Run Quick Actions might see intermittent 500 errors. At 03:04 Cloudflare said the issue had been identified and a fix was being implemented. By 03:31 Cloudflare reported a fix had been implemented and they were monitoring results, and the incident closed out at the 1h 7m mark. Cloudflare filed three updates in total and none of them name a root cause beyond "the issue has been identified", so the specific trigger is not on the record. No components are listed as affected in Cloudflare's own breakdown for this incident. No user reports were filed during the window, so there is no independent account of how many people hit the 500 errors or for how long. This was a single incident for the day, not a string of separate faults. Cloudflare's history shows 208 incidents in the last 90 days with a median duration of 1 hour 55 minutes, so this one resolved faster than Cloudflare's typical fix. Across all time Cloudflare has logged 3,472 incidents on this status page.
Learning
UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components stayed green throughout, showing 100% uptime over 24 hours and 7 days and 99.996% over 30 days, and this incident was not registered against those checks. That is not a contradiction. Browser Run Quick Actions is a specific product surface, not the core DNS, API or edge data paths that those probes watch, so a fault confined to one feature can leave the broader infrastructure checks untouched. This is the common shape of a provider-side partial outage: one function throws errors while the rest of the platform answers normally, which is exactly why a clean uptime graph on your side can sit next to a real, logged incident on theirs. If your own product uses Browser Run specifically, your users would have seen 500 errors during this window even though every other signal you'd normally check looked fine. Watching your own endpoints only tells you your half is up, it says nothing about whether the specific Cloudflare feature you depend on is degraded upstream. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
