Cloudflare favicon

Cloudflare outage on 2026-11-11

cloudflarestatus.com
November 2026 11 Minor incident

Cloudflare logged four separate incidents on 11 November 2026, touching Replicate model uploads, Worker Builds, SSL certificate provisioning and network performance near LAX. The longest, affecting Replicate input uploads and model builds via r8.im, ran for 45h 13m before Cloudflare confirmed a fix. All four were Cloudflare's own infrastructure problems, not anything in your deployment.

Started

04:33 UTC

Duration

Lasted 1d 21h

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, SSL Certificate Provisioning, Workers, Containers, Workers Builds

What happened?

Cloudflare's status page recorded four incidents on 11 November, starting at 04:33 UTC and running into the following day. The first and longest began with Replicate input uploads failing and model builds and pushes via r8.im becoming unavailable entirely. Cloudflare said it had identified the issue within 38 minutes of opening the incident but then spent over 17 hours on "degraded" impact before the 22:55 UTC update reporting a fix in monitoring. That gap between "identified" at 05:11 and "fix implemented" at 22:55 is long against Cloudflare's own history, where the 90 day median incident runs 1 hour 55 minutes. The second incident, a Worker Builds issue, lasted only 16 minutes, with existing Workers and Containers explicitly unaffected according to Cloudflare's own text. The third was an SSL certificate provisioning fault lasting 2h 24m, limited to deploying new custom certificates, Cloudflare stated that certificates already in production remained unaffected. The fourth was a 28 minute network performance degradation localised to LAX and Western North America. Across all four, Cloudflare published identified and monitoring updates but no post-mortem has been filed for any of them. No user reports were filed during the window on this page. Five components appear on Cloudflare's own list as affected across the day: Cloudflare Sites and Services, Workers, Containers, Workers Builds and SSL Certificate Provisioning.

Learning

UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data endpoints, run from EU and NA regions every 60 seconds, stayed green throughout, 100% uptime over 24 hours, 7 days and 30 days. That is not a contradiction. The failures Cloudflare described sat in specific workflows, Replicate uploads, Worker Builds, certificate deployment, not in the edge resolution and control paths those probes check. A product can have fully reachable DNS and API control while the pipeline it depends on for builds or certificate issuance is stuck behind the scenes. This is the pattern to recognise in your own product: your uptime checks hitting your own endpoints tell you your service answered, they say nothing about whether a build pipeline or certificate request routed through a vendor actually completed. Cloudflare's 90 day history shows 208 incidents with a median duration of under two hours, so single incidents clearing 45 hours stand out even against a provider with frequent, usually short faults. 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.