frob

What's the result of ``` curl -sL https://registry.ollama.ai/v2/library/deepseek-r1/manifests/7b curl -sL https://registry.ollama.ai/v2/library/deepseek-r1/blobs/sha256:f4d24e9138dd4603380add165d2b0d970bef471fac194b436ebd50e6147c6588 ```

@epicwhale And now output of ``` curl --head -v https://registry.ollama.ai/v2/library/deepseek-r1/blobs/sha256:96c415656d377afbff962f6cdb2394ab092ccbcbaab4b82525bc4ca800fe8a49 ```

OK, not the expected output. What happens when you run ``` ollama pull deepseek-r1:7b ```

Something is broken at Cloudfare. ``` ServiceUnavailable Please look at https://www.cloudflarestatus.com for issues or contact customer support. ``` [](https://www.cloudflarestatus.com/)

> Strange that it fails on deepseek models and not on others. I think R2 in the cloudfare CDN is distributed storage, some backend hosting a chunk of the GGUF...

> Which means, that the system ollama uses under-the-hood for downloads is not downloading things in sequence for deepseek-r1:7b. Is this normal behavior ? Yes. A download is split into...

deepseek-r1:7b: magnet:?xt=urn:btih:2JDGTZ7JT7KM24GCEXQQGDK4S3HKN23B&dn=models&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce

Use a torrent client to download the model, move the files to [OLLAMA_MODELS]( https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored).

The solution is for Cloudfare to fix their CDN. The workaround is to switch DNS servers or get the model from a different source.

[Server logs](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues) will aid in debugging.