Like every issue I’ve come across in this game it isn’t ISP related. This started happening after the game was patched.
yep seems like they are trying to fix it
Here is a game that was around my normal ping in quick play. Somehow it connected me to a server close to mine and it was around 40-60 ping/latency. I still get many games that are either 80 ping or 150 ping. I just wanted to see if this game had any issues. I did notice some stutter in the game.
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 5 | 453 | 432 | 0 | 13 | 92 | 10 |
| 10.112.56.1 - 6 | 445 | 422 | 0 | 13 | 93 | 14 |
| 100.127.73.14 - 6 | 440 | 415 | 0 | 13 | 42 | 13 |
| 100.120.100.4 - 7 | 425 | 397 | 0 | 18 | 113 | 10 |
| 68.1.4.252 - 9 | 401 | 367 | 0 | 27 | 144 | 21 |
| 68.105.30.130 - 11 | 375 | 335 | 20 | 28 | 83 | 25 |
| ae1-br02-eqla1.as57976.net - 12 | 372 | 331 | 0 | 120 | 1683 | 185 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 108 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~
Just as a quick update: I contacted my ISP and they were aware of the issue. They said this:
We have reached out to NTT (Dallas ISP) and they have confirmed the issue but says it is how Blizzard is advertising their routes to them. The most preferred route is through japan which is why our customers (and others of NTT) are seeing High latency.
They suggested our customers call Blizzard and tell them they have a routing issue that is affecting NTT customers and hopefully they will respond with changes.
NTT has reached out to Blizzard but have yet to get a response.
I wish I had some better news. But that is all I have for now. NTT did say they would reach out to us if Blizzard got back with them or if there was a resolution.
So it seems as though we are SOL until Blizzard will admit they did something wrong and try to fix it. No one would be mad if Blizzard would admit that their routing system didn’t work. People are mad because Blizzard is blaming someone else and there is no external sign to consumers that they are willing to resolve the issue.
Agree completely. We are more angry with them not taking the blame when there is proof from multiple places that it is at their end than them being the cause by having a system that doesn’t work properly for everyone. Or is this like when I was in the Army where the narrative was sometimes, “There’s no problem because I said there’s no problem.”
Yeah, I’m no expert but it seems unlikely that the problem is our ISP when people with different ISP all around the world are having the same issue AFTER a blizzard patch. I think they are just hoping it fixes itself because they have no clue what’s going on.
Same problem since patch. Also seeing same increase in ping on Starcraft 2 servers. Here is my MTR:
~~~~
TRACEROUTE:
traceroute to 64.201.115.153 (64.201.115.153), 15 hops max, 60 byte packets
1 Blizzard Blizzard 10.428 ms 10.412 ms 10.417 ms
2 24.105.18.131 (24.105.18.131) 14.031 ms 14.066 ms 14.091 ms
3 137.221.105.16 (137.221.105.16) 14.036 ms 14.063 ms 14.088 ms
4 137.221.66.18 (137.221.66.18) 14.120 ms 14.143 ms 14.155 ms
5 137.221.83.66 (137.221.83.66) 23.029 ms 23.059 ms 23.071 ms
6 137.221.65.68 (137.221.65.68) 304.831 ms 290.252 ms 290.236 ms
7 137.221.65.1 (137.221.65.1) 35.542 ms 200.540 ms 200.543 ms
8 137.221.65.7 (137.221.65.7) 13.360 ms 13.393 ms 13.109 ms
9 137.221.70.34 (137.221.70.34) 13.308 ms 13.106 ms 13.541 ms
10 * * *
11 te-2-3-cr-gw-lax-lsancarcipr300345.race.com (64.201.96.34) 125.403 ms 125.356 ms 125.514 ms
12 po3-cr-gw-lax-lsancarcipr300346.race.com (64.201.96.41) 125.298 ms 125.284 ms 125.352 ms
13 64-201-115-153.sanfrancisco.static.dsl.race.com (64.201.115.153) 122.488 ms 123.665 ms 122.724 ms
14 64-201-115-153.sanfrancisco.static.dsl.race.com (64.201.115.153) 122.527 ms 121.976 ms 122.365 ms
22/07/2019 16:17:17 UTC
--------------------
TRACEROUTE:
traceroute to 64.201.115.153 (64.201.115.153), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.303 ms 0.313 ms 0.326 ms
2 24.105.18.131 (24.105.18.131) 4.281 ms 4.337 ms 4.351 ms
3 137.221.105.16 (137.221.105.16) 0.732 ms 0.777 ms 0.794 ms
4 137.221.66.18 (137.221.66.18) 1.158 ms 1.200 ms 1.217 ms
5 137.221.83.66 (137.221.83.66) 12.941 ms 12.974 ms 12.991 ms
6 137.221.65.68 (137.221.65.68) 203.202 ms 412.067 ms 412.093 ms
7 137.221.65.1 (137.221.65.1) 135.045 ms 135.062 ms 135.081 ms
8 137.221.65.7 (137.221.65.7) 13.081 ms 13.126 ms 13.139 ms
9 137.221.70.34 (137.221.70.34) 13.436 ms 13.199 ms 13.201 ms
10 * * *
11 te-2-3-cr-gw-lax-lsancarcipr300345.race.com (64.201.96.34) 126.612 ms 125.808 ms 125.820 ms
12 po3-cr-gw-lax-lsancarcipr300346.race.com (64.201.96.41) 125.301 ms 125.600 ms 125.807 ms
13 * * *
14 64-201-115-153.sanfrancisco.static.dsl.race.com (64.201.115.153) 123.577 ms 123.337 ms 122.405 ms
22/07/2019 16:17:18 UTC
--------------------
PING:
PING 64.201.115.153 (64.201.115.153) 56(84) bytes of data.
64 bytes from 64.201.115.153: icmp_seq=1 ttl=111 time=124 ms
64 bytes from 64.201.115.153: icmp_seq=2 ttl=111 time=133 ms
64 bytes from 64.201.115.153: icmp_seq=3 ttl=111 time=123 ms
64 bytes from 64.201.115.153: icmp_seq=4 ttl=111 time=123 ms
--- 64.201.115.153 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 123.148/126.226/133.735/4.358 ms
22/07/2019 16:17:17 UTC
--------------------
PING:
PING 64.201.115.153 (64.201.115.153) 56(84) bytes of data.
64 bytes from 64.201.115.153: icmp_seq=1 ttl=111 time=126 ms
64 bytes from 64.201.115.153: icmp_seq=2 ttl=111 time=129 ms
64 bytes from 64.201.115.153: icmp_seq=3 ttl=111 time=126 ms
64 bytes from 64.201.115.153: icmp_seq=4 ttl=111 time=123 ms
--- 64.201.115.153 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 123.222/126.532/129.873/2.387 ms
22/07/2019 16:17:18 UTC
--------------------
MTR:
Start: Mon Jul 22 16:17:17 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 3.4 0.3 14.0 5.4
2.|-- 24.105.18.131 0.0% 10 0.6 2.5 0.5 12.1 3.7
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.5 0.9 0.0
4.|-- 137.221.66.18 0.0% 10 13.0 6.5 0.8 30.7 9.9
5.|-- 137.221.83.66 0.0% 10 95.8 21.9 12.8 95.8 26.0
6.|-- 137.221.65.68 0.0% 10 12.8 90.9 12.8 437.1 134.2
7.|-- 137.221.65.1 0.0% 10 12.9 16.2 12.8 38.3 7.9
8.|-- 137.221.65.7 0.0% 10 12.9 12.9 12.7 13.6 0.0
9.|-- 137.221.70.34 0.0% 10 13.5 23.4 13.0 110.8 30.7
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- te-2-3-cr-gw-lax-lsancarcipr300345.race.com 0.0% 10 125.4 127.3 125.4 134.1 2.9
12.|-- po3-cr-gw-lax-lsancarcipr300346.race.com 0.0% 10 125.5 167.2 125.4 326.5 72.3
13.|-- 64-201-115-153.sanfrancisco.static.dsl.race.com 0.0% 10 122.4 125.3 122.3 137.1 5.2
22/07/2019 16:17:17 UTC
--------------------
MTR:
Start: Mon Jul 22 16:17:18 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 1.1 0.2 4.3 1.5
2.|-- 24.105.18.131 0.0% 10 0.5 0.8 0.5 2.5 0.5
3.|-- 137.221.105.16 0.0% 10 0.6 0.8 0.5 2.3 0.3
4.|-- 137.221.66.18 0.0% 10 1.1 4.2 0.8 25.8 7.8
5.|-- 137.221.83.66 0.0% 10 12.8 13.2 12.8 15.6 0.7
6.|-- 137.221.65.68 0.0% 10 12.8 62.5 12.8 220.0 70.8
7.|-- 137.221.65.1 0.0% 10 12.8 25.3 12.8 97.2 26.9
8.|-- 137.221.65.7 0.0% 10 12.8 16.5 12.8 26.8 5.2
9.|-- 137.221.70.34 0.0% 10 13.0 18.6 12.9 55.8 13.3
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- te-2-3-cr-gw-lax-lsancarcipr300345.race.com 0.0% 10 125.5 125.7 125.3 127.4 0.3
12.|-- po3-cr-gw-lax-lsancarcipr300346.race.com 0.0% 10 125.5 184.0 125.4 435.1 106.1
13.|-- 64-201-115-153.sanfrancisco.static.dsl.race.com 60.0% 10 122.1 122.4 122.1 122.7 0.0
22/07/2019 16:17:18 UTC
--------------------
~~~~
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| fritz.box - 0 | 36 | 36 | 0 | 8 | 24 | 11 |
|host-62-245-142-140.customer.m-online.net - 0 | 36 | 36 | 7 | 9 | 25 | 17 |
| ae0.rt-decix-2.m-online.net - 0 | 36 | 36 | 15 | 15 | 19 | 15 |
| 213.198.77.233 - 0 | 36 | 36 | 15 | 16 | 25 | 16 |
| 213.198.77.233 - 0 | 36 | 36 | 16 | 265 | 273 | 272 |
| ae-1.r25.frnkge08.de.bb.gin.ntt.net - 0 | 36 | 36 | 15 | 16 | 33 | 16 |
| ae-8.r22.asbnva02.us.bb.gin.ntt.net - 0 | 36 | 36 | 105 | 106 | 108 | 107 |
| ae-5.r23.lsanca07.us.bb.gin.ntt.net - 15 | 20 | 17 | 169 | 170 | 180 | 169 |
| ae-12.r31.tokyjp05.jp.bb.gin.ntt.net - 42 | 12 | 7 | 267 | 267 | 269 | 268 |
| ae-3.r00.tokyjp08.jp.bb.gin.ntt.net - 0 | 36 | 36 | 273 | 273 | 275 | 274 |
| ae-1.a00.tokyjp03.jp.bb.gin.ntt.net - 0 | 36 | 36 | 271 | 272 | 281 | 271 |
| 61.213.179.114 - 0 | 36 | 36 | 279 | 291 | 330 | 279 |
| et-0-0-48-br01-eqty2.blizzardonline.net - 0 | 36 | 36 | 262 | 265 | 339 | 262 |
| xe-0-0-0-1-br01-eqla1.as57976.net - 0 | 36 | 36 | 262 | 314 | 626 | 262 |
| et-0-0-2-br01-swlv10.as57976.net - 0 | 36 | 36 | 262 | 265 | 302 | 263 |
| 137.221.65.133 - 0 | 36 | 36 | 268 | 296 | 749 | 290 |
| be1-pe01-eqch2.as57976.net - 0 | 36 | 36 | 261 | 262 | 264 | 262 |
| 24.105.62.129 - 0 | 36 | 36 | 262 | 263 | 267 | 263 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Yeah basically just talked to blizzard support. I don’t want to hate on this game or company too much but its been nearly 10 days and this hasn’t seem to be fixed or close to fixed by anyone. Basically they told me wait longer and hope it fixes. Which means challenges, the event, comp is out the window. Is overwatch still in beta or something because for such a big company it’s taking them a long time like it always does to fix important issues. This isn’t the first time people including myself have had latency issues that lasted up to 2 weeks to a month before being fixed…
I would post my MTR sh*t but what are they gonna do with it? Look at it and then tell me to wait again just like support?
I realized that in spite of my ranting on this I haven’t done like they said and posted my WinMTR results. I hope I did it right. Bare in mind I had to add spaces to some of them because it considered them links and wouldn’t let me post this otherwise.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.42.129 - 0 | 911 | 911 | 1 | 2 | 436 | 2 |
| 68.29.18.1 - 1 | 905 | 904 | 22 | 73 | 1581 | 37 |
| No response from host - 100 | 183 | 0 | 0 | 0 | 0 | 0 |
| 68.29.20.5 - 4 | 803 | 776 | 23 | 76 | 1455 | 29 |
| 144.223.137.225 - 12 | 632 | 562 | 0 | 82 | 1553 | 58 |
| 144.232.22.198 - 56 | 283 | 125 | 0 | 108 | 1278 | 41 |
| 144.232.13.84 - 74 | 232 | 61 | 0 | 90 | 828 | 50 |
| 144.232.5.226 - 56 | 283 | 125 | 34 | 127 | 1456 | 53 |
| ae-10.r11.dllstx09.us.bb.gin .ntt.net - 76 | 229 | 57 | 0 | 287 | 1364 | 373 |
| ae-1.r23.dllstx09.us.bb.gin .ntt.net - 56 | 283 | 125 | 36 | 84 | 1441 | 70 |
| ae-8.r23.snjsca04.us.bb.gin .ntt.net - 22 | 488 | 382 | 70 | 124 | 1477 | 87 |
| ae-21.r30.tokyjp05.jp.bb.gin .ntt.net - 90 | 200 | 21 | 0 | 209 | 328 | 248 |
| ae-2.r00.tokyjp08.jp.bb.gin .ntt.net - 93 | 195 | 15 | 0 | 271 | 1074 | 206 |
| ae-1.a00.tokyjp03.jp.bb.gin .ntt.net - 83 | 213 | 38 | 0 | 226 | 749 | 749 |
| 61.213.179.114 - 77 | 225 | 52 | 0 | 227 | 547 | 366 |
| et-0-0-48-br01-eqty2.blizzardonline .net - 94 | 193 | 13 | 0 | 293 | 1180 | 229 |
| xe-0-0-0-1-br01-eqla1.as57976 .net - 86 | 206 | 29 | 0 | 256 | 636 | 359 |
| et-0-0-2-br01-swlv10.as57976 .net - 88 | 203 | 25 | 0 | 279 | 1095 | 217 |
| 137.221.65.133 - 89 | 202 | 24 | 0 | 231 | 416 | 218 |
| be1-pe01-eqch2.as57976 .net - 88 | 203 | 25 | 0 | 216 | 402 | 256 |
| 24.105.62.129 - 1 | 901 | 899 | 177 | 231 | 1436 | 191 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Did anything work or fix?
its not going to get fixed until blizzard fixes their routing advertisement so if your ISP uses NTT to send your traffic to their servers you probably going to end up in japan server instead.
In my case att uses level 3/ century link to send my traffic over so i dont get affected because of this screw up.
So all this MTR posting not really going to fix it as DanRaggedy ISP engineering team said NTT is being told by blizzard this are the preferred routes for traffic to take at this current time so the system just does what its been told.
Once blizzard fixes it NTT system will correct the path
You sir are amazing, ProtonVPN works great, its free unlimited, and will only ad 30 ping to your normal. Which is way better then 130. But it is a poor long term solution. Bliz needs to fix their route advertisements. Its not like they a indie company who can’t afford to get a network guy who doesn’t automatically blame everything on the ISP.
Latency back to normal on my end. Played a few in QP and here’s an updated WinMTR trace:
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.42.129 - 1 | 949 | 948 | 0 | 0 | 0 | 0 |
| 10.156.77.9 - 0 | 952 | 952 | 22 | 39 | 74 | 24 |
| No response from host - 100 | 190 | 0 | 0 | 0 | 0 | 0 |
| 66.1.79.1 - 1 | 929 | 923 | 0 | 40 | 99 | 29 |
| sl-crs1-hou-.sprintlink.net - 24 | 494 | 379 | 0 | 44 | 74 | 40 |
| 144.232.22.80 - 53 | 306 | 145 | 0 | 46 | 68 | 44 |
| 144.232.0.16 - 93 | 202 | 15 | 0 | 55 | 66 | 62 |
| 144.232.7.42 - 91 | 206 | 20 | 0 | 52 | 63 | 53 |
| cr1.dlstx.ip.att.net - 84 | 218 | 35 | 0 | 46 | 63 | 41 |
| dlstx409me9.ip.att.net - 62 | 274 | 105 | 0 | 45 | 67 | 40 |
| 12.244.90.238 - 1 | 941 | 938 | 35 | 55 | 177 | 121 |
| ae1-br01-eqda6.as57976.net - 86 | 214 | 30 | 0 | 63 | 77 | 71 |
| et-0-0-4-br01-eqch2.as57976.net - 93 | 202 | 15 | 0 | 61 | 68 | 59 |
| be1-pe02-eqch2.as57976.net - 95 | 198 | 10 | 0 | 67 | 81 | 81 |
| 24.105.62.129 - 1 | 949 | 948 | 55 | 72 | 95 | 63 |
Same. It’s routing properly now.
hey guys yes everything should be back to normal, i did have a call from comporium but i was unfortunately at work in a meeting. thanks for all the help and everyone working together.
While accidentally login into live instead of PTR and queuing for comp… It’s actually fixed for me as well. I appreciate the work a lot, but at the same time i am still disjointed that none really talked about it and acknowledged the real problem officially and telling people whats going on. But thank you for fixing it though.
It seems only partially fixed still having issues on my end though my issues have been around since the start of the month
Hey all,
For those who have the NTT issue, we’ve made a change on our end to see if we could affect things. Is anybody still getting routed through Japan? If so, please run a new WinMTR and let’s see that info so we can see what’s up.