 | The server lag is driving me nuts.(1) | Category: Technical SupportOctober-5-2014 7:23 PM PDT (8 years ago)  |
| I have ran the looking glass stuff and here are the results. I have been getting random disconnects and awful lag for a while now. I have posted path ping results as well.. I have no other internet issues. Not in WoW or HearthStone. All other online activities seem fine. D3 is failing and it is annoying. Legendary items being left on the ground. Lagging out for no apparent reason while chat is still working. A long time to log into the game as well.. What gives? traceroute to 198.84.187.2 (198.84.187.2), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.975 ms 1.483 ms 1.505 ms 2 * * * 3 12.129.248.117 (12.129.248.117) 0.417 ms 0.588 ms 0.649 ms 4 206.16.68.53 (206.16.68.53) 0.384 ms 0.416 ms 12.129.193.249 (12.129.193.249) 0.603 ms 5 cr2.la2ca.ip.att.net (12.122.129.242) 1.477 ms 3.419 ms 1.500 ms 6 cr2.la2ca.ip.att.net (12.122.129.242) 1.465 ms 5.057 ms 2.990 ms 7 ggr2.la2ca.ip.att.net (12.122.129.97) 3.600 ms 3.515 ms 3.494 ms 8 ix-15-0.tcore1.LVW-Los-Angeles.as6453.net (66.110.59.41) 1.301 ms 1.399 ms 1.352 ms 9 if-2-2.tcore2.LVW-Los-Angeles.as6453.net (66.110.59.2) 77.567 ms 77.621 ms 77.562 ms 10 if-14-8.tcore2.AEQ-Ashburn.as6453.net (64.86.252.198) 72.157 ms 72.065 ms 72.965 ms 11 if-2-2.tcore1.AEQ-Ashburn.as6453.net (216.6.87.2) 81.058 ms 82.191 ms 82.156 ms 12 64.86.85.1 (64.86.85.1) 76.273 ms 76.276 ms 78.506 ms 13 if-10-2.tcore1.TTT-Toronto.as6453.net (64.86.32.33) 77.775 ms 74.744 ms 69.910 ms 14 if-9-9.tcore1.TNK-Toronto.as6453.net (64.86.33.25) 81.455 ms 81.828 ms 78.163 ms 15 64.86.33.22 (64.86.33.22) 82.384 ms 82.375 ms 83.504 ms traceroute to 198.84.187.2 (198.84.187.2), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.511 ms 0.544 ms 0.770 ms 2 * * * 3 12.129.199.177 (12.129.199.177) 0.404 ms 0.426 ms 0.495 ms 4 12.129.193.249 (12.129.193.249) 0.393 ms 0.414 ms 0.485 ms 5 cr2.la2ca.ip.att.net (12.122.129.242) 1.087 ms 3.344 ms 5.146 ms 6 cr2.la2ca.ip.att.net (12.122.129.242) 3.353 ms 4.704 ms 2.868 ms 7 ggr2.la2ca.ip.att.net (12.122.129.97) 2.770 ms 2.777 ms 1.659 ms 8 ix-15-0.tcore1.LVW-Los-Angeles.as6453.net (66.110.59.41) 1.340 ms 1.343 ms 1.328 ms 9 if-2-2.tcore2.LVW-Los-Angeles.as6453.net (66.110.59.2) 76.367 ms 76.368 ms 76.033 ms 10 if-14-8.tcore2.AEQ-Ashburn.as6453.net (64.86.252.198) 73.555 ms 73.565 ms 73.334 ms 11 if-2-2.tcore1.AEQ-Ashburn.as6453.net (216.6.87.2) 77.973 ms 77.976 ms 77.958 ms 12 64.86.85.1 (64.86.85.1) 76.517 ms 76.517 ms 76.715 ms 13 if-10-2.tcore1.TTT-Toronto.as6453.net (64.86.32.33) 76.284 ms 78.063 ms 78.064 ms 14 if-9-9.tcore1.TNK-Toronto.as6453.net (64.86.33.25) 74.010 ms 73.854 ms 73.836 ms 15 64.86.33.22 (64.86.33.22) 81.235 ms 81.207 ms 81.209 ms PING 198.84.187.2 (198.84.187.2) 56(84) bytes of data. --- 198.84.187.2 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 4999ms HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev 1. Blizzard 0.0% 10 0.5 0.9 0.4 2.6 0.9 2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3. 12.129.199.177 0.0% 10 47.3 29.7 0.3 170.1 56.0 4. 12.129.193.249 0.0% 10 0.5 4.3 0.3 39.4 12.3 5. cr2.la2ca.ip.att.net 0.0% 10 1.7 3.3 1.7 5.0 1.3 6. cr2.la2ca.ip.att.net 0.0% 10 2.1 2.9 2.0 4.8 1.1 7. ggr2.la2ca.ip.att.net 0.0% 10 1.5 3.9 1.5 5.6 1.2 8. ix-15-0.tcore1.LVW-Los-Angeles.as6453.net 0.0% 10 1.3 1.4 1.3 1.4 0.0 9. if-2-2.tcore2.LVW-Los-Angeles.as6453.net 90.0% 10 76.9 76.9 76.9 76.9 0.0 10. if-14-8.tcore2.AEQ-Ashburn.as6453.net 0.0% 10 73.5 73.8 73.5 74.3 0.3 11. if-2-2.tcore1.AEQ-Ashburn.as6453.net 0.0% 10 77.3 81.7 76.1 88.9 4.0 12. 64.86.85.1 0.0% 10 75.7 78.1 75.6 88.0 3.8 13. if-10-2.tcore1.TTT-Toronto.as6453.net 0.0% 10 75.3 77.7 75.3 87.7 3.7 14. if-9-9.tcore1.TNK-Toronto.as6453.net 0.0% 10 73.9 74.6 73.9 77.6 1.2 15. 64.86.33.22 0.0% 10 75.9 80.9 75.9 85.2 2.9 16. ae3_2120-bdr01-tor.teksavvy.com 0.0% 10 76.8 76.5 75.6 80.7 1.6 17. kitchener.cable.packetflow.ca 0.0% 10 82.5 217.5 80.0 642.9 225.6 18. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 | ||
 | The server lag is driving me nuts.(2) | October-5-2014 7:45 PM PDT (8 years ago) |
