- Level
- confirmed
- Worst impact
- Degraded
- Replicate says
- 2026-10-26 08:21 to 09:03 UTC (42m)
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 42m it lasted.
Anything that failed between 2026-10-26 08:21 UTC and 2026-10-26 09: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 1
- resolved
Between 08:21 and 09:03 UTC, Cloudflare observed localized network degradation affecting traffic routed through the Chicago (ORD) data center. Customers may have experienced intermittent latency and connection timeouts during this period.
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-043a1a661c
Is Replicate still down?
No, this incident was resolved 2026-10-26 09:03 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
42m, from 2026-10-26 08:21 UTC to 2026-10-26 09:03 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.