Cloudflare logged three separate incidents on 5 November 2026, touching Durable Objects, its India network colocations, and Workers Builds. The longest ran 19 hours 44 minutes, all three were Cloudflare's own infrastructure problems, not anything on your end.
Started
13:23 UTC
Duration
Lasted 19h 44m
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 Builds, Durable Objects
What happened?
Cloudflare's status page lists three incidents for the day, starting at 13:23 UTC. The first was an increase in errors for Durable Objects in Western Europe, and Cloudflare's own update says the issue was already resolved by the time they posted, with the single filing marked "monitoring". That incident shows a duration of 19 hours 44 minutes, the longest of the three, though Cloudflare gave no further detail on what caused it or how it was fixed. The second incident, starting 15:05 UTC, was a network disruption across multiple colocations in India. Cloudflare identified 9 impacted colocations, all in India, and pulled them from the network while investigating, resolving within 1 hour 12 minutes. The third incident, starting 19:51 UTC, affected Cloudflare Workers Builds, with Cloudflare saying it was aware of an issue "which potentially impacts multiple customers" and that builds were being processed through a backlog. That one closed out in 30 minutes. Across all three incidents, Cloudflare published five updates in total, and none of the three has a published post-mortem explaining root cause. No user reports were filed during the window on this record. Three components were affected over the day: Cloudflare Sites and Services, Durable Objects, and Workers Builds.
Learning
UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components, run from EU and NA regions, show 100% uptime over 24 hours and 7 days, and 99.996% over 30 days, with this incident day not registered against those probes. That is not a contradiction. Durable Objects errors in Western Europe and a colocation drop in India are both scoped failures, affecting specific regions and specific product paths rather than the general edge network that basic uptime checks hit. A probe hitting Cloudflare's DNS or edge-data endpoint from Frankfurt or Virginia can stay green while a customer routed through an affected Indian colocation or relying on Durable Objects in the wrong region sees errors the whole time. This is the recurring shape of edge-network outages: the provider's core reachability holds up on paper while a real subset of traffic is broken. Cloudflare's 90 day history shows 206 incidents with a median duration of 1 hour 54 minutes, so short regional disruptions like these are routine for them, not rare events. Your own monitoring tells you whether your product is reachable, but it cannot tell you whether the fault, when something breaks, sits on your side or Cloudflare's. UptimeRobot now watches Cloudflare's own status feed alongside your endpoints, so next time something looks wrong you know which side broke without guessing.