- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on 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 18d 8h it lasted.
Anything that failed between 2026-10-05 13:00 UTC and 2026-10-23 21:00 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
Between October 5 at 1:00 PM UTC and October 23 at 9:00 PM UTC, some customers may have experienced missing log events, incomplete traces, or inconsistent issue counts due to ingestion pipeline capacity limits. Traffic and Workers were not affected, and customers will not be billed for dropped events. Capacity has since been increased, and service has 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-4b3690c145
Is Replicate still down?
No, this incident was resolved 2026-10-23 21:00 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
18d 8h, from 2026-10-05 13:00 UTC to 2026-10-23 21:00 UTC, by the times Replicate posted.
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.