Repository-specific HTTP 503 when downloading nomic-ai/CodeRankEmbed

Models
1

I am unable to download any file from the public repository
nomic-ai/CodeRankEmbed.

Repository:
nomic-ai/CodeRankEmbed

Pinned revision:
3c4b60807d71f79b43f3c4363786d9493691f8b1

Environment:

  • Linux under WSL2
  • Python 3.12
  • huggingface_hub
  • Both anonymous and authenticated access tested

What works:

  • HfApi().model_info(“nomic-ai/CodeRankEmbed”) succeeds
  • It returns the expected revision and complete file list
  • Other Hugging Face repositories download normally from the same machine

What fails:

  1. File resolve endpoint:

https://huggingface.co/nomic-ai/CodeRankEmbed/resolve/3c4b60807d71f79b43f3c4363786d9493691f8b1/config.json

  1. Tree endpoint:

https://huggingface.co/api/models/nomic-ai/CodeRankEmbed/tree/3c4b60807d71f79b43f3c4363786d9493691f8b1?recursive=true

Both consistently return HTTP 503.

Latest resolver request:

Date:
Wed, 22 Jul 2026 17:51:39 GMT

Request ID:
Root=1-6a61032b-0401bfc35dc05d903715bcd4

CloudFront POP:
ATH51-P2

Response:
HTTP/2 503
x-error-message: Internal Error - We’re working hard to fix this as soon as possible!
x-cache: Error from cloudfront

Latest tree-listing request:

Date:
Wed, 22 Jul 2026 17:51:49 GMT

Request ID:
Root=1-6a610335-494af48c3124e1ab6d50289c

CloudFront POP:
ATH51-P2

Response:
HTTP/2 503
x-error-message: Internal Error - We’re working hard to fix this as soon as possible!
x-cache: Error from cloudfront

Response body:
{“error”:“Internal Error - We’re working hard to fix this as soon as possible!”}

This has also been reproduced through geographically different VPN routes and
CloudFront POPs:

  • Athens: ATH51-P2
  • Bucharest: OTP50-P3
  • Atlanta: ATL59-P13

The same repository-specific HTTP 503 occurs through all three routes.

Troubleshooting already attempted:

  • snapshot_download()
  • hf_hub_download() per file
  • hf download
  • repeated retries
  • anonymous and authenticated access
  • HF_HUB_DISABLE_XET=1
  • Git and Git LFS
  • exact pinned commit rather than main
  • multiple geographical VPN routes

Other repositories download correctly, including:

  • sentence-transformers/all-MiniLM-L6-v2
  • jinaai/jina-embeddings-v2-base-code
  • ibm-granite/granite-embedding-97m-multilingual-r2

Because even config.json returns HTTP 503, the issue does not appear to be
limited to the model.safetensors LFS/Xet object.

Could Hugging Face staff please inspect the repository’s backend or storage
state?

2

It appears that the issue has been resolved by now.

More specifically, there is evidence of a successful response as early as July 22, 2026 at 18:29:54 UTC: the pinned config.json currently resolves to a cached HTTP 200 response carrying that timestamp. In a separate Colab check on July 23 at approximately 23:32 UTC, the pinned config endpoint, the recursive tree endpoint, hf_hub_download(), and a fresh-cache snapshot download of all non-weight files also completed successfully. Therefore, the broader repository-specific 503 reported earlier is no longer reproducible, although this does not identify the original internal cause or establish the exact moment at which it was fixed.