- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 100
What to do
Check whether your product depends on Cloudflare Workers. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-07-08 18:37 UTC and 2026-07-08 18:37 UTC may need a replay.Subscribe to Cloudflare Workers's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cloudflare-workers works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cloudflare Workers 1
- resolved
Cloudflare has identified and mitigated an issue which impacted a small subset of projects running Workers Builds between 2026-07-07 20:10 UTC to 2026-07-08 18:30 UTC. Customers experiencing the issue will have seen their builds fail with the error "A Worker named already exists in your account...".
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b6252e60d5
Is Cloudflare Workers still down?
No, this incident was resolved 2026-07-08 18:37 UTC. For Cloudflare Workers's live state, see https://down.guide/cloudflare-workers.
How long did it last?
0m, from 2026-07-08 18:37 UTC to 2026-07-08 18:37 UTC, by the times Cloudflare Workers posted.
What caused it?
Cloudflare Workers hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cloudflare Workers's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.