Live / Cloudflare / Incident
Cloudflare: Elevated error rate for workers startup
Cloudflare · cloudflare.comMinor incidentResolved2026-11-13 15:16 UTC
Public — what happened
Summary
Cloudflare said it saw a higher-than-normal rate of errors when Workers, its service for running customer code, were starting up, and that it affected Workers using large amounts of memory. The company reported the problem at 13:54 UTC on 2026-11-13, said it had identified the issue, and described itself as working on a fix. At 15:16 UTC Cloudflare posted that the incident was resolved, and it rated the issue as minor.
Affected
Workers
Timeline
- Started — 2026-11-13 13:54 UTC
- Identified — 2026-11-13 13:54 UTC
- Resolved — 2026-11-13 15:16 UTC · 1h 22m after it started
What SquidGrid measured
SquidGrid measured 193 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.