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

hongkong ipv6 tunnel server down??

Started by chonwingcong, July 14, 2025, 05:50:42 PM

Previous topic - Next topic

chonwingcong

PING 216.218.221.6 (216.218.221.6) 56(84) bytes of data.

^C
--- 216.218.221.6 ping statistics ---
33 packets transmitted, 0 received, 100% packet loss, time 32753ms

binnychan


chonwingcong

ping per subnet ip ok,server ipv4 and ipv6 is down
PING 216.218.221.2 (216.218.221.2) 56(84) bytes of data.
64 bytes from 216.218.221.2: icmp_seq=1 ttl=58 time=3.29 ms
64 bytes from 216.218.221.2: icmp_seq=2 ttl=58 time=3.58 ms
64 bytes from 216.218.221.2: icmp_seq=3 ttl=58 time=3.27 ms
64 bytes from 216.218.221.2: icmp_seq=4 ttl=58 time=3.42 ms
64 bytes from 216.218.221.2: icmp_seq=5 ttl=58 time=3.39 ms
64 bytes from 216.218.221.2: icmp_seq=6 ttl=58 time=3.50 ms
^C
--- 216.218.221.2 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 3.267/3.406/3.578/0.108 ms

XQZR

I am also having the same issue.

I opened a ticket(in email)'[HE#6647982]',but 72h+ No response.

I don't think the issue is caused by the underwater cable disruption. This is because the tunnel server is local, and tserv1 (216.218.221.2) is functioning properly.

jslhk

Same here.
PING 216.218.221.6 (216.218.221.6) 56(84) bytes of data.
^C
--- 216.218.221.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9240ms
Although https://tunnelbroker.net/status.php shows that tserv20.hkg1 is Up without issue.