Here’s a traceroute and MTR from the looking glass tool
TRACEROUTE:
traceroute to 152.169.25.88 (152.169.25.88), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.253 ms 0.233 ms 0.232 ms Blizzard(24.105.18.3) 0.900 ms 0.910 ms 0.919 ms
3 137.221.105.16 (137.221.105.16) 0.898 ms 0.903 ms 0.910 ms
4 137.221.66.18 (137.221.66.18) 0.891 ms 0.893 ms 0.896 ms
5 137.221.83.66 (137.221.83.66) 7.986 ms 7.999 ms 7.998 ms
6 137.221.65.68 (137.221.65.68) 5.639 ms 5.788 ms 5.751 ms
7 137.221.68.32 (137.221.68.32) 5.522 ms 5.577 ms 5.555 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 5.440 ms 5.427 ms 5.491 ms
9 ae-1-3.edge1.SanJose2.Level3.net (4.69.209.157) 14.124 ms 14.116 ms 14.105 ms
10 ae9-10G.edge1.SanJose.Level3.net (4.68.110.98) 166.611 ms 166.861 ms 166.180 ms
11 195.22.220.15 (195.22.220.15) 331.321 ms 331.361 ms 331.314 ms
12 185.70.203.33 (185.70.203.33) 310.702 ms 310.185 ms 310.150 ms
13 221-165-89-200.fibertel.com.ar (200.89.165.221) 306.913 ms 306.847 ms 306.850 ms
14 * * *
15 * * *
I am having same problem with that hop. High packet loss and MS. This is 5th or 6th post I have seen people winmtr and they ALL show same hop that is having issues.
This is something we’re looking into at the moment and is mainly affecting players in Argentina. We have a thread on the forums here where we’ll be providing updates as we get them. In the meantime, the main workaround we’ve seen so far is to connect through a VPN if this is an option for you.
What about xe-0-0-1-1-br01-eqpa4.as57976. net which is much worse? This hop for me is reason I’m experiencing high MS. I have seen others as well who have posted winmtr and theirs too are showing this hop here is high ms and packet loss.
That hop is generally not a concern. Both of the connections here spiking to around 2-3kms is due to mitigation/firewall. The average latency for both of these align with the rest of the test. xe-0-0-1-1-br01-eqpa4.as57976.net - 1 1712 1704 284 299 2504 288 et-0-0-2-br01-eqch2.as57976.net - 2 1660 1643 284 317 4571 296
It’s stating its routing to Milan, Italy which is why the latency increases from around 17ms to 200ms. We have made some recent changes though today. Could you try checking the game again and see if the latency is back to normal?
Zhyxen i’m sure you can recall cause its your job, but every single time blizzard had problems with Argentina/brasil/chile and other LAS seabone was the main issue. Every single time. It would be wise to try and have a permanent solution with seabone once and for all.
Thx in advance
Same exact problem - Arnet ISP same 175ms and now 283, 175 is bearable, 283 its imposible worse if you like to rank bg or do raids.
I can play other games and everything runs smooth by my side. Just wow with high ms.
I was ok for a few days now last night and today it is back. Even a VPN is not working. This is while playing.
|------------------------------------------------------------------------------------------|