Cloudflare's Cloud Connector Rules stopped creating and updating for 2h 37m on 12 September 2026. The fault sat inside Cloudflare's own configuration tooling, not on your side.
Started
08:06 UTC
Duration
Lasted 2h 37m
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, Cloud Connector
What happened?
Cloudflare logged one incident on this day, starting at 08:06 UTC and closing at 10:43 UTC, a span of 2h 37m. It affected two listed components: Cloudflare Sites and Services, and Cloud Connector. The problem was specific: failures in creating and updating Cloud Connector Rules, the feature that routes traffic through third party connectors from Cloudflare's edge. Cloudflare's status page posted three updates across the window. At 08:06 it opened as "investigating", saying it was working to mitigate the problem. By 08:11, five minutes later, it moved to "identified" and said a fix was being implemented. At 10:10 it moved to "monitoring", stating a fix had been implemented. There is no further update after that, and no closing statement confirming resolution beyond the monitoring note; the 2h 37m duration is Cloudflare's own figure. No user reports were filed in this window on our side. Over the past 90 days Cloudflare has logged 193 incidents with a median duration of 1 hour 48 minutes, so this one ran longer than typical for the service.
Learning
UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components stayed at 100% uptime through this window, across both EU and NA regions, and this incident was not registered against those checks. That is not a contradiction. This fault sat inside a specific configuration feature, Cloud Connector Rules, which affects creating and updating rules rather than the resolution of live DNS, edge delivery or API availability that our probes are built to catch. A control-plane failure like this can block your ability to change routing configuration while every existing connection keeps resolving normally, which is exactly the shape of failure that pings against a live endpoint will not surface. If your own monitoring only watches your endpoints, it will look clean during an incident like this because your endpoints genuinely were fine. This is the case for watching the provider's side directly rather than inferring its health from your own uptime numbers. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
