Cloudflare had two separate incidents on 24 October 2026, the longer one running 2h 9m out of Ashburn, VA. Both were on Cloudflare's side of the network, affecting Durable Objects, R2, Workflows, D1 and related services.
Started
01:01 UTC
Duration
Lasted 2h 9m
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, Workflows, Ashburn, VA, United States - (IAD), North America, Network, R2, D1, Durable Objects
What happened?
The first incident started at 01:01 UTC and was logged as network performance issues in Ashburn, VA. Four minutes later Cloudflare listed the affected services as Durable Objects, R2, Workflows, Queues, D1 and Artifacts, which tells you this was not a cosmetic blip but something touching the edge compute and storage stack. By 01:28 UTC Cloudflare said a fix had been implemented and they were monitoring, and the incident closed out at 2h 9m total. A second, unrelated incident began at 13:13 UTC, described as an increased error rate in Workflow Operations. That one ran shorter, 46 minutes, with Cloudflare moving to monitoring status at 13:38 UTC and no further update logged after that. Across both incidents Cloudflare posted five updates in total, and none of them explain what caused either problem. The component list for the day spans eight entries, including Cloudflare Sites and Services, North America, the Ashburn IAD location, and specific products like D1, Durable Objects, R2 and Workflows. No post-mortem has been published for either incident. No user reports were filed during the window, which is unsurprising given these were backend services (Durable Objects, R2, Workflows, D1) rather than consumer-facing sites. Cloudflare's own history shows 195 incidents in the last 90 days with a median duration of 1 hour 58 minutes, so a 2h 9m incident sits close to Cloudflare's typical pace of disruption, and a 46 minute one sits well under it.
Learning
UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components, run from EU and NA regions at 60 second intervals, showed 100% uptime over 24 hours and 7 days, and 99.996% over 30 days, with this incident not registered as a probe failure. That is not a contradiction. The incidents hit Durable Objects, R2, Workflows and D1 at the platform level, services that sit behind the basic reachability checks a status probe makes, so a product relying on those services could see real errors while a simple ping or HTTP check against Cloudflare's edge stayed green throughout. This is the general shape of a platform-layer fault: the edge network answers fine, but the specific compute or storage service behind it is degraded or erroring. If your own monitoring only watches your endpoints, an outage like this shows up as mysterious errors in your product with nothing externally wrong to point to. Over the last 30 days UptimeRobot's data shows Cloudflare running 65 incidents with a median duration of 2h 56m, which gives you a sense of how often this kind of thing recurs and how long you should expect to wait it out. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.