Cloudflare favicon

Cloudflare outage on 2026-11-12

cloudflarestatus.com
November 2026 12 Minor incident

Cloudflare logged three separate incidents on 12 November 2026, touching DNSSEC configuration, Replicate predictions, and Durable Objects. The longest ran 5h 6m and affected Durable Objects error rates in North America. All three were Cloudflare-side faults, not something you could have fixed on your end.

Started

04:53 UTC

Duration

Lasted 33m

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, Durable Objects

What happened?

Cloudflare's status page recorded three incidents on 12 November, starting at 04:53 UTC and running through the day. The first, lasting 33 minutes, affected customers enabling or disabling DNSSEC signing. Cloudflare said it was investigating within minutes, identified the issue by 05:03, and had a fix live by 05:06. The second incident, starting at 08:30 UTC and lasting 3h 5m, hit Cloudflare Replicate, where customers saw an increase of 500 errors for predictions. Cloudflare identified the issue and said a fix was being implemented at 09:34, but no further update closing it out appears on the record. The third and longest incident began at 22:39 UTC and ran 5h 6m, affecting Durable Objects in North American colos. Cloudflare described it as an increased error rate caused by a sudden spike in traffic, and the single update filed says impact had already subsided by the time they posted and that they were monitoring. No user reports were filed during the window for any of the three incidents. Cloudflare's own filings are the only record of what happened, and in two of the three cases that record is thin: one update for the Durable Objects incident, two for Replicate.

Learning

UptimeRobot's own probes against Cloudflare's control plane, DNS, and edge data components held 100% uptime across the past 24 hours, 7 days, and 30 days, with no outage registered against this incident. That is not a contradiction. These three incidents sat in specific layers, DNSSEC signing configuration, Replicate's prediction pipeline, and Durable Objects error rates in one region, none of which a general availability probe is built to see. A product depending on Replicate predictions or Durable Objects in North America would have felt 500 errors or increased failures while a simple reachability check on the edge kept reporting green, because the edge itself stayed up. This is the usual shape of a partial outage: the front door is open, but one specific function behind it is broken. Watching your own endpoints tells you your product is failing, but not whether the fault sits with you or with Cloudflare. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke 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.