- Level
- confirmed
- Worst impact
- Degraded
- Components
- Workers Builds
- Down Index
- 28of 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 51m it lasted.
Anything that failed between 2026-10-26 15:12 UTC and 2026-10-26 16:03 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 4
- investigating
Cloudflare is investigating increased delays running Workers builds. We are working to analyse and mitigate this problem. More updates to follow shortly.
provider
- identified
We are continuing to work on a fix for the issue.
provider
- monitoring
Fix has been deployed. Monitoring as queue times return to normal.
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-1cf2ea0e19
Is Replicate still down?
No, this incident was resolved 2026-10-26 16:03 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
51m, from 2026-10-26 15:12 UTC to 2026-10-26 16:03 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.