Forum Discussion

MadiraNofo's avatar
MadiraNofo
On our wavelength
2 months ago

Help with packet loss on Virgin's aorta.net

Hi

been getting real issues with packet loss/ ping when playing World of Tanks. It's consistently poor, whether I play on wifi, or am wired into the router directly or on a Poweline extender. The issue seems to be these two hops:

nl-ams17b-rc1-ae-14-0.aorta.net
cz-prg02a-ra2-ae-99-45.aorta.net

Packet loss is currently 78% for nl- and 86.4% for cz- . It's been this way for a long time and makes the game hard to play. The game server I'm communicating with is: login.p1.worldoftanks.eu

Does support read these forums, and how do I go about getting this at least looked at?

Many thanks 🙂

  • asim18's avatar
    asim18
    Rising star
    2 months ago
    MadiraNofo wrote:

    Packet loss is currently 78% for nl- and 86.4% for cz- .🙂

    How are you measuring packet loss to these routers?

    As these are routers, if you're using ping, they may not be accurate as the router itself is having to respond to your ping rather than simply forwarding the ping packet to the destination server. If the routers are dropping your ping packets it doesn't really mean much, but if the destination server itself is dropping packets then it's meaningful.

    What is the ping to the destination server? what are the results if you ping the destination server. Try the following command which will ping it 30 times:

    ping -n 30 login.p1.worldoftanks.eu  

    Ping statistics for 185.12.240.54:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 26ms, Average = 17ms

     

  • MadiraNofo's avatar
    MadiraNofo
    On our wavelength
    2 months ago

    Hi asim

    Thanks for the reply. I was using PingPlotter (apologies for not mentioning that). I used your ping command:

    C:\Users\xxxx>ping -n 30 login.p1.worldoftanks.eu

    Pinging woteu1.login.wargaming.net [185.12.240.53] with 32 bytes of data:
    Reply from 185.12.240.53: bytes=32 time=43ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=73ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=70ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=98ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=21ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=21ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=48ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=33ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=47ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=25ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=1431ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=28ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=29ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=26ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=21ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=21ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=26ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=30ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=24ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=25ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=22ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=31ms TTL=49
    Reply from 185.12.240.53: bytes=32 time=55ms TTL=49

    Ping statistics for 185.12.240.53:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 1431ms, Average = 80ms

    This is in-line with my experience, it's fine, then there's a spike (highlighted in bold above).

    • Steven_L's avatar
      Steven_L
      Forum Team
      2 months ago

      Hey MadiraNofo,

      Welcome to the community and thanks for taking the time to post here on the forums. I’m sorry to hear of the issues that you’re having with your connection. I have looked into this and cannot see any issues with your connection or in your local area. Are you still experiencing issues since you last posted? If you're still experiencing issues, please can you setup a BQM using the link here and this will help us to diagnose the issues that you're having.

      Kind Regards,

      Steven_L

      • MadiraNofo's avatar
        MadiraNofo
        On our wavelength
        17 days ago

        Hi Steven

        Sorry for the delay, I have created a BQM now. What do you need from me to view it?

        Thanks

        Joe.

    • DEsaian's avatar
      DEsaian
      Joining in
      2 days ago

      Hi Madira! I have the same issue with WoT and packets missing. Did you manage to solve the issue?

      • MadiraNofo's avatar
        MadiraNofo
        On our wavelength
        2 days ago

        Hey. Not solved but identified. I was always using wifi when I had the issues I described. However, when I plugged my laptop directly into the SuperHub, everything was peachy. Turns out WiFi was the issue. So, I'll be buying a decent wifi router and using the SuperHub in modem mode- just haven't got to it yet

  • Client62's avatar
    Client62
    Alessandro Volta
    2 days ago

    nl-ams17b-rc1-ae-14-0.aorta.net
    cz-prg02a-ra2-ae-99-45.aorta.net

    Neither host name has a DNS entry.
    What am I missing ?

  • Adduxi's avatar
    Adduxi
    Very Insightful Person
    24 hours ago

    Most, if not all gaming is improved over a cabled connection .....