- Level
- confirmed
- Worst impact
- Degraded
- Components
- CDN Cache Purge
Summary
Replicate says a bug in its purge pipeline is delaying purges for FedRAMP customers, so stale content may be served until it expires. Non-FedRAMP customers are not affected. The issue is identified, and the provider says it is still working on a fix.
Written by anthropic/claude-haiku-5.5 from Replicate's own updates.
What to do
Check whether you use Replicate CDN Cache Purge. 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.Switch to another region or a fallback provider while it is open, if you have one.
Otherwise back off retries and queue work, so you don't add load while it recovers.Watch Replicate's own updates; this page re-reads them every minute.
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 2
- investigating
Cloudflare has identified a bug with our purge pipeline impacting fedramp customers. Stale content may be served until expired. Non-fedramp customers are not impacted.
provider
- identified
We are continuing to work on a fix for the issue.
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-0f8243ffd0
Is Replicate down right now?
Replicate reports degraded (Fedramp Customers have Delayed Purges), open since 2026-11-06 17:47 UTC. Live state for every component: https://down.guide/providers/replicate.
What was affected?
Replicate named CDN Cache Purge.
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.