Cloudflare favicon

Cloudflare outage on 2026-11-13

cloudflarestatus.com
November 2026 13 Minor incident

Cloudflare had four separate incidents on 13 November 2026, touching Workers, a registry used for Replicate builds, and the 1.1.1.1 resolver in Canada. The longest, a Workers API availability problem, ran 22h 7m before Cloudflare closed it out. All four were on Cloudflare's side, not yours.

Started

13:54 UTC

Duration

Lasted 1h 25m

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, Recursive DNS, Workers

What happened?

Cloudflare logged four incidents on 13 November, starting at 13:54 UTC and running into the following day. The first was an elevated error rate for Workers startup affecting workers that use large amounts of memory, identified quickly and lasting 1h 25m. Twenty minutes later, a second and unrelated problem hit the r8.im registry used for Replicate model publishing and builds, restricting builds for 9h 58m before Cloudflare implemented a fix and moved to monitoring. The most significant incident started at 15:31 UTC: Cloudflare Workers API availability degraded, with customers seeing an increase in 5xx errors when deploying Workers or doing other API actions. Cloudflare identified that issue within 8 minutes and said a fix was implemented and being monitored by 15:42 UTC, but the incident itself stayed open on their status page for 22h 7m before full resolution. Late in the day, at 23:53 UTC, a fourth and distinct problem surfaced: users in Canada using the 1.1.1.1 public resolver were affected. Cloudflare's own update explains the cause plainly here, an active hijack of the 1.1.1.0/24 route from another network, with 1.0.0.1 and the IPv6 resolver prefixes unaffected throughout. That one resolved in 1h 8m once the other network fixed its route leak. Across all four incidents, Cloudflare's status page carries nine updates total and no user reports were filed in this window on our side. The affected components list spans Cloudflare Sites and Services, Workers, and Recursive DNS, three distinct parts of the stack failing independently on the same day.

Learning

Our probes watching Cloudflare's API control, DNS resolver, and edge data endpoints from the EU and North America stayed at 100% uptime across 24 hours, 7 days and 30 days, and this incident day was not flagged as a registered outage in our own monitoring history. That is not a contradiction. Three of the four incidents were narrow: a memory-threshold bug in Workers startup, a registry restriction for a specific third-party build pipeline, and a route hijack affecting one country's resolver traffic. A generic uptime check hitting Cloudflare's edge from elsewhere can sail through green while a specific API path, a specific registry, or a specific region's DNS traffic is broken. The Workers API incident is the one most likely to have hit you if you deploy through that API, since Cloudflare itself confirmed 5xx errors on deploy and other API actions for over 22 hours on their own clock. The takeaway is the same every time this happens: 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.