High latency problem

Technical Support
Prev 1 4 5 6 7 Next
30/05/2017 23:13Posted by Erratus
29/05/2017 21:06Posted by Rresto
well,i dont have time but ill share my details later. with openvpn i solved my problem. 65 world ms :) but 7 day free and 200mb :( ill edit later this post. if anyone solved prob with free vpn pls tell me :P


cant believe you sweeping problem under the carpet, after week what do you do? at least participate solving problem obviously blizzard needs a fix for this. they are slowing our ips somehow.

i just write quick solution for now. they say share your details, and we shared right? we explained the problem. i have same problem for 1 month. i didnt go last 2 week raid because of lag. if u have better idea tell me.
Here is a wild guess.
DPI or deep packet inspection may be the reason for bad latency.
People, who use VPN, can bypass DPI.

I see that complainants use WinMTR to see which node is to blame for bad latency. Is that node located in Turkey or not?

There is also another handy tool people may want to explore
http://eu-looking-glass.battle.net/
Same problem need help, ramdom huge lag spikes, cant play vp at all :(

PING:
PING 87.247.115.124 (87.247.115.124) 56(84) bytes of data.
64 bytes from 87.247.115.124: icmp_seq=1 ttl=54 time=33.2 ms
64 bytes from 87.247.115.124: icmp_seq=2 ttl=54 time=33.9 ms
64 bytes from 87.247.115.124: icmp_seq=3 ttl=54 time=33.0 ms
64 bytes from 87.247.115.124: icmp_seq=4 ttl=54 time=35.9 ms

--- 87.247.115.124 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3034ms
rtt min/avg/max/mdev = 33.025/34.037/35.986/1.182 ms

31/05/2017 12:38:17 UTC
--------------------

PING:
PING 87.247.115.124 (87.247.115.124) 56(84) bytes of data.
64 bytes from 87.247.115.124: icmp_seq=1 ttl=54 time=33.6 ms
64 bytes from 87.247.115.124: icmp_seq=2 ttl=54 time=33.3 ms
64 bytes from 87.247.115.124: icmp_seq=3 ttl=54 time=33.0 ms
64 bytes from 87.247.115.124: icmp_seq=4 ttl=54 time=33.2 ms

--- 87.247.115.124 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3035ms
rtt min/avg/max/mdev = 33.055/33.337/33.677/0.316 ms

31/05/2017 12:38:17 UTC
--------------------

TRACEROUTE:
traceroute to 87.247.115.124 (87.247.115.124), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.916 ms 0.925 ms 0.980 ms
2 * * *
3 37.244.9.100 (37.244.9.100) 0.951 ms 1.136 ms 1.262 ms
4 37.244.9.32 (37.244.9.32) 0.719 ms 0.759 ms 0.820 ms
5 retn.par.franceix.net (37.49.236.17) 0.970 ms 0.982 ms 0.997 ms
6 ae2-3.RT.RTC.KUN.LT.retn.net (87.245.232.86) 33.413 ms 33.376 ms 33.381 ms
7 GW-Cgates.retn.net (87.245.248.101) 33.465 ms 33.483 ms 33.537 ms
8 dmz-2-209.cgates.lt (5.20.2.209) 32.018 ms 32.133 ms 32.223 ms
9 looking-glass.mvisata.lt (217.17.85.181) 32.305 ms 32.344 ms 32.345 ms
10 cer15-g24-vl13.cgates.lt (217.17.85.145) 32.650 ms 32.496 ms 32.540 ms
11 data-84-60.cgates.lt (217.17.84.60) 32.084 ms 31.999 ms 32.065 ms
12 client-87-247-115-124.cgates.lt (87.247.115.124) 33.094 ms 33.159 ms 33.160 ms

31/05/2017 12:38:17 UTC
--------------------

TRACEROUTE:
traceroute to 87.247.115.124 (87.247.115.124), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.821 ms 0.872 ms 0.927 ms
2 * * *
3 37.244.9.100 (37.244.9.100) 0.759 ms 0.788 ms 0.839 ms
4 37.244.9.32 (37.244.9.32) 0.701 ms 0.766 ms 0.785 ms
5 retn.par.franceix.net (37.49.236.17) 0.972 ms 0.987 ms 1.000 ms
6 ae2-3.RT.RTC.KUN.LT.retn.net (87.245.232.86) 33.400 ms 33.391 ms 33.403 ms
7 GW-Cgates.retn.net (87.245.248.101) 33.510 ms 33.558 ms 33.620 ms
8 dmz-2-209.cgates.lt (5.20.2.209) 32.048 ms 32.132 ms 32.245 ms
9 looking-glass.mvisata.lt (217.17.85.181) 32.191 ms 32.231 ms 32.255 ms
10 cer15-g24-vl13.cgates.lt (217.17.85.145) 34.471 ms 33.891 ms 34.161 ms
11 data-84-60.cgates.lt (217.17.84.60) 32.149 ms 32.195 ms 32.219 ms
12 client-87-247-115-124.cgates.lt (87.247.115.124) 33.662 ms 33.180 ms 33.180 ms

31/05/2017 12:38:17 UTC
--------------------

TRACEROUTE:
traceroute to 87.247.115.124 (87.247.115.124), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.258 ms 0.326 ms 0.402 ms
2 * * *
3 37.244.10.102 (37.244.10.102) 0.959 ms 0.968 ms 1.021 ms
4 37.244.10.34 (37.244.10.34) 0.783 ms 0.816 ms 0.934 ms
5 ams-ix.retn.net (80.249.209.216) 1.069 ms 1.049 ms 1.066 ms
6 ae2-3.RT.RTC.KUN.LT.retn.net (87.245.232.86) 28.807 ms 28.825 ms 28.833 ms
7 GW-Cgates.retn.net (87.245.248.101) 28.923 ms 29.029 ms 28.876 ms
8 dmz-2-209.cgates.lt (5.20.2.209) 27.458 ms 27.569 ms 27.696 ms
9 looking-glass.mvisata.lt (217.17.85.181) 27.768 ms 27.666 ms 27.638 ms
10 cer15-g24-vl13.cgates.lt (217.17.85.145) 28.967 ms 30.176 ms 30.268 ms
11 data-84-60.cgates.lt (217.17.84.60) 27.578 ms 27.578 ms 27.577 ms
12 client-87-247-115-124.cgates.lt (87.247.115.124) 28.637 ms 28.477 ms 28.443 ms

31/05/2017 12:38:21 UTC
--------------------

PING:
PING 87.247.115.124 (87.247.115.124) 56(84) bytes of data.
64 bytes from 87.247.115.124: icmp_seq=1 ttl=54 time=30.3 ms
64 bytes from 87.247.115.124: icmp_seq=2 ttl=54 time=30.0 ms
64 bytes from 87.247.115.124: icmp_seq=3 ttl=54 time=28.4 ms
64 bytes from 87.247.115.124: icmp_seq=4 ttl=54 time=28.9 ms

--- 87.247.115.124 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3027ms
rtt min/avg/max/mdev = 28.470/29.429/30.316/0.773 ms

31/05/2017 12:38:21 UTC
--------------------

TRACEROUTE:
traceroute to 87.247.115.124 (87.247.115.124), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.504 ms 0.820 ms 0.851 ms
2 * * *
3 37.244.10.102 (37.244.10.102) 0.892 ms 0.904 ms 0.963 ms
4 37.244.10.34 (37.244.10.34) 0.785 ms 1.018 ms 1.126 ms
5 ams-ix.retn.net (80.249.209.216) 0.970 ms 0.991 ms 0.982 ms
6 ae2-3.RT.RTC.KUN.LT.retn.net (87.245.232.86) 28.746 ms 28.845 ms 28.842 ms
7 GW-Cgates.retn.net (87.245.248.101) 29.081 ms 29.004 ms 28.951 ms
8 dmz-2-209.cgates.lt (5.20.2.209) 28.162 ms 27.897 ms 28.036 ms
9 looking-glass.mvisata.lt (217.17.85.181) 27.766 ms 27.693 ms 27.706 ms
10 cer15-g24-vl13.cgates.lt (217.17.85.145) 28.289 ms 28.684 ms 28.805 ms
11 data-84-60.cgates.lt (217.17.84.60) 27.230 ms 27.272 ms 27.497 ms
12 client-87-247-115-124.cgates.lt (87.247.115.124) 28.419 ms 28.340 ms 28.452 ms

31/05/2017 12:38:24 UTC
--------------------

PING:
PING 87.247.115.124 (87.247.115.124) 56(84) bytes of data.
64 bytes from 87.247.115.124: icmp_seq=1 ttl=54 time=29.5 ms
64 bytes from 87.247.115.124: icmp_seq=2 ttl=54 time=28.7 ms
64 bytes from 87.247.115.124: icmp_seq=3 ttl=54 time=28.5 ms
64 bytes from 87.247.115.124: icmp_seq=4 ttl=54 time=28.8 ms

--- 87.247.115.124 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3031ms
rtt min/avg/max/mdev = 28.515/28.912/29.553/0.425 ms

31/05/2017 12:38:24 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.7 0.6 0.5 0.7 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.9.100 0.0% 10 0.7 0.9 0.7 2.0 0.4
4. 37.244.9.32 0.0% 10 0.6 0.8 0.6 2.0 0.4
5. retn.par.franceix.net 0.0% 10 1.0 1.3 1.0 4.0 0.9
6. ae2-3.RT.RTC.KUN.LT.retn.net 0.0% 10 33.9 33.5 33.4 33.9 0.1
7. GW-Cgates.retn.net 0.0% 10 33.5 33.9 33.5 36.5 0.9
8. dmz-2-209.cgates.lt 0.0% 10 32.1 38.2 32.1 89.9 18.2
9. looking-glass.mvisata.lt 0.0% 10 32.2 33.0 32.1 40.4 2.6
10. cer15-g24-vl13.cgates.lt 0.0% 10 35.7 34.7 33.2 40.8 2.3
11. data-84-60.cgates.lt 0.0% 10 32.1 32.1 32.1 32.1 0.0
12. client-87-247-115-124.cgates.lt 0.0% 10 33.1 33.5 33.0 34.1 0.4

31/05/2017 12:38:17 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.8 0.6 0.4 0.8 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.9.100 0.0% 10 0.6 0.7 0.6 1.1 0.1
4. 37.244.9.32 0.0% 10 0.8 0.8 0.7 0.9 0.1
5. retn.par.franceix.net 0.0% 10 1.8 2.1 1.3 3.2 0.8
6. ae2-3.RT.RTC.KUN.LT.retn.net 0.0% 10 33.4 33.5 33.4 33.6 0.1
7. GW-Cgates.retn.net 0.0% 10 33.9 33.8 33.5 35.9 0.7
8. dmz-2-209.cgates.lt 0.0% 10 32.2 41.5 32.0 92.8 20.1
9. looking-glass.mvisata.lt 0.0% 10 32.1 33.0 32.1 40.3 2.6
10. cer15-g24-vl13.cgates.lt 0.0% 10 33.9 46.8 32.3 167.0 42.2
11. data-84-60.cgates.lt 0.0% 10 32.2 32.1 32.0 32.3 0.1
12. client-87-247-115-124.cgates.lt 0.0% 10 33.8 34.1 33.0 38.5 1.7

31/05/2017 12:38:17 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 1.0 0.4 0.3 1.0 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.10.102 0.0% 10 0.7 0.9 0.7 1.1 0.1
4. 37.244.10.34 0.0% 10 0.8 0.9 0.8 1.0 0.1
5. ams-ix.retn.net 0.0% 10 1.1 1.1 0.9 1.7 0.2
6. ae2-3.RT.RTC.KUN.LT.retn.net 0.0% 10 28.9 33.2 28.8 67.7 12.2
7. GW-Cgates.retn.net 0.0% 10 29.2 31.0 28.8 40.2 4.4
8. dmz-2-209.cgates.lt 0.0% 10 27.4 28.2 27.3 35.1 2.4
9. looking-glass.mvisata.lt 0.0% 10 97.8 34.9 27.4 97.8 22.1
10. cer15-g24-vl13.cgates.lt 0.0% 10 102.0 36.1 27.7 102.0 23.2
11. data-84-60.cgates.lt 0.0% 10 27.6 27.7 27.4 29.3 0.6
12. client-87-247-115-124.cgates.lt 0.0% 10 29.6 30.0 28.7 35.6 2.1

31/05/2017 12:38:21 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.3 0.5 0.3 0.9 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.10.102 0.0% 10 0.9 0.9 0.7 1.0 0.1
4. 37.244.10.34 0.0% 10 0.8 0.9 0.8 1.1 0.1
5. ams-ix.retn.net 0.0% 10 0.9 2.9 0.8 12.3 4.0
6. ae2-3.RT.RTC.KUN.LT.retn.net 0.0% 10 28.8 29.1 28.7 31.7 0.9
7. GW-Cgates.retn.net 0.0% 10 28.8 29.4 28.8 33.1 1.3
8. dmz-2-209.cgates.lt 0.0% 10 67.5 38.8 27.4 100.9 25.2
9. looking-glass.mvisata.lt 0.0% 10 29.4 28.6 27.6 32.1 1.4
10. cer15-g24-vl13.cgates.lt 0.0% 10 34.0 29.8 27.8 34.0 1.9
11. data-84-60.cgates.lt 0.0% 10 29.4 27.7 27.3 29.4 0.6
12. client-87-247-115-124.cgates.lt 0.0% 10 29.0 29.1 28.4 33.1 1.4

31/05/2017 12:38:21 UTC
--------------------
31/05/2017 09:32Posted by Tiogaradh
Thanks to those of you that provided the info I requested, i have passed this on now so hopefully we can get an update for you all soon.

_____________________________________________________
Na na na na na na na na na na na na na na na na Survey!
https://www.surveymonkey.com/s/Tiogaradh


well thank you. also interacting with isp.
31/05/2017 17:16Posted by Erratus
31/05/2017 09:32Posted by Tiogaradh
Thanks to those of you that provided the info I requested, i have passed this on now so hopefully we can get an update for you all soon.

_____________________________________________________
Na na na na na na na na na na na na na na na na Survey!
https://www.surveymonkey.com/s/Tiogaradh


well thank you. also interacting with isp.


i hope it gets fixed im still having issues :(
I am in the same situatiuon - just lag spikes all the time. Sometimes the ingame latency shows 39ms and i am still geting 3-4 secs of spikes. After some time the game detects that there is something wrong with latency and changes to 200-300 , sometimes more. Using VPN didn't solve anything for me - game shows 62 ms and still the same spikes going over and over.
Location - Bulgaria, Burgas - around 400 km from Instanbul so might be some area related problem.
Today the problems started around 11 pm ( ofc during raid ) and keep going 1 hour later.
All of this started at Saturday evening, so so far its 5 days for me without being able to play properly - especially at evenings.
I have the same problem and I'm using the same isp as others (uydunet).I hope our problem will be fixed any time soon.Thank you!
Computer Engineer here:
I do have the same ISP, uydunet, same lag spikes all around...
Just got back to woe after 6 months.... it was around 50 ms 6 months ago.
now its 300 in good times and 900ms in bad times and sometimes disconnects as well.
blizzard needs to speak with those server owners in those hops and find out why the packets do not reach to their servers that are coming from uydunet.

i do other stuff on the net, i have no issues with it but wow is soooo laggy!

blizzard needs to fix this.
Ok here is possible issue and fix:
im having this issue since 4 months and using VPNs.Uydunet started to use CNG pool for our ips since 4 months.i called and asked thats why im sure.This means we are using shared ips and they make massive lag in online games.i found this resource:

https://forum.donanimhaber.com/kablonet-cgn-havuzundan-cikmak--126380237-2

it is turkish ofc.i just called them and asked to change my ip.if you are using 100.xxx.xx ip on ur modem you are most probably in CNG pool.Mine will be changed today i guess.i will write result here.
02/06/2017 06:01Posted by Gíø
Ok here is possible issue and fix:
im having this issue since 4 months and using VPNs.Uydunet started to use CNG pool for our ips since 4 months.i called and asked thats why im sure.This means we are using shared ips and they make massive lag in online games.i found this resource:

https://forum.donanimhaber.com/kablonet-cgn-havuzundan-cikmak--126380237-2

it is turkish ofc.i just called them and asked to change my ip.if you are using 100.xxx.xx ip on ur modem you are most probably in CNG pool.Mine will be changed today i guess.i will write result here.


mine starts with 94.55.***
lag started 17 pm again. 200-500ms
i have tried to change my ip adress they changed twice no improvements.
with vpn from some other country mask wow works fine but vpn is not stable and dont wanna pay for it aswell.
02/06/2017 15:27Posted by Erratus
02/06/2017 06:01Posted by Gíø
Ok here is possible issue and fix:
im having this issue since 4 months and using VPNs.Uydunet started to use CNG pool for our ips since 4 months.i called and asked thats why im sure.This means we are using shared ips and they make massive lag in online games.i found this resource:

https://forum.donanimhaber.com/kablonet-cgn-havuzundan-cikmak--126380237-2

it is turkish ofc.i just called them and asked to change my ip.if you are using 100.xxx.xx ip on ur modem you are most probably in CNG pool.Mine will be changed today i guess.i will write result here.


mine starts with 94.55.***
lag started 17 pm again. 200-500ms
i have tried to change my ip adress they changed twice no improvements.
with vpn from some other country mask wow works fine but vpn is not stable and dont wanna pay for it aswell.

Read the link and ask them to change ur CGN block.
(modem ip si ile whatsmyip com dan iplerine baktır üstat.uyuşmuyorsa sende havuzdasın)
02/06/2017 17:41Posted by Gíø
02/06/2017 15:27Posted by Erratus
...

mine starts with 94.55.***
lag started 17 pm again. 200-500ms
i have tried to change my ip adress they changed twice no improvements.
with vpn from some other country mask wow works fine but vpn is not stable and dont wanna pay for it aswell.

Read the link and ask them to change ur CGN block.
(modem ip si ile whatsmyip com dan iplerine baktır üstat.uyuşmuyorsa sende havuzdasın)


talked to isp also mailed waiting to get them on action.
beyler nasıl çözülcek bu olay kaç hafta geçti biz hala yazıyoruz bakan ilgilenen yok bu kadar zor mu bunu çözümlemek
any updates? tonight its 100 ms , which is normal at the moment. gonna let you inform how it goes. i hope its solved.

*** nope its not working just died to latency its more than 200.
Details of issue : low home ms and high world ms.

When does the issue occur: Mostly after 20:00 - 24:00

City and country : Antalya - TURKEY
ISP : Turkcell Superonline
Connection type : wired Fiber 100mb/5mb

EU Twisting Nether

Tracing route to 80-239-149-96.customer.teliacarrier.com [80.239.149.96]
over a maximum of 30 hops:

1 - 1 ms <1 ms <1 ms
2 - 1 ms <1 ms * host-92-45-0-35.reverse.superonline.net [92.45.0.35]
3 - 2 ms 1 ms * 10.36.7.109
4 - 20 ms 19 ms * 10.34.255.217
5 - 20 ms 20 ms * 10.34.255.222
6 - 21 ms 21 ms * 10.40.132.78
7 - 21 ms 21 ms * 10.36.6.37
8 - 21 ms 21 ms * 10.38.218.182
9 - 72 ms 56 ms 56 ms ix-ae-11-0.tcore1.IT5-Istanbul.as6453.net [5.23.0.41]
10 - 104 ms 104 ms 105 ms if-ae-8-2.tcore1.FNM-Frankfurt.as6453.net [195.219.156.21]
11 - 62 ms 61 ms 83 ms if-ae-12-2.tcore2.FNM-Frankfurt.as6453.net [195.219.87.1]
12 - 114 ms 103 ms 103 ms ffm-b1-link.telia.net [213.248.82.40]
13 - 107 ms 110 ms 115 ms ffm-bb4-link.telia.net [62.115.116.159]
14 - 125 ms 123 ms 121 ms war-b2-link.telia.net [80.91.250.104]
15 - 75 ms 75 ms 75 ms 80-239-149-96.customer.teliacarrier.com [80.239.149.96]

C:\WINDOWS\system32>tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 - <1 ms <1 ms <1 ms
2 - 1 ms <1 ms * host-92-45-0-35.reverse.superonline.net [92.45.0.35]
3 - 3 ms 1 ms * 10.36.7.109
4 - 20 ms 19 ms * 10.34.255.217
5 - 21 ms 20 ms * 10.34.255.222
6 - 22 ms 21 ms * 10.40.132.78
7 - 22 ms 21 ms * 10.36.6.37
8 - 22 ms 21 ms * 10.38.218.170
9 - 55 ms 56 ms 56 ms ix-ae-11-0.tcore1.IT5-Istanbul.as6453.net [5.23.0.41]
10 - 119 ms 121 ms 121 ms if-ae-8-2.tcore1.FNM-Frankfurt.as6453.net [195.219.156.21]
11 - 75 ms 75 ms 75 ms if-ae-12-2.tcore2.FNM-Frankfurt.as6453.net [195.219.87.1]
12 - 124 ms 121 ms 121 ms if-ae-9-2.tcore1.PVU-Paris.as6453.net [195.219.87.14]
13 - 71 ms 72 ms 71 ms 80.231.153.66
14 - * * * Request timed out.
15 - 129 ms 130 ms 132 ms BLIZZARD-EN.ear2.Paris1.Level3.net [212.73.205.158]
16 - 81 ms 80 ms 80 ms 37.244.9.35
17 - * * * Request timed out.
18 - 82 ms 82 ms 82 ms 37.244.10.103
19 - 125 ms * 122 ms 185.60.114.151
20 - 79 ms 79 ms 79 ms 185.60.112.157
C:\WINDOWS\system32>pathping 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

0 DESKTOP-83TNNTK.home []
1
2 - host-92-45-0-35.reverse.superonline.net [92.45.0.35]
3 - 10.36.7.109
4 - 10.34.255.217
5 - 10.34.255.222
6 - * 10.40.132.78
7 - 10.36.6.37
8 - 10.38.218.170
9 - * ix-ae-11-0.tcore1.IT5-Istanbul.as6453.net [5.23.0.41]
10 - if-ae-8-2.tcore1.FNM-Frankfurt.as6453.net [195.219.156.21]
11 - if-ae-12-2.tcore2.FNM-Frankfurt.as6453.net [195.219.87.1]
12 - if-ae-9-2.tcore1.PVU-Paris.as6453.net [195.219.87.14]
13 - * 80.231.153.66
14 - * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-83TNNTK.home [192.168.1.31]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% host-92-45-0-35.reverse.superonline.net [92.45.0.35]
0/ 100 = 0% |
3 1ms 0/ 100 = 0% 0/ 100 = 0% 10.36.7.109
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 10.34.255.217
0/ 100 = 0% |
5 21ms 0/ 100 = 0% 0/ 100 = 0% 10.34.255.222
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 10.40.132.78
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 10.36.6.37
0/ 100 = 0% |
8 19ms 0/ 100 = 0% 0/ 100 = 0% 10.38.218.170
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% ix-ae-11-0.tcore1.IT5-Istanbul.as6453.net [5.23.0.41]
0/ 100 = 0% |
10 107ms 1/ 100 = 1% 1/ 100 = 1% if-ae-8-2.tcore1.FNM-Frankfurt.as6453.net [195.219.156.21]
0/ 100 = 0% |
11 60ms 3/ 100 = 3% 3/ 100 = 3% if-ae-12-2.tcore2.FNM-Frankfurt.as6453.net [195.219.87.1]
0/ 100 = 0% |
12 117ms 2/ 100 = 2% 2/ 100 = 2% if-ae-9-2.tcore1.PVU-Paris.as6453.net [195.219.87.14]
0/ 100 = 0% |
13 68ms 0/ 100 = 0% 0/ 100 = 0% 80.231.153.66

ms high on diablo III too. I have never seen more then 80ms for years.

http://www.speedtest.net/my-result/6354010443
well isp is not helping at all. blizzard we need to fix this with you i think. they say cgn information classified we cant share it with you.
wow is the only game I play and after this terrible home-world ms issue I installed CS:GO and joined a comp game. My ping was 62 ( stable ) I don't blame my ISP after this result tbh. I think its you dear blizzard.

uptade: playing wow atm
location: broken shore 92 ms and keeps increasing. Hello blizzard you there?
Same here , dealing with spikes and lag last few days.
ignore us more blizzard?

Join the Conversation

Return to Forum