Cloudflare favicon

Cloudflare outage on 2026-11-10

cloudflarestatus.com
November 2026 10 Minor incident

Cloudflare logged four separate incidents on 10 November 2026, touching Workers event subscriptions, analytics dashboards, Replicate's OpenAI predictions and network performance in St. Louis. The first of these, affecting Workers Event Subscription events, started at 01:53 UTC and was still unresolved as of Cloudflare's last update.

Started

01:53 UTC

Duration

Not closed by vendor

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: North America, St. Louis, MO, United States - (STL), Cloudflare Sites and Services, Analytics, Workers

What happened?

Cloudflare's status page recorded four incidents across the day. The first began at 01:53 UTC: changes to Workers stopped producing Event Subscription events. Cloudflare said it had intentionally disabled the feature because of an ongoing issue, and was clear that Workers themselves kept deploying and running normally, only the event subscription mechanism was affected. By 05:05 UTC Cloudflare said the cause had been identified and a fix was being worked on, but no further update had landed, so the incident remains open on Cloudflare's own timeline. The second incident, an Account Analytics Filter Issue starting at 08:02 UTC, ran a short course: identified at 08:12, fixed and monitored by 08:25, for a total of 44 minutes. The third, starting at 18:35 UTC, hit predictions on official OpenAI models routed through Replicate, with some requests failing on a 401 token_invalidated error; Cloudflare said a fix was being implemented by 18:43, and the incident closed out at 32 minutes. The fourth began at 22:50 UTC: network performance issues specific to St. Louis, Missouri, with Cloudflare reporting a fix implemented and results being monitored straight away, closing at 2 hours 22 minutes. No user reports were filed during the window for any of these four. Cloudflare's own filings are the only record of what happened; there is no independent confirmation beyond what the company itself posted, and each filing carries exactly as much weight as Cloudflare chose to give it.

Learning

UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data endpoints in the EU and North America stayed at 100% uptime across the last 24 hours, 7 days and 30 days, and none of the four incidents above triggered a change in that reading. That is not a contradiction. The faults Cloudflare described sat in specific product layers, Workers event subscriptions, an analytics dashboard filter, a third-party inference pipeline, and a regional network path, none of which map onto a simple edge reachability check from an external monitor. Your own monitoring, watching your endpoints behind Cloudflare, would show the same thing: everything green, because the edge itself kept routing traffic. This is the general shape of a provider-side partial outage, the parts that break are narrower than "Cloudflare is down," and they are invisible to uptime checks built to catch full outages rather than feature-level breakage. 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.