- Level
- confirmed
- Worst impact
- Degraded
- Components
- Replicate
- Down Index
- 39of 100
What to do
Check whether you use Replicate Replicate. 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 1h 54m it lasted.
Anything that failed between 2026-09-24 20:40 UTC and 2026-09-24 22:34 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 1
- resolved
The impacted backend has been redeployed, and all related services should now be back up and running. There may be some increased latency as they continue to come online.
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-089c10a306
Is Replicate still down?
No, this incident was resolved 2026-09-24 22:34 UTC. For Replicate's live state, see https://down.guide/replicate.
How long did it last?
1h 54m, from 2026-09-24 20:40 UTC to 2026-09-24 22:34 UTC, by the times Replicate posted.
What was affected?
Replicate named Replicate.
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.