- Level
- confirmed
- Worst impact
- Degraded
- Components
- Recursive DNS
- Regions
- ca
Summary
Cloudflare says its 1.1.1.1 public resolver had issues for users in Canada, caused by an active hijack of 1.1.1.0/24. The network with the offending route leak has fixed the issue on its end, and Cloudflare is monitoring the effect of that fix.
Written by anthropic/claude-haiku-5.5 from Replicate's own updates.
What to do
Check whether you use Replicate Recursive DNS in ca. 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 1h 8m it lasted.
Anything that failed between 2026-11-13 23:53 UTC and 2026-11-14 01:01 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 4
- investigating
Cloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Canada that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.
provider
- identified
We have reached out to the network where we see an active hijack of 1.1.1.0/24. 1.0.0.1 and public resolver IPv6 prefixes are fully operational and reachable at this time.
provider
- monitoring
The network with the offending route leak has fixed the issue on their end. We are currently monitoring the effect of this fix.
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-521d9ca390
Is Replicate still down?
No, this incident was resolved 2026-11-14 01:01 UTC. For Replicate's live state, see https://down.guide/providers/replicate.
How long did it last?
1h 8m, from 2026-11-13 23:53 UTC to 2026-11-14 01:01 UTC, by the times Replicate posted.
What was affected?
Replicate named Recursive DNS in ca.
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.