Cloudflare had two separate incidents on 2 November, one affecting Worker deployments and another affecting Gateway DNS-over-TLS connections over IPv4, with the DNS issue lasting 2h 25m. Both faults sat on Cloudflare's side of the network.
Started
16:41 UTC
Duration
Lasted 51m
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, Gateway, Workers
What happened?
Cloudflare logged two incidents against its status page on 2 November, affecting Cloudflare Sites and Services, Workers and Gateway. The first started at 16:41 UTC and was described as delays when deploying updates to Cloudflare Workers, lasting 51m. Cloudflare's only update on that incident said remediation was in progress, and no further update was filed, so you do not get confirmation of what the remediation involved or when it finished beyond the recorded duration. The second incident started at 22:12 UTC and affected Cloudflare Gateway DNS-over-TLS connections over IPv4. Cloudflare's own wording is specific here: affected customers saw connection timeouts and failed DNS resolution, and the issue was limited to DoT over IPv4, with DoT over IPv6, DNS-over-HTTPS and standard DNS over UDP/TCP all unaffected. That scoping matters if you use Gateway for DNS filtering, since it tells you exactly which transport and IP version to check in your own logs. At 00:23 UTC Cloudflare reported it had identified and applied a fix and was monitoring results, and the incident closed at 2h 25m with no further update after that. No user reports were filed in the window on this page. Cloudflare's history over the last 90 days shows 204 incidents with a median duration of 1 hour 54 minutes, so a 2h 25m incident sits a little above typical. Over all time Cloudflare has logged 3,477 incidents on its status page.
Learning
UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components stayed at 100% uptime over 24 hours and 7 days, with 30-day uptime at 99.996%, and this incident was not registered against those probes. That is not a contradiction. The Worker deployment delay affected the control plane that pushes new code out, not the edge serving already-deployed Workers, so a probe hitting a live edge endpoint would keep passing green while your deploy pipeline sat stuck. The DNS-over-TLS issue was narrower still, limited to one transport protocol over one IP version, so a generic reachability check using DNS over UDP or DoH would never see it even though real DoT-over-IPv4 clients were timing out. This is the general shape of a provider-side outage: the fault lives in a specific feature or protocol path that your own endpoint monitoring never touches, because your monitoring watches whether your product responds, not whether every control-plane function behind it is healthy. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.