Cloudflare favicon

Cloudflare outage on 2026-11-14

cloudflarestatus.com
November 2026 14 Minor incident

If you use Cloudflare's R2 storage or Tiered Cache, you may have seen errors for about an hour and a quarter on 14 November 2026. The fault sat inside Cloudflare's own network, not in anything you run.

Started

05:30 UTC

Duration

Lasted 1h 15m

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, North America, R2, Chicago, IL, United States - (ORD), Newark, NJ, United States - (EWR)

What happened?

Cloudflare logged one incident on this day, starting at 05:30 UTC and lasting 1h 15m. The first update said Cloudflare was investigating an issue with R2, with customers in Chicago, IL seeing 503 errors. Thirteen minutes later, at 05:43 UTC, Cloudflare gave a fuller account: a network connectivity issue between several of its data centres, starting at 05:00 UTC, had caused a small percentage of requests to fail. R2 customers may have seen HTTP 500 errors, and requests served through Tiered Cache may have returned 520, 522 or 524 errors. Chicago (ORD) and Newark (EWR) saw the highest error rates, with other locations affected at lower rates. That second update also said error rates had dropped close to normal by 05:30 UTC, and that Cloudflare was continuing to monitor while the underlying network issue was resolved. Five components appear on the affected list: Cloudflare Sites and Services, North America as a region, R2, and the two named data centres. No further update was filed after 05:43 UTC, and no post-mortem has been published explaining what caused the connectivity issue between data centres. No user reports were filed during this window on our side. Cloudflare's own history shows this kind of incident is routine for them: 213 incidents in the last 90 days, with a median duration of 1 hour 55 minutes, so this one resolved faster than their typical case.

Learning

UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components, across EU and NA regions, showed 100% uptime over the past 24 hours, 7 days and 30 days, and this incident was not registered against our monitoring. That is not a contradiction. R2 storage requests and Tiered Cache lookups travel a different path than the control-plane and DNS endpoints our probes check, and a connectivity problem between a handful of data centres can degrade one service's request path while leaving the rest of the edge untouched. This is the shape to watch for: a narrow, internal routing fault that shows up as elevated error codes on specific products and specific locations, rather than a wholesale outage visible everywhere. If your own uptime checks hit a general Cloudflare endpoint rather than the exact R2 or cache path your product depends on, you could stay green while your users see 500s and 520s. 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.