The issue seems to be when traffic is routed from 137.221.86.x through 137.221.65.x
Im having no issues when its through 137.221.66 fx
The issue seems to be when traffic is routed from 137.221.86.x through 137.221.65.x
Im having no issues when its through 137.221.66 fx
As a dane i got the same problem, and itâs not only WoW. FeelsBadMan
Can confirm VPN worked for me connected to sweden
plx fix - is bad
Thats interesting
Seems its trying to communicate with the states before going back to eu server?
I dont have 60ms. I got 500-4k MS ingame.
Do you have high latency both with game and chat? Trying to see if both home and world server connection affected. so i imagine in game latency bar is red with 500-4k?
Iâve had same problem for some days now even contacted my internet provider and could not understand what was going on. SAME ISSUE HERE DANISH TOO. Blizzard please take this serious seems alot of danes are having this problem.
Hope you guys take it serious, many danes experience this and have happend for some days now.
More data:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 33 | 33 | 0 | 0 | 0 | 0 |
| 10.203.64.1 - 0 | 33 | 33 | 9 | 15 | 27 | 11 |
| 10.242.129.134 - 0 | 33 | 33 | 6 | 11 | 20 | 14 |
| 10.0.30.45 - 0 | 33 | 33 | 7 | 12 | 20 | 8 |
| ae20-0.khk7nqp8.dk.ip.tdc.net - 0 | 33 | 33 | 7 | 10 | 15 | 7 |
| ae1-0.stkm2nqp7.se.ip.tdc.net - 0 | 33 | 33 | 17 | 22 | 33 | 20 |
| peer-as57976.stkm2nqp7.se.ip.tdc.net - 0 | 33 | 33 | 17 | 25 | 57 | 26 |
| ae1-br01-eqsk1.as57976.net - 31 | 13 | 9 | 64 | 71 | 117 | 64 |
| et-0-0-3-br01-eqam1.as57976.net - 29 | 14 | 10 | 63 | 70 | 108 | 63 |
| 137.221.65.75 - 0 | 33 | 33 | 46 | 59 | 146 | 57 |
| 137.221.78.51 - 15 | 20 | 17 | 63 | 65 | 74 | 63 |
| 185.60.112.157 - 25 | 16 | 12 | 0 | 65 | 71 | 64 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 27 | 27 | 0 | 0 | 0 | 0 |
| 10.203.64.1 - 0 | 27 | 27 | 10 | 15 | 20 | 17 |
| 10.242.129.134 - 0 | 27 | 27 | 7 | 11 | 15 | 14 |
| 10.0.30.45 - 0 | 27 | 27 | 8 | 13 | 32 | 13 |
| ae20-0.khk7nqp8.dk.ip.tdc.net - 0 | 27 | 27 | 7 | 12 | 15 | 13 |
| ae1-0.stkm2nqp7.se.ip.tdc.net - 0 | 27 | 27 | 17 | 24 | 51 | 23 |
| peer-as57976.stkm2nqp7.se.ip.tdc.net - 0 | 27 | 27 | 19 | 25 | 67 | 23 |
| ae1-br01-eqsk1.as57976.net - 20 | 15 | 12 | 64 | 68 | 95 | 64 |
| et-0-0-3-br01-eqam1.as57976.net - 37 | 11 | 7 | 65 | 119 | 246 | 74 |
| 137.221.65.75 - 0 | 27 | 27 | 33 | 122 | 604 | 33 |
| 137.221.78.47 - 20 | 15 | 12 | 0 | 64 | 70 | 64 |
| 137.221.66.41 - 28 | 11 | 8 | 64 | 65 | 69 | 69 |
| 185.60.112.158 - 12 | 18 | 16 | 63 | 66 | 71 | 63 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 26 | 26 | 0 | 0 | 0 | 0 |
| 10.203.64.1 - 0 | 26 | 26 | 9 | 17 | 63 | 19 |
| 10.242.129.134 - 0 | 26 | 26 | 7 | 12 | 23 | 8 |
| 10.0.30.45 - 0 | 26 | 26 | 7 | 11 | 17 | 15 |
| ae20-0.khk7nqp8.dk.ip.tdc.net - 0 | 26 | 26 | 7 | 12 | 16 | 9 |
| ae1-0.stkm2nqp7.se.ip.tdc.net - 0 | 26 | 26 | 17 | 22 | 28 | 17 |
| peer-as57976.stkm2nqp7.se.ip.tdc.net - 0 | 26 | 26 | 18 | 23 | 47 | 22 |
| ae1-br01-eqsk1.as57976.net - 6 | 17 | 16 | 70 | 73 | 78 | 73 |
| et-0-0-3-br01-eqam1.as57976.net - 22 | 14 | 11 | 69 | 71 | 77 | 70 |
| et-0-0-29-br02-eqam1.as57976.net - 22 | 14 | 11 | 146 | 252 | 414 | 414 |
| et-0-0-3-br02-eqpa4.as57976.net - 0 | 26 | 26 | 39 | 48 | 97 | 40 |
| et-0-0-1-pe04-eqpa4.as57976.net - 16 | 13 | 11 | 69 | 70 | 76 | 70 |
| 137.221.66.39 - 15 | 14 | 12 | 69 | 73 | 76 | 72 |
| 185.60.114.159 - 5 | 20 | 19 | 69 | 71 | 76 | 71 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 12 ms 9 ms 11 ms 10.203.64.1
3 7 ms 7 ms 7 ms 10.242.129.134
4 9 ms 11 ms 7 ms 10.0.30.45
5 9 ms 9 ms 9 ms ae20-0.khk7nqp8.dk.ip.tdc.net [87.61.121.170]
6 18 ms 17 ms 17 ms ae1-0.stkm2nqp7.se.ip.tdc.net [83.88.2.131]
7 20 ms 19 ms 19 ms peer-as57976.stkm2nqp7.se.ip.tdc.net [128.76.59.65]
8 64 ms 68 ms * ae1-br01-eqsk1.as57976.net [137.221.86.33]
9 * 3409 ms * et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
10 1103 ms 1319 ms 1539 ms 137.221.65.75
11 65 ms 65 ms 65 ms 137.221.78.51
12 64 ms 64 ms * 185.60.112.157
13 66 ms 65 ms * 185.60.112.157
14 64 ms 65 ms 65 ms 185.60.112.157
Tracing route to 185.60.112.158 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 12 ms 12 ms 10.203.64.1
3 8 ms 7 ms 7 ms 10.242.129.134
4 23 ms 24 ms 8 ms 10.0.30.45
5 8 ms 9 ms 7 ms ae20-0.khk7nqp8.dk.ip.tdc.net [87.61.121.170]
6 17 ms 17 ms 17 ms ae1-0.stkm2nqp7.se.ip.tdc.net [83.88.2.131]
7 19 ms 19 ms 19 ms peer-as57976.stkm2nqp7.se.ip.tdc.net [128.76.59.65]
8 65 ms 62 ms 63 ms ae1-br01-eqsk1.as57976.net [137.221.86.33]
9 68 ms 63 ms 63 ms et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
10 50 ms 33 ms 33 ms 137.221.65.75
11 64 ms 62 ms 65 ms 137.221.78.47
12 70 ms 64 ms 64 ms 137.221.66.41
13 * 66 ms 64 ms 185.60.112.158
Trace complete.
Tracing route to 185.60.114.159 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 11 ms 10 ms 10.203.64.1
3 7 ms 7 ms 13 ms 10.242.129.134
4 7 ms 24 ms 9 ms 10.0.30.45
5 8 ms 7 ms 6 ms ae20-0.khk7nqp8.dk.ip.tdc.net [87.61.121.170]
6 17 ms 17 ms 19 ms ae1-0.stkm2nqp7.se.ip.tdc.net [83.88.2.131]
7 19 ms 18 ms 17 ms peer-as57976.stkm2nqp7.se.ip.tdc.net [128.76.59.65]
8 70 ms 71 ms 70 ms ae1-br01-eqsk1.as57976.net [137.221.86.33]
9 * * 69 ms et-0-0-3-br01-eqam1.as57976.net [137.221.65.110]
10 160 ms * 128 ms et-0-0-29-br02-eqam1.as57976.net [137.221.65.33]
11 116 ms 40 ms 39 ms et-0-0-3-br02-eqpa4.as57976.net [137.221.65.92]
12 69 ms 69 ms 69 ms et-0-0-1-pe04-eqpa4.as57976.net [137.221.77.53]
13 69 ms 72 ms 71 ms 137.221.66.39
14 73 ms * 71 ms 185.60.114.159
Trace complete.
has this been fixed?
Sadly no, personally I had it for a few days but seems more and more people started to have same problem.
Source country: DK
Source ISP: Hiper (cabled ethernet)
Source ASN: 203953
Tracing route to 37.244.54.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 14 ms 14 ms 12 ms 10.203.88.1
3 10 ms 9 ms 9 ms 10.242.130.254
4 14 ms 9 ms 8 ms 10.0.30.49
5 10 ms 8 ms 9 ms 87.61.121.170
6 17 ms 19 ms 19 ms 83.88.2.131
7 20 ms 21 ms 20 ms 128.76.59.65
8 68 ms 65 ms * 137.221.86.33
9 * * * Request timed out.
10 * * 3072 ms 137.221.65.75
11 * 65 ms 65 ms 137.221.78.47
12 * 66 ms 65 ms 137.221.66.41
13 * * * Request timed out.
14 66 ms * 63 ms 37.244.54.10
ISP: TDC (mobile via USB tethering)
ASN: 3292
Tracing route to 37.244.54.10 over a maximum of 30 hops
1 1 ms 2 ms 2 ms 192.168.248.37
2 * * * Request timed out.
3 198 ms 66 ms 38 ms 10.117.97.174
4 48 ms 39 ms 66 ms 10.219.160.28
5 462 ms 78 ms 58 ms 62.243.140.50
6 115 ms 67 ms 169 ms 83.88.2.128
7 84 ms 431 ms 123 ms 128.76.59.65
8 * 131 ms 108 ms 137.221.86.33
9 124 ms 92 ms 127 ms 137.221.65.110
10 120 ms 177 ms 296 ms 137.221.65.75
11 137 ms 106 ms 117 ms 137.221.78.49
12 256 ms 98 ms * 137.221.66.43
13 * * * Request timed out.
14 1422 ms 1438 ms 1596 ms 37.244.54.10
ISP: 3 (mobile USB tethering)
ASN: 44034
Tracing route to 37.244.54.10 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.248.37
2 * * * Request timed out.
3 1217 ms 524 ms 313 ms 10.66.37.1
4 59 ms 317 ms 325 ms 10.66.199.1
5 871 ms 295 ms 49 ms 10.66.201.170
6 320 ms 1149 ms 102 ms 95.209.204.252
7 75 ms 80 ms 75 ms 10.66.190.9
8 1622 ms 145 ms 92 ms 194.68.128.6
9 65 ms 102 ms 1731 ms 137.221.86.33
10 1417 ms 1356 ms 1283 ms 137.221.65.110
11 86 ms 84 ms 71 ms 137.221.65.75
12 278 ms 150 ms 103 ms 137.221.78.53
13 81 ms 79 ms 474 ms 137.221.66.47
14 * * * Request timed out.
15 667 ms 104 ms 86 ms 37.244.54.10
looks like the tracert is giving home server
now sure if 137.* is world server as this is americas
i see vpns are mentioned to help,also using mobile data
I feel so dumb for thinking this have been my internet for daaaysâŚ
game is unplayable for me right nowâŚHow blizzard is looking into this rather quickly
im also seeing a lot of packet loss at the end near home server from winmtr, looks like latency is ok but cause of packet loss u get bumpy connection
can someone try in cmd:
ping 185.60.112.157 -t
wait for like 25-50 hoops and press ctrl-c to stop
see how many end up dead/high latency pls and post here
Yeah.
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=63ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=67ms TTL=243
Request timed out.
Request timed out.
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=66ms TTL=243
Request timed out.
Request timed out.
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Request timed out.
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=66ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=66ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=68ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=63ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Request timed out.
Request timed out.
Request timed out.
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=63ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Request timed out.
Request timed out.
Reply from 185.60.112.157: bytes=32 time=64ms TTL=243
Reply from 185.60.112.157: bytes=32 time=63ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Request timed out.
Request timed out.
Request timed out.
Reply from 185.60.112.157: bytes=32 time=71ms TTL=243
Request timed out.
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=65ms TTL=243
Reply from 185.60.112.157: bytes=32 time=63ms TTL=243
Mine was just fine yesterday evening, so if youâve had issues for several days, that may be unrelated.