Cloudflare favicon

Cloudflare outage on 2026-10-29

cloudflarestatus.com
October 2026 29 Minor incident

Cloudflare ran through eight separate incidents on 29 October 2026, touching Workers, Durable Objects, D1, Workflows, R2, CNI and the dashboard at different points in the day. The longest single incident ran 2h 29m, and the fault sat on Cloudflare's side throughout.

Started

06:55 UTC

Duration

Lasted 1h 35m

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, R2, Durable Objects, D1, Workflows, Dashboard, Support Site, Workers, Containers, Los Angeles, CA, United States - (LAX), North America, Cloud Network Interconnect (CNI)

What happened?

The day opened at 06:55 UTC with increased errors and latency on CNI 2.0 traffic in LAX, which Cloudflare called fixed by 08:08. From there the incidents overlapped rather than followed one another cleanly. At 09:22 Cloudflare reported elevated 500 errors hitting Durable Objects, D1, Workflows, Workers Assets uploads and Cloudchamber together, an incident that ran 2h 29m, the longest of the day. Two minutes later, at 09:24, a separate filing noted Workflows success rates had actually been dipping since around 07:00 UTC, well before Cloudflare opened a ticket for it. At 10:06 a third incident hit Durable Objects availability specifically in Eastern Europe's EEUR2 region, running 1h 41m with only one update ever posted. At 10:31 the dashboard itself started returning HTTP 429 rate limit errors for people on shared egress networks, including Cloudflare One default egress IPs, lasting 1h 40m before a fix landed. A fourth Durable Objects and D1 and Workflows error spike began at 14:16 and ran 2h 19m, again with no update beyond the opening report. A brief 15 minute Durable Objects issue in Eastern North America followed at 16:36, identified and resolved within two updates. The day closed with R2 reporting elevated latency in Eastern Europe starting at 19:57, running 1h 54m. Across all eight incidents, several never received a resolved or monitoring update on Cloudflare's status page, so the record stops at whatever the last posted line says. No user reports were filed during the window for any of these.

Learning

UptimeRobot's own probes, which check Cloudflare's API control plane, DNS at 1.1.1.1 and edge data delivery from both the EU and North America, stayed at 100% uptime for 24 hours and 7 days, and 99.996% over 30 days. That is not a contradiction with a day holding eight separate incidents. Most of what failed here was specific: Durable Objects in one region, Workflows success rates, R2 latency in Eastern Europe, dashboard rate limiting for certain egress paths. These are narrow, often regional or component-level faults that a generic reachability check from outside will not reproduce, because the edge itself kept answering requests normally while a backend service behind it degraded. This is the recurring shape of a Cloudflare outage: the front door stays open while specific rooms inside have problems. Your own monitoring tells you whether your product is reachable. UptimeRobot now watches Cloudflare's side of that boundary too, so next time something breaks you know which side it was without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.