- Level
- confirmed
- Worst impact
- Degraded
- Components
- Workers Builds
- Down Index
- 27of 100
What to do
Check whether you use Replicate Workers Builds. 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 29m it lasted.
Anything that failed between 2026-11-05 19:51 UTC and 2026-11-05 20:20 UTC may need a replay.Subscribe to Replicate's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=replicate works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Replicate 3
- identified
Cloudflare is aware of and investigating an issue with Cloudflare Workers Builds which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
provider
- monitoring
Builds are being processed and we're working through backlog
provider
- resolved
Queue times have returned to normal.
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-3510ae0b65
Is Replicate still down?
No, this incident was resolved 2026-11-05 20:20 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
29m, from 2026-11-05 19:51 UTC to 2026-11-05 20:20 UTC, by the times Replicate posted.
What was affected?
Replicate named Workers Builds.
What caused it?
Replicate hasn't published a root cause. If it does, it shows here.
Where does this come from?
Replicate's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.