| Doronik, Let's download WinMTR. This tool will run a different style of pathping which will hopefully give us a little bit more information about what might be going on with the connection. 1. Download WinMTR 2. Unzip the WinMTR.zip file to the Desktop. 3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows. 4. Run the WinMTR.exe 5. Type the IP address you want to trace in the "Host" field. If you are not sure what IP address to use, be sure to check out our "Running A Pathping Test" support article, which mentions all of our IPs used for troubleshooting purposes. 6. Click on "Start" and then launch the game. Once you notice the connection issue, play for about 10 more minutes, minimize the game and click on "Stop". 7. Click on "Copy text to clipboard" and paste the results into your next forum reply. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| The server lag is driving me nuts.(9) | October-6-2014 3:09 PM PDT (8 years ago) |
| Doronik, |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 1108 | 1108 | 0 | 1 | 16 | 1 | | 10.125.103.1 - 1 | 1105 | 1104 | 4 | 10 | 32 | 9 | | 209.148.241.225 - 1 | 1105 | 1104 | 10 | 17 | 42 | 20 | | 24.156.157.81 - 0 | 1109 | 1109 | 11 | 16 | 48 | 16 | | ae1_2120-bdr04-tor.teksavvy.com - 0 | 1109 | 1109 | 9 | 16 | 65 | 15 | |ix-0-0-2-0.tcore1.TNK-Toronto.as6453.net - 5 | 949 | 909 | 11 | 17 | 48 | 15 | | if-5-0-0-5.core4.TNK-Toronto.as6453.net - 0 | 1108 | 1108 | 9 | 28 | 219 | 40 | |if-0-3-2-0.tcore1.CT8-Chicago.as6453.net - 1 | 1081 | 1074 | 23 | 29 | 51 | 28 | | if-22-2.tcore2.CT8-Chicago.as6453.net - 1 | 1105 | 1104 | 21 | 27 | 53 | 30 | Your connection is show some data loss on hops 2, 3, 6, 8, and 9. This is all occurring before the connection has reached our servers. You are going to want to contact your ISP to have them look into this further. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| The server lag is driving me nuts.(10) | October-6-2014 3:24 PM PDT (8 years ago) |
| agentpewpew, there is no reason what so ever the tech support agent needs to know so much about the customers computer that lies within a dxdiag report. they probably need to know something in the range of 5% of that report. asking for a dxdiag to learn what gpu the customer has is just lazy and counterproductive. In any case lets not continue this argument to further derail the thread. It was just a comment regarding the constant postings of dxdiag on these forums, it is kind of unique to this company.. Any tech support troubleshooting forum that you go on will eventually request a DXDIAG, so it's not just a Blizzard thing. The DXDIAG isn't only used to check for what video card they are using. If you know how to read one, there is a lot more information that is provided in the DXDIAG report that we can then use to give suggestions that may help resolve certain issues. Also, asking for the DXDIAG saves time from having customers look up the information themselves. Keep in mind that not all customers are tech savvy. Searching for driver versions and what hardware they are running, will usually take them longer than merely posting the DXDIAG. The third party WinMTR tool was suggested by me because in all honesty, it works better than the options that the Windows OS offers. I could have requested a tracert, but tracerts only run for that instance. If the connection happened to work fine those few minutes that it was running the tracert, we won't see anything. This may lead to needing to run multiple tracerts, which in itself can be considered a waste of time. The same thing applies to pathpings. In fact, some networks are set up to not return ping information, which then results in a blank pathping report. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? [Post edited one time, last edit by Dankorii at October-9-2014 12:38 PM PDT (8 years ago)] | ||
