Cloudflare favicon

Cloudflare outage on 2026-10-21

cloudflarestatus.com
October 2026 21 Minor incident

Cloudflare had two separate incidents on 21 October: slower loading times for some traffic in India lasting 3h 18m, and a shorter 46-minute spell of elevated error rates for Durable Objects in its Lisbon facility. Both were filed and resolved by Cloudflare itself, and the fault sits on its side, not yours.

Started

16:42 UTC

Duration

Lasted 3h 18m

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, Lisbon, Portugal - (LIS), Europe, CDN/Cache

What happened?

Cloudflare logged two unrelated incidents on 21 October, affecting different parts of its network. The first started at 16:42 UTC, described as increased latency affecting some traffic in India, with Cloudflare warning that affected users may see slower loading times. Cloudflare posted a second update at 18:51 UTC saying it had identified and implemented a fix and was monitoring the results, and the incident closed out at 3h 18m total. The second incident began later that day at 23:50 UTC, affecting Durable Objects in Cloudflare's Lisbon (LIS) facility, with Cloudflare reporting higher than usual error rates there. That one ran for 46 minutes with only the opening update on record, no follow-up confirming a fix or a cause. Across both incidents, Cloudflare published three updates in total, and none of them name a root cause for either problem. The affected components list spans Cloudflare Sites and Services, CDN/Cache, Europe, the Lisbon facility specifically, and Durable Objects, five components touched across the two events. No user reports were filed during either window on this record. Cloudflare's own status history for the past 90 days shows 192 incidents with a median duration of 1 hour 55 minutes, so a 3h 18m incident sits above that median while the 46-minute one sits below it. Over all time Cloudflare has logged 3,439 incidents on its status page. Neither incident on this day carries a published post-mortem.

Learning

UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components, from both EU and North America regions, stayed at 100% uptime over 24 hours and 7 days, and 99.996% over 30 days, with no registration against either incident on this day. That is not a contradiction. Cloudflare's incidents were scoped narrowly, regional latency in India and an error rate bump for Durable Objects in one facility in Lisbon, and a general health probe checking core endpoints from other regions has no reason to see either. This is the common shape of a partial outage: the provider's status page names a specific region or product, your monitoring checks a different path entirely, and both readings are true at once. If your product routes traffic through India or leans on Durable Objects in Lisbon specifically, you could have been affected while a broad uptime check showed nothing wrong. Watching your own endpoints only tells you your side is up, it cannot tell you whether the edge network or a specific regional facility you depend on is degraded. 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.