Version.storj.io not reachable via ipv6

[d4rk4]

Hi I’m now trying install IPv6 only storajing node and I found that IPv6 connectivity is broken for version.storj.io

root@v6bg0:~# ping -6 version.storj.io
PING version.storj.io(64:ff9b::22ad:a45a (64:ff9b::22ad:a45a)) 56 data bytes
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=2 Destination unreachable: No route
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=12 Destination unreachable: No route
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=13 Destination unreachable: No route
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=14 Destination unreachable: No route
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=15 Destination unreachable: No route
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=16 Destination unreachable: No route
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=17 Destination unreachable: No route
From be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1) icmp_seq=19 Destination unreachable: No route
^C
--- version.storj.io ping statistics ---
19 packets transmitted, 0 received, +8 errors, 100% packet loss, time 18994ms

root@v6bg0:~# traceroute -6 version.storj.io
traceroute to version.storj.io (64:ff9b::22ad:a45a), 30 hops max, 80 byte packets
 1  gw.spec.friendhosting.net (2001:67c:2f4c::1)  55.907 ms  55.822 ms  55.862 ms
 2  2a01:8740::3c (2a01:8740::3c)  56.066 ms  56.020 ms  56.082 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  be5230.126.ccr31.sof02.atlas.cogentco.com (2001:978:2:48::4c:1)  57.138 ms !N * *

[d4rk4]

It’s globally unaccessible, you may check it’s itself using ping command on HE Looking glass service for example - https://lg.he.net/

[d4rk4]

I rechecked with dig manually and now I see “global.tardigrade.io.” just don’t have any AAAA records. So Storj is still not ready for IPv6?

[Knowledge]

This topic has been discussed several times in the past. The following is some detail as to the issue…

IPv6 full Support again

I can definitely agree that the situation is frustrating. It’s also frustrating for a lot of us who are engineers on the project. We designed the system from the beginning to support IPv6; there wouldn’t be any need to rewrite software to enable it. Some satellites have had IPv6 endpoints already. I expect you’ve already heard this before, but for the sake of someone else reading the thread: the main thing stopping us from moving to another cloud provider and enabling IPv6 everywhere is that we…

[nerdatwork]

A good read https://www.ipxo.com/blog/ipv6-adoption/

Today, almost a decade later, only 20.9% of all websites support IPv6.

[Alexey]

HE and Cogent have an old issue with IPv6 routing, they did not negotiate the exchange, so it will not work as not worked for more than 3 years now (yeah, I know, this is not only sounds weird).