• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Routing troubles, only via tunnelbroker, December 2022

Started by jrcovert, December 04, 2022, 05:18:24 AM

Previous topic - Next topic


Recently I'm experiencing IPv6 connectivity issues through tunnelbroker to various sites, preventing webpages from loading:

Specific example:

Through tunnelbroker: ping6 substackcdn.com
PING6(56=40+8+8 bytes) 2001:470:.... --> 2600:9000:24eb:ee00:4:b4b9:d3c0:93a1
--- substackcdn.com ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

From a cloud server with direct IPv6 service:

ping6 substackcdn.com
PING substackcdn.com(2600:9000:...) 56 data bytes
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=0 ttl=56 time=1.17 ms
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=1 ttl=56 time=1.21 ms
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=2 ttl=56 time=1.18 ms
64 bytes from 2600:9000:2269:7200:4:b4b9:d3c0:93a1: icmp_seq=3 ttl=56 time=1.25 ms
--- substackcdn.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.173/1.207/1.252/0.052 ms, pipe 2


I'm experiencing the same thing from the tserv4.nyc4 tunnel server.

It seems to be certain Cloudfront prefixes aren't accessible from HE. I'm unsure why currently, but I've been seeing this problem for over a month.

The prefixes I cannot access that I've seen so far are...
2600:9000:20ea::/48 (example IP: 2600:9000:20ea:6a00:c:132:48e:f021)
2600:9000:24eb::/48 (example IP: 2600:9000:24eb:6a00:c:132:48e:f021)
2600:9000:20ee::/48 (example IP: 2600:9000:20ee:4800:3:ce9:7f80:93a1)

I have also tried pinging from a cloud server and they all work. It's just from HE that they do not.

What tunnel server are you on? Can you try pinging those 3 example IPs and providing results?
I suggest you also email support@he.net to let them know this is affecting more than just me.

Can people on other tunnel servers please also try and see what happens? I'm wondering if this is only affecting the same tunnel server I'm on.