- Level
- confirmed
- Worst impact
- Degraded
- Components
- Workers
- Down Index
- 31of 100
What to do
Check whether you use Replicate 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 3h 26m it lasted.
Anything that failed between 2026-10-26 21:48 UTC and 2026-10-27 01:15 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
- investigating
We are investigating reports that some Workers Cron Triggers are running late, being skipped, or running more than once. Affected customers may see scheduled Workers invocations that do not run on time or run more than once. We will post an update as we learn more.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
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-93074ee963
Is Replicate still down?
No, this incident was resolved 2026-10-27 01:15 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
3h 26m, from 2026-10-26 21:48 UTC to 2026-10-27 01:15 UTC, by the times Replicate posted.
What was affected?
Replicate named Workers.
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.