Mine still very slow today. I will try to use usb-tethering and compare the speed.
Yeah, mine is dogshit today. Not affecting web browsing or videos, but trying to play a game I’m getting like 10k MS and constant D/Cs.
My 500/500 is also fully used, but it seems like the routing (especially to european servers) is not good.
That’s why I assumed it might be a underwater cable problem again.
Interesting, the server I’m playing on is in the UK so that tracks with what I’m experiencing.
Note that by default, speedtest.net will use you a server close to you. Often, that’s exactly what you want because you want to test the connection from your home to the provider:
They also allow to change the server (it’s a bit hidden: You need to click settings first, then wait quite a bit for the list to load and then chose a server in the list). For example, testing to Frankfurt, Germany:
And once to London, England:
And once Potsdam, NY, US:
Note the much higher ping (as expected…). But overall, now everything looks fine for my connection at the moment, I’d say. Except that the ping to Frankfurt is considerably higher than the one to London…
2 Likes
I stream to Europe and no issues…
Yeah, that works too! It’s just not directly obvious that this feature can be used to test connections to other countries and such.
1 Like
Does anyone NOT have HiNet broadband at home and could ping this server 95.111.201.233 please and give me the results?
Thanks!
HiNet ping is:
ping 95.111.201.233
Ping wird ausgeführt für 95.111.201.233 mit 32 Bytes Daten:
Antwort von 95.111.201.233: Bytes=32 Zeit=82ms TTL=49
Antwort von 95.111.201.233: Bytes=32 Zeit=82ms TTL=49
Antwort von 95.111.201.233: Bytes=32 Zeit=82ms TTL=49
Antwort von 95.111.201.233: Bytes=32 Zeit=81ms TTL=49
Ping-Statistik für 95.111.201.233:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 81ms, Maximum = 82ms, Mittelwert = 81ms
AWS in Japan
Pinging 95.111.201.233 with 32 bytes of data:
Reply from 95.111.201.233: bytes=32 time=90ms TTL=51
Reply from 95.111.201.233: bytes=32 time=87ms TTL=51
Reply from 95.111.201.233: bytes=32 time=78ms TTL=51
Reply from 95.111.201.233: bytes=32 time=90ms TTL=51
Ping statistics for 95.111.201.233:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 90ms, Average = 86ms
Which provider do you have?
Pinged from AWS server in Japan
HiNet at home has similar ping
That IP is a server hosted in Singapore. So ping looks fine for that location.
1 Like
These days I’m having issues with my TWM home internet - mostly in the afternoon and at night.
What I noticed is that ipv6 traffic works much smoother than ipv4 traffic (pinging a server in Germany):
C:\Users\qwert>ping -4 www.strato.de
Pinging www.strato.de [192.67.198.33] with 32 bytes of data:
Reply from 192.67.198.33: bytes=32 time=359ms TTL=240
Reply from 192.67.198.33: bytes=32 time=358ms TTL=240
Reply from 192.67.198.33: bytes=32 time=360ms TTL=240
Request timed out.Ping statistics for 192.67.198.33:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 358ms, Maximum = 360ms, Average = 359msC:\Users\qwert>ping -6 www.strato.de
Pinging www.strato.de [2a01:238:20a:202:6660:0:198:33] with 32 bytes of data:
Reply from 2a01:238:20a:202:6660:0:198:33: time=249ms
Reply from 2a01:238:20a:202:6660:0:198:33: time=248ms
Reply from 2a01:238:20a:202:6660:0:198:33: time=246ms
Reply from 2a01:238:20a:202:6660:0:198:33: time=249msPing statistics for 2a01:238:20a:202:6660:0:198:33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 246ms, Maximum = 249ms, Average = 248ms
359ms average (and one lost package) vs. 248ms average…
When I use a mobile hotspot (4G), the difference disappears:
C:\Users\qwert>ping -4 www.strato.de
Pinging www.strato.de [192.67.198.33] with 32 bytes of data:
Reply from 192.67.198.33: bytes=32 time=278ms TTL=241
Reply from 192.67.198.33: bytes=32 time=285ms TTL=241
Reply from 192.67.198.33: bytes=32 time=273ms TTL=241
Reply from 192.67.198.33: bytes=32 time=293ms TTL=241Ping statistics for 192.67.198.33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 273ms, Maximum = 293ms, Average = 282msC:\Users\qwert>ping -6 www.strato.de
Pinging www.strato.de [2a01:238:20a:202:6660:0:198:33] with 32 bytes of data:
Reply from 2a01:238:20a:202:6660:0:198:33: time=284ms
Reply from 2a01:238:20a:202:6660:0:198:33: time=280ms
Reply from 2a01:238:20a:202:6660:0:198:33: time=289ms
Reply from 2a01:238:20a:202:6660:0:198:33: time=279msPing statistics for 2a01:238:20a:202:6660:0:198:33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 279ms, Maximum = 289ms, Average = 283ms
Not sure what’s going on here…
1 Like
This could explain a few things
Running the ping for a couple of minutes yields a really bad result (so many lost packages…) - but only for ipv4:
Ping statistics for 192.67.198.33:
Packets: Sent = 265, Received = 214, Lost = 51 (19% loss),
Approximate round trip times in milli-seconds:
Minimum = 345ms, Maximum = 514ms, Average = 361ms
vs. ipv6:
Ping statistics for 2a01:238:20a:202:6660:0:198:33:
Packets: Sent = 257, Received = 257, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 239ms, Maximum = 419ms, Average = 254ms
Unfortunately, my work VPN only supports ipv4… No wonder the connection felt so terrible these days…
ChatGPT to the help:
It helped me compare a tracert using ipv6 and ipv4 and found out the following:
Your IPv4 traffic is routed through Taiwan (TFN network) → Los Angeles → Frankfurt before reaching Strato.
The long route from Taiwan → LAX → Frankfurt causes high latency.
[…]
Your IPv6 traffic stays within Asia longer, then follows thetwelve99.net(Telia) backbone.
Hop 10 (San Jose, SJO) shows ~147ms latency, meaning it also crosses the Pacific, but likely via a better backbone.
The final latency (~244ms) is better than IPv4 (~350ms) but still high.
It then suggested trying out a VPN or Cloudflare WARP (I chose the latter one). And indeed, this improves the connection quality significantly:
Ping statistics for 192.67.198.33:
Packets: Sent = 49, Received = 49, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 268ms, Maximum = 309ms, Average = 273ms
Your connection now follows Telstra Global instead of the previous Los Angeles route.
The path still takes a detour through Hong Kong (hkth-core03.telstraglobal.net) → Singapore (sgcn-core01) → London (linx.bb-d.ba.slo.gb.oneandone.net) before reaching Germany.
Still, ipv4 over Cloudflare WARP is 275ms vs. ipv6 without VPN 200ms…
1 Like
It further suggested me to try connecting to VPN servers in different countries.
Interestingly, the results differ by quite a bit!
For my case - pinging a server in Germany: The best result seems to be connecting to a VPN server in Turkey… 
The ping (using ipv4) is around 214ms vs. 350ms when pinging that server directly… I honestly did not expect that using a VPN (in a different country!) would make such a huge difference…
Maybe something you can try, too, if you’re still experience those issues…
1 Like
Mine seems to be working fine now, thanks.