Menu
Reply
  • 9
  • 0
  • 0
sekmet64
Joining in
251 Views
Message 1 of 7
Flag for a moderator

high ping Sunday evening

Hi I have unplayable ping and lag when playing on blizzard servers.

Please look into it:

 

C:\Users\Csongor>tracert eu.battle.net

Tracing route to eu.battle.net [80.239.186.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms routerlogin.net [192.168.0.1]
2 17 ms 15 ms 19 ms 10.240.96.1
3 137 ms 70 ms 24 ms bmly-core-2a-xe-030-0.network.virginmedia.net [2
13.105.193.61]
4 * * * Request timed out.
5 178 ms 370 ms 338 ms popl-bb-1c-ae0-0.network.virginmedia.net [62.254
.42.94]
6 209 ms 192 ms 165 ms xe-1-0-0-xcr1.lsw.cw.net [166.63.211.129]
7 443 ms 384 ms 316 ms ae17-xcr1.lnd.cw.net [195.2.25.166]
8 290 ms 281 ms 275 ms ae2-xcr1.hex.cw.net [195.2.24.158]
9 365 ms 428 ms 384 ms ldn-b3-link.telia.net [62.115.41.109]
10 305 ms 281 ms 233 ms ldn-bb2-link.telia.net [213.155.133.32]
11 174 ms 231 ms 243 ms prs-bb2-link.telia.net [80.91.247.240]
12 334 ms 190 ms 299 ms prs-b8-link.telia.net [213.155.136.209]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

 

Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
0 csongorpal-pc [192.168.0.12]
1 routerlogin.net [192.168.0.1]
2 10.240.96.1
3 bmly-core-2b-xe-030-0.network.virginmedia.net [213.105.193.113]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 csongorpal-pc [192.168.0.12]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% routerlogin.net [192.168.0.1]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.240.96.1
0/ 100 = 0% |
3 159ms 0/ 100 = 0% 0/ 100 = 0% bmly-core-2b-xe-030-0.network.virginmedia.net [213.105.193.113]

Trace complete.

 

 

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

--- 82.12.255.36 ping statistics ---

traceroute to 82.12.255.36 (82.12.255.36), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.484 ms !X * *

traceroute to 82.12.255.36 (82.12.255.36), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.376 ms  0.389 ms  0.513 ms
 2  * * *
 3  80.249.209.253 (80.249.209.253)  0.932 ms  0.962 ms  0.967 ms
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  bmly-core-2b-ae8-0.network.virginmedia.net (62.254.42.86)  26.743 ms  26.780 ms  26.782 ms
10  slam-cmts-06-tenge330.network.virginmedia.net (213.105.193.114)  26.021 ms  26.052 ms  26.050 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *

HOST: Blizzard                 Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                              0.0%    10    0.4   0.4   0.3   0.5   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.7   0.8   0.6   0.9   0.1
  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. ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
  7. ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0

 

0 Kudos
  • 14.34K
  • 640
  • 1.44K
Moderator
Moderator
219 Views
Message 2 of 7
Flag for a moderator

Re: high ping Sunday evening

Hi Sekmet64,

 

Welcome to the forum and sorry to hear you're getting poor speeds to WoW. Thank you for providing the traces and other data, looking at it there is certainly a problem on the 3rd hop onwards. This is down to a contention issue which has been raised under ticket F003444101 which is due for review 26/08/15. This should only affect you in peak times so could you run another trace around midday and post it here?


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


0 Kudos
  • 9
  • 0
  • 0
sekmet64
Joining in
191 Views
Message 3 of 7
Flag for a moderator

Re: high ping Sunday evening

Hi, 

 

Thanks, and I hope this will get looked at soon. It sometimes happens on weekday evenings too and that's pretty much all the times I would need it to work well Smiley Sad

 

The results below are from Sunday 11pm when things got back to normal.

 

Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms routerlogin.net [192.168.0.1]
2 9 ms 8 ms 8 ms 10.240.96.1
3 8 ms 7 ms 7 ms bmly-core-2b-xe-030-0.network.virginmedia.net [2
13.105.193.113]
4 * * * Request timed out.
5 * * * Request timed out.
6 21 ms 17 ms 14 ms brhm-bb-1c-ae1-0.network.virginmedia.net [62.254
.42.210]
7 27 ms 28 ms 54 ms 213.161.65.149
8 31 ms 37 ms 20 ms ldn-b5-link.telia.net [213.248.76.85]
9 23 ms 23 ms 21 ms ldn-bb3-link.telia.net [213.155.132.194]
10 25 ms 26 ms 29 ms adm-bb3-link.telia.net [62.115.143.189]
11 27 ms 28 ms 27 ms adm-b2-link.telia.net [62.115.141.57]
12 * * * Request timed out.
13 * * * Request timed out.

 

 

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

traceroute to 82.12.255.36 (82.12.255.36), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.496 ms !X * *

traceroute to 82.12.255.36 (82.12.255.36), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.322 ms  0.385 ms  0.451 ms
 2  * * *
 3  80.249.209.253 (80.249.209.253)  0.578 ms  0.591 ms  0.601 ms
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  bmly-core-2b-ae8-0.network.virginmedia.net (62.254.42.86)  26.974 ms  26.982 ms  26.985 ms
10  slam-cmts-06-tenge330.network.virginmedia.net (213.105.193.114)  26.845 ms  26.883 ms  26.883 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *

HOST: Blizzard                 Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                              0.0%    10    0.9   0.5   0.3   0.9   0.2
  2. ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 80.249.209.253                              0.0%    10    0.6   0.7   0.6   0.8   0.1
  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. ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
  7. ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
  8. ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
  9. bmly-core-2b-ae8-0.network.virginmedia.net  0.0%    10   26.9  29.4  26.9  48.3   6.7

 

0 Kudos
  • 14.34K
  • 640
  • 1.44K
Moderator
Moderator
173 Views
Message 4 of 7
Flag for a moderator

Re: high ping Sunday evening

Thank you for posting the new traces Sekmet64,

 

As they all look fine then this problem will be solely down to the fault reference I posted previously. We'll have to wait until the review date of 26/08/15 to see how the work to increase capacity has gone. 


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


0 Kudos
  • 9
  • 0
  • 0
sekmet64
Joining in
165 Views
Message 5 of 7
Flag for a moderator

Re: high ping Sunday evening

This is every single evening. Waiting for more than an entire month seems absurd for me to get this fixed Smiley Sad

 

I should have a 100 Mbps connection, and this is what I get, it was a Wednesday evening 9:30pm: 

 

 

 

5Mbps instead of 100. 

 

Ping to google:

Pinging google.com [62.252.169.152] with 32 bytes of data&colon;
Reply from 62.252.169.152: bytes=32 time=257ms TTL=58
Reply from 62.252.169.152: bytes=32 time=286ms TTL=58
Reply from 62.252.169.152: bytes=32 time=283ms TTL=58

 

Tracert to battle.net:

Tracing route to eu.battle.net [80.239.186.40]
over a maximum of 30 hops:

1 <1 ms <1 ms 17 ms routerlogin.net [192.168.0.1]
2 129 ms 169 ms 178 ms 10.240.96.1
3 230 ms 270 ms 225 ms bmly-core-2a-xe-030-0.network.virginmedia.net [
13.105.193.61]
4 * * * Request timed out.
5 195 ms * 263 ms popl-bb-1c-ae0-0.network.virginmedia.net [62.25
.42.94]
6 227 ms 317 ms * xe-1-0-0-xcr1.lsw.cw.net [166.63.211.129]
7 247 ms 180 ms 148 ms ae2-xcr1.lnt.cw.net [195.2.30.54]
8 248 ms 202 ms 197 ms ae3-xcr1.hex.cw.net [195.2.24.162]
9 217 ms 281 ms 166 ms ldn-b3-link.telia.net [62.115.41.109]
10 129 ms 166 ms 194 ms ldn-bb2-link.telia.net [213.155.133.32]
11 109 ms 191 ms 198 ms prs-bb2-link.telia.net [80.91.246.177]
12 178 ms 235 ms 191 ms prs-b8-link.telia.net [213.155.131.19]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

 

It's not even the 100+ latency that's that bad, it's actually loosing packets and sometimes having laaarge lag spikes that last for a second. Very annoying and basically unplayable in any game. I wouldn't mind not going as blazing fast as during off-peak but seriously this is terrible. It's even annoying if I were just using it for browsing websites, a typical webpage takes long seconds 10+ to load in the evening.

0 Kudos
  • 9
  • 0
  • 0
sekmet64
Joining in
144 Views
Message 6 of 7
Flag for a moderator

Re: high ping Sunday evening

When is this going to be fixed???

Monday 10PM: 

600MS lag in games

 

Tracing route to google.com [62.252.169.168]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 312 ms 279 ms 282 ms 10.240.96.1
3 19 ms 18 ms 13 ms bmly-core-2a-xe-030-0.network.virginmedia.net [213.105.193.61]
4 * * * Request timed out.
5 * * * Request timed out.
6 383 ms 483 ms 329 ms basl-icdn-1-ae0-0.network.virginmedia.net [62.253.174.238]
7 389 ms 347 ms 294 ms m424-mp1-cvx1b.lan.ntl.com [62.252.169.168]

 

0 Kudos
  • 4.2K
  • 88
  • 271
Moderator
Moderator
126 Views
Message 7 of 7
Flag for a moderator

Re: high ping Sunday evening

Hi sekmet64

 

Thanks for getting back to us. I'm sorry to hear of the slow speeds you are experiencing around peak times.

 

I've had a check on ticket F003444101. There aren't any updates available at the moment. If you are able to bump the thread a little closer to the review date of 26/08/2015 we can certainly check for more information. 

 

Apologies for any inconvenience caused while we work to resolve this fault.

 


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


0 Kudos