Cloudflare ran two separate incidents on 9 November 2026, one affecting Workers changes for 9h 34m and another affecting network performance in Eastern North America for 3h 39m. Both were faults on Cloudflare's side, not yours.
Started
16:15 UTC
Duration
Lasted 9h 34m
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, Network, Workers
What happened?
Cloudflare's status page logged two incidents starting within 19 minutes of each other on 9 November 2026. The first began at 16:15 UTC, titled "Changes made to Workers may be delayed or disrupted". Cloudflare's own text is specific about scope: it says impact is limited to creating, editing and deleting Workers, and that Workers already deployed are unaffected. Cloudflare moved to monitoring by 16:35 UTC, and the incident closed after 9h 34m. The second incident started at 16:34 UTC, titled "Network Performance Issues in Eastern North America", and ran for 3h 39m before resolving. Cloudflare's updates for both incidents follow the same thin pattern: investigating, identified, monitoring, with no further detail on root cause in either case. No post-mortem has been published for either incident. Three components were listed as affected across the day: Cloudflare Sites and Services, Workers, and Network. No user reports were filed during the window for either incident. Cloudflare's 90 day history shows 207 incidents with a median duration of 1 hour 50 minutes, so this day's longer incident sat well above that median.
Learning
UptimeRobot's own probes against Cloudflare's api-control, dns-1111 and edge-data components, from both EU and North American regions, stayed at 100% uptime over 24 hours, 7 days and 30 days, with this incident not registered against them. That is not a contradiction. The Workers issue affected the control plane used to create, edit and delete Workers, not the deployed Workers themselves, and the network performance issue was geographically scoped to Eastern North America, so probes outside that path or outside that control plane action can legitimately read clean while Cloudflare's own status page shows active incidents. If you were only watching your own endpoints, a disruption to editing or deploying Workers, or a regional network slowdown, could easily pass unnoticed until you tried to make a change or a user in that region complained. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.