Cloudflare favicon

Cloudflare outage on 2026-11-06

cloudflarestatus.com
November 2026 6 Minor incident

Cloudflare logged three separate incidents on 6 November 2026, hitting Singapore network performance, Wrangler/Pages/Workers Builds deployments, and purge processing for FedRAMP customers. The longest of the three, the FedRAMP purge delay, ran for 142h 49m before Cloudflare closed it. All three were Cloudflare-side faults, not anything in your own setup.

Started

08:54 UTC

Duration

Lasted 1h 50m

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, CDN Cache Purge, Wrangler, Workers Builds, Pages, Singapore, Singapore - (SIN), Asia

What happened?

Cloudflare's status page recorded three distinct incidents starting on 6 November 2026. The first began at 08:54 UTC, described as network performance issues in the Singapore region, and ran for 1h 50m before Cloudflare moved it to monitoring at 09:32 UTC with no further detail on cause. The second started at 09:47 UTC and covered Wrangler deployments, Pages, and Workers Builds, with Cloudflare warning that "Users may observe from failed uploads." That one was shorter, at 25 minutes, with a fix implemented and monitoring confirmed by 09:53 UTC. The third, and by far the longest, started at 17:47 UTC: Cloudflare identified "a bug with our purge pipeline impacting fedramp customers," meaning stale content could be served until it expired naturally. Cloudflare explicitly stated that "Non-fedramp customers are not impacted," narrowing that incident to a specific customer segment. That purge issue ran for 142h 49m, far longer than Cloudflare's own 90-day median incident length of 1 hour 55 minutes across 208 incidents. Seven components appear across the day's incidents: Singapore, Asia, Cloudflare Sites and Services, Wrangler, Workers Builds, Pages, and CDN Cache Purge. No user reports were filed during the window for any of the three incidents. Cloudflare published six updates in total across the day, and no post-mortem has been published for any of them.

Learning

UptimeRobot's own probes against Cloudflare's api-control, dns-1111, and edge-data components, run from EU and NA regions, held 100% uptime across the 24-hour, 7-day, and 30-day windows, and this incident was not registered against those checks. That is not a contradiction. The three incidents here were narrow: a regional network degradation in Singapore, a deployment pipeline fault affecting Wrangler, Pages and Workers Builds, and a purge pipeline bug scoped specifically to FedRAMP customers serving stale cached content. None of those map to the general edge, DNS, or control-plane paths that external synthetic checks exercise from outside Cloudflare's infrastructure. A purge delay in particular is invisible to a probe checking that a resource responds, since the response still arrives, just with outdated content behind it. If your product depends on Wrangler deployments, Workers Builds, or purge timing for FedRAMP compliance, your own uptime checks against your front door will not show you this kind of failure because the layer that broke sits further back in Cloudflare's pipeline. 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.