- Level
- confirmed
- Worst impact
- Degraded
- Replicate says
- 2026-11-14 19:41 to 20:03 UTC (22m)
- Components
- R2
- Regions
- us
Summary
Replicate says R2 buckets in West North America (WNAM) had elevated error rates from 19:41Z to 20:03Z UTC on 2026-11-14. The incident is now resolved.
Written by anthropic/claude-haiku-5.5 from Replicate's own updates.
What to do
Check whether you use Replicate R2 in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 40m it lasted.
Anything that failed between 2026-11-14 19:41 UTC and 2026-11-14 20:20 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 2
- resolved
There were elevated error rates for WNAM based buckets from 19:41Z to 20:03Z UTC
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-f13cb96c9c
Is Replicate still down?
No, this incident was resolved 2026-11-14 20:20 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
40m, from 2026-11-14 19:41 UTC to 2026-11-14 20:20 UTC, by the times Replicate posted.
What was affected?
Replicate named R2 in us.
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.