Latency and Packet Loss Issues

BlizzCS told me to post here on Twitter, so i figured I’d do it again.
I’ve had some pretty serious latency and packet loss spikes over the past few days (NA East, spikes of 80% loss out and minimum 100 ping constantly). The following traceroute data is from about 20 minutes ago:

Tracing route to 24.105.42.210 over a maximum of 30 hops

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 12 ms 10 ms 10 ms 99.242.88.1
3 7 ms 10 ms 10 ms 8089-dgw02.lndn.rmgt.net.rogers. com [24.156.150.29]
4 11 ms 10 ms 14 ms 209.148.236.9
5 27 ms 25 ms 27 ms 64.71.241.110
6 30 ms 27 ms 31 ms eqix-dc2.blizzard. com [206.126.237.174]
7 34 ms 32 ms 33 ms ae1-br01-eqdc2.as57976. net [137.221.72.33]
8 40 ms 37 ms 39 ms et-0-0-2-br01-eqch2.as57976. net [137.221.65.13]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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.

I’ve done all of the standard troubleshooting that blizzard suggests (changing IP, flushing DNS, restarting modem, reinstalling, etc etc) multiple times, and I’ve had zero success whatsoever. I filed a support ticket but apparently the wait time is upwards of 24 hours, which is sort of testing my patience at that point. The only things I was able to understand from the traceroute is that for some reason hop 6 goes all the way to the UK, and it’s also where all the packet loss is occurring (at least that’s what i concluded by pinging the addresses of hops 5 and 6). I’ve had a lot more success playing on KR and EU servers because they’re just consistently unplayable. Any solutions at this point? I seriously have no idea where to go and I’m getting a little desperate for an answer.

Hey, Xylezia! Thank you for the Traceroute test here.

6 30 ms 27 ms 31 ms eqix-dc2.blizzard. com [206.126.237.174]

For hop 6 in the traceroute here, it is not going to the UK. The latency if it was going to the UK would be much higher as well then what we see here. Searching IP’s will give the registration location, not the actual server location. Hop 6 and 7 here is the Ashburn, Virginia Equinix peer, then it moves to the Chicago Equinix (Hop 8) location. The ones prior to hops 6-8 are Roger Cable.

The Traceroute test is not as detailed so it’s not super clear what’s happening, other than we don’t have any data after the equinix chicago node (which is not the server). It’s better to run a WinMTR test while in a Practice vs AI match for 10-15 minutes. This should give us data for the packet loss and latency. Copy and paste the text file created and paste it between two ~~~ like so:

~~~
WinMTR Here
~~~

If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)

A post was merged into an existing topic: Continued latency issues making the game rubber band