Starting Tuesday afternoon, I started having really horrible ping issues that made the game unplayable. Home ping is normal around 50ms but world sits steady at 500ms and spikes to over 1000ms frequently. Traceroute to the server is attached below. It all looks fairly normal to me except the large 240ms spike. Up to now I have had a steady ping around 50ms and have very very rarely had spikes. While raiding last night I could not do anything and things kept freezing. I know its not just framerate lag because everything on my end keeps moving as normal but the players run in place.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 27 ms 10 ms 8 ms 96.120.76.5
3 15 ms 13 ms 13 ms 68.86.214.245
4 15 ms 14 ms 11 ms 96.110.124.97
5 16 ms 18 ms 16 ms be-201-ar03.ivyland.pa.panjde.comcast.ne [96.108.181.21]
6 17 ms 17 ms 17 ms be-31223-cs02.newark.nj.ibone.comcast.ne [96.110.42.53]
7 27 ms 17 ms 17 ms be-1211-cr11.newark.nj.ibone.comcast.ne [96.110.35.70]
8 * 17 ms 18 ms be-302-cr12.newyork.ny.ibone.comcast.ne [96.110.36.150]
9 17 ms 19 ms 24 ms be-1212-cs02.newyork.ny.ibone.comcast.ne [96.110.35.133]
10 18 ms 17 ms 18 ms be-4211-pe11.60hudson.ny.ibone.comcast.ne [96.110.34.54]
11 17 ms 19 ms 16 ms 50.208.235.78
12 240 ms 167 ms 158 ms ae1-br01-eqny8.as57976.ne [137.221.71.33]
13 * * * Request timed out.
14 34 ms 35 ms 36 ms et-0-0-1-pe04-eqch2.as57976.ne [137.221.69.79]
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.
NOTE: I removed the âtâ at the end of all the â.netâ because the forums wouldnât let me post links.
Have you tried using the looking glass tool yet? It runs the mtr/tracert/ping from their end and it looks like thatâs where your problem is. Iâm having the same issues but it started last week.
Thanks for that! I did not know that tool existed. It appears to slowly go through internal servers then once it hits comcast it speeds along. I am not too tech savvy but here is what it spat out:
TRACEROUTE:
traceroute to MY IP, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.394 ms 0.388 ms 0.390 ms
2 24.105.18.130 (24.105.18.130) 0.857 ms 0.871 ms 0.873 ms
3 137.221.105.14 (137.221.105.14) 0.955 ms 0.962 ms 1.032 ms
4 137.221.66.22 (137.221.66.22) 0.449 ms 0.470 ms 0.473 ms
5 137.221.83.86 (137.221.83.86) 647.266 ms 647.312 ms 647.320 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.974 ms 5.994 ms 6.315 ms
8 be-102-pe12.600wseventh.ca.ibone.comcast.ne (75.149.229.69) 6.311 ms 5.820 ms 5.778 ms
9 be-3112-cs01.losangeles.ca.ibone.comcast.ne (96.110.33.65) 6.653 ms 6.357 ms 6.401 ms
10 be-1112-cr12.losangeles.ca.ibone.comcast.ne (96.110.45.166) 6.636 ms 6.686 ms 6.684 ms
11 be-302-cr13.houston.tx.ibone.comcast.ne (96.110.37.189) 32.501 ms 32.502 ms 32.500 ms
12 be-1413-cs04.houston.tx.ibone.comcast.ne (96.110.46.153) 33.065 ms 32.571 ms 32.504 ms
13 be-1412-cr12.houston.tx.ibone.comcast.ne (96.110.46.150) 32.657 ms 32.769 ms 32.360 ms
14 be-302-cr14.56marietta.ga.ibone.comcast.ne (96.110.39.209) 44.729 ms 44.946 ms 44.974 ms
15 be-1114-cs01.56marietta.ga.ibone.comcast.ne (96.110.34.241) 45.603 ms 45.311 ms 44.909 ms
18/08/2021 14:54:29 UTC
PING:
PING MY IP 56(84) bytes of data.
â MY IP ping statistics â
4 packets transmitted, 0 received, 100% packet loss, time 3007ms
TRACEROUTE:
traceroute to MY IP, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.356 ms 0.344 ms 0.344 ms
2 37.244.23.3 (37.244.23.3) 1.132 ms 1.149 ms 1.150 ms
3 24.105.62.152 (24.105.62.152) 1.150 ms 1.150 ms 1.150 ms
4 137.221.66.10 (137.221.66.10) 2.026 ms 2.047 ms 2.048 ms
5 137.221.69.52 (137.221.69.52) 545.089 ms 545.111 ms 545.113 ms
6 137.221.69.34 (137.221.69.34) 3.399 ms 2.594 ms 2.562 ms
7 CHGOBBRJ01GE030100.r2.ch.cox.ne (68.105.30.217) 1.946 ms 2.929 ms 2.917 ms
8 elmwdsrj01-ae1.0.rd.no.cox.ne (68.1.2.137) 32.126 ms 32.200 ms 32.174 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
Yup it looks pretty similar to mine⌠not sure whatâs going on but i ended up just macroâing a flushdns/release/renew batch file so when i see the latency start to spike iâm back within 30 sec. Wish we had answers instead of a workaround though. Also I didnât know about that tool either but itâs pretty handy.
How long does your ping stay stable after using that trick? Can you write out the code for it so I can copy?
After doing a bit more research and looking up the IP address of the hops with him latency, for some reason my data is being routed from the US to London and back again even though I am playing on a US server. I am not sure if this has always been the case or why it may have changed but that is whatâs happening. It goes from Chicago>London>Philadelphia. Does anyone know why this might be happening and if there is a way to fix it?
The location of where an IP address is registered doesnât always match where that router is physically located.
There are cases where high latency on certain routers is normal (due to the way the device is configured) so itâs important to look at the overall connection test to get the best picture. The results youâve posted so far donât show any major issues. Although if the problem is intermittent then the Looking-Glass tool isnât super useful (since it only runs for a short time).
Can you try running a WinMTR instead when the problem is happening again? WinMTR you can leave running in the background so itâll be running as the problem is happening in-game.
Right-click on the downloaded .zip folder and select âExtract Allâ, to extract the files to a new folder.
Open the new folder that was created, then open the WinMTR_x64 folder.
Right-click on the WinMTR application and select âRun as administratorâ.
Type the IP address 24.105.62.129 in the âHostâ field.
Click on âStartâ and then launch the game. Allow the test to run for at least 10 minutes. Click on âStopâ when youâre done playing after you have experienced the latency or connection issue.
Click on âCopy Text to Clipboardâ, paste the results here, then highlight everything and hit the </> button in the posting section so it will allow links.
Looking Glass is a web-based tool that replaces WinMTR (doesnât require you to download an executable) and is provided by Blizzard. You can also pick a specific server and not just a regional gateway IP, so a better choice imo.
Iâd say 90% packet loss and a 15-sec (not msec) delay is pretty indicative of a major problem on hop 6. This looks very much like the problem that WAVE customers were having HERE. The problem there was that WAVE pushed a port security configuration change on 13-Aug that caused Blizzardâs servers in Las Vegas and New York City to reject incoming packets. WAVE reversed that (for most customers) a day or two later and most players had their issue resolved.
Check with Cox about whether or not they might have changed port security configuration. If you own your own modem/router, see if you had a recent software update that would have closed off ports that Blizzard games use. Also could be a software firewall issue with your anti-virus program (if that updated recently).
That hop just deprioritizes test packets and is not displaying any problems. You can tell when a server is doing that by checking the hops afterward - there is no latency or packet loss to any of the hops after that one, so it canât be losing 90% of traffic.
That particular router is configured to de-prioritize ICMP traffic which is what these connection tests use. So it looks like a bad hop, but in reality your TCP and UDP game traffic is getting through that node just fine with no delay. This is definitely nothing to worry about, look at the hops afterwards to see the latency return to normal levels. If that were an issue the latency would be just as high all the way down from that hop onward.
Looking-Glass does not replace WinMTR, it is simply a different tool that can be used. The big thing with Looking-Glass is that it sends a predetermined amount of packets from the Blizzard server to your modemâs IP and it only runs over a few seconds. WinMTR is more useful when problems are occurring intermittently because you can run WinMTR for as long as you want. Sometimes packet loss problems like this come and go and arenât constant, so WinMTR can help capture that.
Looking-Glass tests the connection from a Blizzard server to you, while WinMTR (and traceroute and pathping) tests the connection from you to the server. Sometimes the route is different in each direction, so it can occasionally be good to look at both. However WinMTR is generally our go-to for latency and packet loss issues.
@Awildtuna - For Macs I recommend using PingPlotter. It does pretty much what WinMTR does for Windows machines, and there should be a free trial available. Iâd recommend taking a screenshot of the output and posting it to imgur.com and then share the link here. Apologies I had assumed you were using a Windows machine. We have a separate Mac Technical Support forum for Macs.
