Packet loss on Frankfurt tunnel - what should i do?

[sumehl]

Hello all,

my IPV4 Endpoint is 216.66.80.30. Since 3.6.2020 i have packet loss. Internet connection is fine, because other ipv4 targets are working fine. Please see my attached graphs.

https://darkdevil.osit.cc/nextcloud/s/FogYy7RQTykXHfS?path=%2Fshares%20for%20forums%2FTunnelbroker

So what can i do to solve the problem?

Very Thanks and best Regards
sumehl

[sumehl]

Problem exists. On the Speedtests last days, IPV4 was on  77Mbps and IPV6 was on 53Mbps. So what should i do, change from Frankfurt to ...?

[SID6581]

Experiencing the same problem on the Amsterdam tunnel server (tserv1.ams1.he.net.) It started around the same date.

I have tried emailing support about it but they stopped replying :(

[sumehl]

Thank you for the information. And it won't get any better.  :'(  :-\

[SID6581]

Bump, this is still an issue. Can't really complain about a free service, but it's kind of annoying.

Code Select Expand

# ping 216.66.84.46
PING 216.66.84.46 (216.66.84.46) 56(84) bytes of data.
64 bytes from 216.66.84.46: icmp_seq=1 ttl=60 time=10.7 ms
64 bytes from 216.66.84.46: icmp_seq=2 ttl=60 time=10.4 ms
64 bytes from 216.66.84.46: icmp_seq=3 ttl=60 time=10.8 ms
64 bytes from 216.66.84.46: icmp_seq=4 ttl=60 time=10.4 ms
64 bytes from 216.66.84.46: icmp_seq=5 ttl=60 time=11.3 ms
64 bytes from 216.66.84.46: icmp_seq=6 ttl=60 time=12.0 ms
64 bytes from 216.66.84.46: icmp_seq=7 ttl=60 time=10.2 ms
64 bytes from 216.66.84.46: icmp_seq=8 ttl=60 time=46.5 ms
64 bytes from 216.66.84.46: icmp_seq=9 ttl=60 time=10.9 ms
64 bytes from 216.66.84.46: icmp_seq=10 ttl=60 time=10.8 ms
64 bytes from 216.66.84.46: icmp_seq=11 ttl=60 time=83.7 ms
64 bytes from 216.66.84.46: icmp_seq=12 ttl=60 time=10.7 ms
64 bytes from 216.66.84.46: icmp_seq=13 ttl=60 time=10.6 ms
64 bytes from 216.66.84.46: icmp_seq=14 ttl=60 time=10.3 ms
64 bytes from 216.66.84.46: icmp_seq=15 ttl=60 time=10.7 ms
64 bytes from 216.66.84.46: icmp_seq=16 ttl=60 time=10.3 ms
64 bytes from 216.66.84.46: icmp_seq=17 ttl=60 time=10.6 ms
64 bytes from 216.66.84.46: icmp_seq=18 ttl=60 time=10.2 ms
64 bytes from 216.66.84.46: icmp_seq=19 ttl=60 time=10.8 ms
64 bytes from 216.66.84.46: icmp_seq=20 ttl=60 time=10.8 ms
64 bytes from 216.66.84.46: icmp_seq=21 ttl=60 time=10.3 ms
64 bytes from 216.66.84.46: icmp_seq=22 ttl=60 time=13.3 ms
64 bytes from 216.66.84.46: icmp_seq=23 ttl=60 time=10.9 ms
64 bytes from 216.66.84.46: icmp_seq=24 ttl=60 time=11.0 ms
64 bytes from 216.66.84.46: icmp_seq=25 ttl=60 time=42.3 ms
64 bytes from 216.66.84.46: icmp_seq=26 ttl=60 time=10.9 ms
64 bytes from 216.66.84.46: icmp_seq=27 ttl=60 time=10.7 ms
64 bytes from 216.66.84.46: icmp_seq=29 ttl=60 time=11.1 ms
64 bytes from 216.66.84.46: icmp_seq=30 ttl=60 time=11.5 ms
64 bytes from 216.66.84.46: icmp_seq=31 ttl=60 time=114 ms
64 bytes from 216.66.84.46: icmp_seq=32 ttl=60 time=10.3 ms
64 bytes from 216.66.84.46: icmp_seq=33 ttl=60 time=10.6 ms
64 bytes from 216.66.84.46: icmp_seq=34 ttl=60 time=11.0 ms
64 bytes from 216.66.84.46: icmp_seq=35 ttl=60 time=10.9 ms
^C
--- 216.66.84.46 ping statistics ---
35 packets transmitted, 34 received, 2.85714% packet loss, time 34049ms
rtt min/avg/max/mdev = 10.177/17.977/113.854/21.996 ms


Code Select Expand


                            My traceroute  [v0.94]
82.169.212.38 -> 216.66.84.46            2020-11-17T16:11:17+0100
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                     Packets               Pings
Host                              Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 195-190-228-169.fixed.kpn.net   0.0%   132    5.9  11.8   4.8  47.7  11.1
2. kpn-as1136.kpn-rt-dc2.nl-ix.ne 89.3%   131   11.1  10.5  10.0  11.3   0.4
3. (waiting for reply)
4. 100ge2-1.core1.ams1.he.net      0.0%   131   10.8  10.9   9.8  12.2   0.4
5. tserv1.ams1.he.net              0.8%   131   10.7  18.3  10.1 110.0  20.2

I'm also seeing the same packet loss and latency spikes when pinging tserv1.ams1.he.net from a native IPv6 address....

[mennig]

Switched from Frankfurt to London   :'(

[SID6581]

I did the same, that solved it thankfully.

I just checked and tserv1.fra1 and tserv1.ams1 are still experiencing the same problem, but it's a bit worse on tserv1.ams1.