Diablo IIIBlue TrackerTechnical SupportProblem with AT&T Connection - Post advised by live chat agent
 | Problem with AT&T Connection - Post advised by live chat agent(1) | Category: Technical SupportFebruary-9-2016 7:42 PM PST (9 years ago)  |
| Hello Devs :) I've run into issues with a data center and serious packet loss, making the game rather unplayable. I've spoken with a live chat agent and he recommended creating this post to get attention and possible resolution. Support Case ID: 53860871 Here is my pathping results: C:\WINDOWS\system32>pathping 12.129.222.10 Tracing route to 12.129.222.10 over a maximum of 30 hops 0 DESKTOP-PNMJ55E [192.168.2.29] 1 RT-AC87R-FFD0 [192.168.2.1] 2 192.168.1.254 3 172-15-172-1.lightspeed.mssnks.sbcglobal.net [172.15.172.1] 4 71.150.19.40 5 * * 71.150.32.210 6 12.83.42.153 7 12.123.249.225 8 * * * Computing statistics for 175 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 DESKTOP-PNMJ55E [192.168.2.29] 0/ 100 = 0% | 1 2ms 0/ 100 = 0% 0/ 100 = 0% RT-AC87R-FFD0 [192.168.2.1] 0/ 100 = 0% | 2 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254 0/ 100 = 0% | 3 5ms 0/ 100 = 0% 0/ 100 = 0% 172-15-172-1.lightspeed.mssnks.sbcglobal.net [172.15.172.1] 0/ 100 = 0% | 4 5ms 0/ 100 = 0% 0/ 100 = 0% 71.150.19.40 0/ 100 = 0% | 5 5ms 0/ 100 = 0% 0/ 100 = 0% 71.150.32.210 98/ 100 = 98% | 6 6ms 98/ 100 = 98% 0/ 100 = 0% 12.83.42.153 2/ 100 = 2% | 7 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.225 Trace complete. And here is my Looking Glass results: PING: PING 172.15.172.9 (172.15.172.9) 56(84) bytes of data. --- 172.15.172.9 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 5002ms 10/02/2016 03:35:27 UTC -------------------- TRACEROUTE: traceroute to 172.15.172.9 (172.15.172.9), 15 hops max, 60 byte packets 1 Blizzard (Blizzard) 0.410 ms 0.411 ms 0.517 ms 2 * * * 3 12.129.244.189 (12.129.244.189) 0.416 ms * * 4 12.129.193.249 (12.129.193.249) 0.435 ms 0.486 ms 0.622 ms 5 cr1.la2ca.ip.att.net (12.122.128.182) 44.336 ms 44.360 ms 44.366 ms 6 cr1.la2ca.ip.att.net (12.122.128.182) 44.429 ms 43.208 ms 43.203 ms 7 cr1.slkut.ip.att.net (12.122.30.29) 45.547 ms 45.564 ms 45.568 ms 8 cr2.dvmco.ip.att.net (12.122.30.26) 43.718 ms 43.881 ms 45.053 ms 9 cr1.dvmco.ip.att.net (12.122.31.21) 45.606 ms 45.630 ms 45.598 ms 10 cr1.kc9mo.ip.att.net (12.122.3.46) 45.469 ms 45.477 ms 44.930 ms 11 12.122.150.65 (12.122.150.65) 42.012 ms 44.327 ms 44.325 ms 12 * * * 13 71.150.32.211 (71.150.32.211) 42.747 ms 42.920 ms 43.214 ms 14 71.150.19.41 (71.150.19.41) 46.806 ms 46.816 ms 47.986 ms 15 * * * 10/02/2016 03:35:27 UTC -------------------- MTR: Error! Please, try again later. 10/02/2016 03:35:27 UTC -------------------- | ||
 | Problem with AT&T Connection - Post advised by live chat agent(2) | February-9-2016 8:05 PM PST (9 years ago) |
| Hey Lynx, I noticed on the pathping that the connection from hop 2 to 3 is experiencing 1% of data loss. That would be when the data actually leaves your house and transfers to your ISP's network. There could be an issue there but 1% isn't a strong indicator to know for sure. Please use WinMTR to test again. WinMTR tests the connection over a period of time so we can get a better picture of what is going on, opposed to a pathping which is a single moment in time. - Download WinMTR - Extract the download and then run either 32 or 64 bit as an admin. - Use 12.129.222.10 for the Host field and click Start. Let the test run for 5-10 minutes. Play the game during this time if you can. - Stop the test and click Copy Text to clipboard. - Post the results here please. | ||
| Problem with AT&T Connection - Post advised by live chat agent(6) | February-9-2016 10:16 PM PST (9 years ago) |
| Thanks for the info Lynx, When the data jumps to hop 5 on the route, there is a massive loss of data - 62%. That is likely why you are experiencing such severe lag spikes. Now that you have the WinMTR it would be best if you sent it to AT&T when communicating with them. With a clear picture of where the issue lies, they may be able to better assist. We aren't able to directly change anything on the nodes that are dropping packets since it is on AT&T's network. I'll leave the thread open though, if other AT&T customers are experiencing the same issues they can chime in. The more players that report issues the more attention the issue gets. ;) | ||
