Menu
Reply
  • 53
  • 0
  • 3
majikthiseuk
Tuning in
177 Views
Message 1 of 5
Flag for a moderator

Still shocking ping, lost hops and general routing

It's starting to get beyond a joke now have repeatedly reported the same network problems for months and still no fix. Here is an example for WoW

Tracing route to 80-239-233-112.customer.teliacarrier.com [80.239.233.112]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    14 ms    10 ms    12 ms  midd-core2bxe123-0.network.virginmedia.net [62.252.68.157]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    84 ms    81 ms    81 ms  nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
  8    87 ms    87 ms    84 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.

And back the other way

Tracing route to 80-239-233-112.customer.teliacarrier.com [80.239.233.112] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    14 ms    10 ms    12 ms  midd-core-2b-xe-123-0.network.virginmedia.net [62.252.68.157]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    49 ms    31 ms    48 ms  nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
  8    67 ms   67 ms    64 ms  m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
0 Kudos
  • 14.34K
  • 640
  • 1.44K
Moderator
Moderator
142 Views
Message 2 of 5
Flag for a moderator

Re: Still shocking ping, lost hops and general routing

Hi Majikthiseuk,

 

That's a very strange traceroute. Barely any of the hops are responding to pings. Are these the full traceroutes? I'm assuming they just continue with Request timed out after hop 13? 

I know Wow has a looking glass tool that might help bypass some of the servers that ignore ping requests, it would be worth giving that a try and posting the results here for us to take a look at.


The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
  • 53
  • 0
  • 3
majikthiseuk
Tuning in
128 Views
Message 3 of 5
Flag for a moderator

Re: Still shocking ping, lost hops and general routing

Yes that is the case however loosing hops and massive increase in pings between nodes within Virgins network has been going on for months.

As for Looking-Glass it starts internally passes through the first network node after the main server then on to Telia, this shows the hops inside Blizzards network since external traces end at Blizzards first node to prevent attacks. I must have missed that from the post but it's still the same, reaches Virgins network then fails to respond multiple nodes and increased pings within two hops.

It has literally been months since I can get a straight trace to anything via Virgin since there are always lost hops inside their network and they are always after midd-core from my location, I'm not alone in this when testing this on other peoples computers it always gives the same results even people in other parts of the country there appears to be some serious issues on Virgins network

Though as I say Virgins default position is blame the user even when presented with facts that present otherwise. You can even see that from other posts on the forum this issue is persistent and all over the network

Looking Glass

traceroute to 82.17.41.17 (82.17.41.17), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.376 ms  0.426 ms  0.678 ms
 2  * * *
 3  80.249.209.253 (80.249.209.253)  0.640 ms  0.652 ms  0.653 ms
 4  * * *
 5  * * *
 6  midd-core-2b-ae2-0.network.virginmedia.net (62.254.84.138)  28.604 ms  28.651 ms  28.627 ms
 7  * * *
 8  cpc89688-darl9-2-0-cust272.11-2.cable.virginm.net (82.17.41.17)  68.535 ms  69.846 ms  85.151 ms

PING 82.17.41.17 (82.17.41.17) 56(84) bytes of data.
64 bytes from 82.17.41.17: icmp_seq=1 ttl=57 time=71.1 ms
64 bytes from 82.17.41.17: icmp_seq=2 ttl=57 time=69.6 ms
64 bytes from 82.17.41.17: icmp_seq=3 ttl=57 time=68.7 ms
64 bytes from 82.17.41.17: icmp_seq=4 ttl=57 time=80.6 ms

--- 82.17.41.17 ping statistics ---

HOST: Blizzard                        Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                                     0.0%    10    0.3   0.4   0.3   0.7   0.1
  2. ???                                               100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 80.249.209.253                                     0.0%    10    0.6   1.5   0.6   9.0   2.6
  4. ???                                               100.0    10    0.0   0.0   0.0   0.0   0.0
  5. ???                                               100.0    10    0.0   0.0   0.0   0.0   0.0
  6. midd-core-2b-ae2-0.network.virginmedia.net         0.0%    10   32.6  31.7  28.6  28.7   0.0

 

0 Kudos
  • 12.92K
  • 366
  • 1.04K
Moderator
Moderator
72 Views
Message 4 of 5
Flag for a moderator

Re: Still shocking ping, lost hops and general routing

Hi majikthiseuk,

 

Thanks for the additional information, though not sure if there's any real problem with the routing as it's fairly common for ICMP traffic to be ignored when running trace route checks and hence all the timed out responses.

 

If I ping Blizzard directly from your default gateway, the response times are excellent with no drops, even when sending large size packets

 

Sending IP ping to: 82.17.41.17 from 82.17.**.*
ping (82.17.41.17): 1500 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
50 packets transmitted, 50 packets received
 
I can see that your Superhub is in modem mode, is it connected directly to your PC or gaming console? 
 
What are your connection speeds like in general? Are other or all games affected by lag problems? Do similar problems occur on more than one device?
 
Hopefully we can puzzle out where the problem is.
 
Rgds
 
Ralph_R
Forum Moderator

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
  • 9.73K
  • 313
  • 838
legacy1
Hero
70 Views
Message 5 of 5
Flag for a moderator

Re: Still shocking ping, lost hops and general routing


majikthiseuk wrote:
traceroute to 82.17.41.17 (82.17.41.17), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.376 ms  0.426 ms  0.678 ms
 2  * * *
 3  80.249.209.253 (80.249.209.253)  0.640 ms  0.652 ms  0.653 ms
 4  * * *
 5  * * *
 6  midd-core-2b-ae2-0.network.virginmedia.net (62.254.84.138)  28.604 ms  28.651 ms  28.627 ms 7  * * *
 8  cpc89688-darl9-2-0-cust272.11-2.cable.virginm.net (82.17.41.17)  68.535 ms  69.846 ms  85.151 ms

 


Unless you do ping -n 200 to your IP from Blizzard its not packet loss but more about latency from 62.254.84.138 VM network under 30ms to you at say 75ms to which you ask the question why is their that much of a delay at best from Blizzard to you should be 40ms maybe.

 


majikthiseuk wrote:

As for Looking-Glass it starts internally passes through the first network node after the main server then on to Telia, this shows the hops inside Blizzards network since external traces end at Blizzards first node to prevent attacks. I must have missed that from the post but it's still the same, reaches Virgins network then fails to respond multiple nodes and increased pings within two hops.

 


But what if VM do the same to prevent attacks in the network on their routers say?

 

0 Kudos