Live / Cloudflare / Incident
Cloudflare: Changes made to Workers may be delayed or disrupted
Cloudflare · cloudflare.comMinor incidentResolved2026-11-10 01:46 UTC
Public — what happened
Summary
Cloudflare said that starting at 16:15 UTC on 2026-11-09 it was investigating problems with creating, editing and deleting Workers, which it rated as minor. The company said only changes were affected, and Workers that were already deployed kept running normally. Cloudflare reported at 16:22 UTC that the issue had been identified and a fix was in progress, then said at 16:35 UTC that it was monitoring. It marked the incident resolved at 01:46 UTC on 2026-11-10.
Affected
Workers
Timeline
- Started — 2026-11-09 16:15 UTC
- Investigating — 2026-11-09 16:15 UTC
- Identified — 2026-11-09 16:22 UTC
- Monitoring — 2026-11-09 16:35 UTC
- Resolved — 2026-11-10 01:46 UTC · 9h 31m after it started
What SquidGrid measured
SquidGrid measured 277 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Cloudflare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Cloudflare: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Cloudflare report →
More from Cloudflare
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.