Cache.nixos-cuda.org it's unreachable

Since yesterday (December 15, 2025) the nixos-cuda team cache it’s unreachable when trying to switch a nixos system logging stuff like:

warning: error: unable to download '``https://cache.nixos-cuda.org/mhf691zwwjrqi8b6an14pblyqbzwn1v2.narinfo``': Could not connect to server (7) Failed to connect to ``cache.nixos-cuda.org`` port 443 after 6 ms: Could not connect to server; retrying in 258 ms

Talking via Matrix in the NixOS CUDA some guy tried to reproduce this by running:
❯ curl ``https://cache.nixos-cuda.org/mhf691zwwjrqi8b6an14pblyqbzwn1v2.narinfo`` missed hash⏎

But instead I get:

❯ curl https://cache.nixos-cuda.org/mhf691zwwjrqi8b6an14pblyqbzwn1v2.narinfo curl: (7) Failed to connect to cache.nixos-cuda.org port 443 after 675 ms: Could not connect to server

Running traceroute I get this:
❯ traceroute ``cache.nixos-cuda.org
traceroute to ``hydra.nixos-cuda.org`` (37.27.129.22), 64 hops max
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *

And obviously it’s not a DNS issue because I’m getting an IP but dig returns:
cache.nixos-cuda.org``. 300 IN CNAME ``hydra.nixos-cuda.org``.
hydra.nixos-cuda.org``. 300 IN A 37.27.129.22
nixos-cuda.org``. 300 IN NS ``helium.ns.hetzner.de``.
nixos-cuda.org``. 300 IN NS ``hydrogen.ns.hetzner.com``.
nixos-cuda.org``. 300 IN NS ``oxygen.ns.hetzner.com``.

They also told me these server it’s located in Hetzner Helsinki, which I’ve tried to see if there was a routing issue from where I am (Argentina) to there using https://hel1-speed.hetzner.com/ but I can reach these no problem. Also tried curling from a mobile phone using mobile data to discard possible network issues with my main PC or my local network, but it’s still unreachable.

It’s weird that your traceroute doesn’t show any hop at all.

https://www.locabrowser.com/ shows that the website is reachable from various locations across the globe. What is your network location?

I see no South American country listed there tho. So I’m not sure if we can conclude that it’s reachable here.

My network is located in Argentina.

I confirmed with another friend in the country that also cannot reach the host.

Also, my first initial traceroute was trash, I run it again and this is what I get:
❯ sudo traceroute ``cache.nixos-cuda.org
traceroute to ``hydra.nixos-cuda.org`` (37.27.129.22), 64 hops max
1 192.168.1.1 0.463ms 0.410ms 0.476ms
2 * 6.286ms 4.488ms 3.511ms
3 * * *
4 * * *
5 * 5.120ms * *
6 * 4.814ms !N 2.586ms !N 2.801ms !N

I understand that the !N means the network it’s unreachable from there. Probably a problem with my ISP?

@picnoir thinks it might be a BGP loop. You can try to figure out who you AS is and use a looking glass to see what the root is.

2 Likes

Interesting how he deduced that with so little information. Running some right now to get more information, but at this point I’m doing this more for the food for thought than anything else because I have covered from my network of friends that at least 3 ISPs from my city cannot reach the host also.

But funny enough the first one I tried from this site from another city in my country (Rosario), it’s able to reach the host no problem:

ROSARIO ARGENTINA Ping results for: 37.27.129.22 (static.22.129.27.37.clients.your-server.de)
Target: 37.27.129.22 with 64 data bytes Success rate sent/received = (1/1) packets
Round-Trip min/avg/max = 243ms/243ms/243ms

But also Buenos Aires as well:

BUENOSAIRES ARGENTINA Ping results for: 37.27.129.22 (static.22.129.27.37.clients.your-server.de)
Target: 37.27.129.22 with 64 data bytes Success rate sent/received = (1/1) packets
Round-Trip min/avg/max = 240ms /240ms /240ms


image

Ok, seems like that from my AS it’s not able to make a ping to this IP which it’s reasonable because my IP lives there and I cannot connect as well.

Do you think this is somewhat reportable somewhere? lol

1 Like

Got resolved finally.