 | Diablo III latency reports 2/1/2016 *** Updated ***(1) | Category: Technical SupportFebruary-1-2016 11:44 AM PST (9 years ago)  |
| We're looking into increased reports regarding high latency for Diablo III users in the North American region. When there's more info to report, we'll update this thread.
[Post edited two times, last edit by Omrakos at February-1-2016 2:02 PM PST (9 years ago)] | ||
 | Diablo III latency reports 2/1/2016 *** Updated ***(16) | February-1-2016 1:54 PM PST (9 years ago) |
| We're continuing to investigate these issues. It looks like the majority of impacted players are on Verizon, Time Warner, and Windstream ISPs. Our Network Administrators are reaching out to our service providers to see how we can help address the issue. In the meantime, your traces are extremely useful in gathering information! Please be sure to include the following: Network traces to your region's game server. | ||
| Diablo III latency reports 2/1/2016 *** Updated ***(50) | February-1-2016 3:54 PM PST (9 years ago) |
| We're still working on these issues, but for players on the Verizon ISP, are you still experiencing issues? If so can I get a new set of traces? Time Warner, Windstream and others, we'll reply back as soon as we have more information to share. | ||
| Diablo III latency reports 2/1/2016 *** Updated ***(72) | February-1-2016 8:49 PM PST (9 years ago) |
| Thanks for the additional information, everyone. We're seeing that overall the issue has greatly improved, but some subnets of ISPs (city/state combinations) may still be affected. Our Network Administrators are still investigating. We may likely not have another update for the evening, but we'll be monitoring this thread for any new reports/information and pass along updates as they come to us. | ||
| Diablo III latency reports 2/1/2016 *** Updated ***(117) | February-3-2016 5:00 PM PST (9 years ago) |
| Thanks for the reports everyone. Our Network Engineers have worked with the affected peering points and impact should be alleviated. I've looked over the most recent reports and there are a few outstanding items, however many issues appear to be occurring within a local network and can be troubleshot directly. I've attached a few examples from above: 0 AultmanPC.attlocal.net [192.168.1.73] 2/ 100 = 2% | 1 2ms 2/ 100 = 2% 0/ 100 = 0% homeportal [192.168.1.254] 1 5ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1 4/ 100 = 4% | 2 20ms 8/ 100 = 8% 4/ 100 = 4% cpe-66-74-48-1.dc.res.rr.com [66.74.48.1] 0/ 100 = 0% | 2 4 ms 2 ms 4 ms loop0.57w.ba09.stjh.nf.aliant.net [142.163.63.12] 3 33 ms 2 ms 3 ms ae15-182.dr02.stjh.nf.aliant.net [142.176.208.61] 4 5 ms 3 ms 3 ms be3-50.dr01.stjh.nf.aliant.net [142.166.181.49] If you are still experiencing an issue, give these troubleshooting steps a shot to address any local network issues. In addition to the above, some players have found that disabling QoS on their Network Interface Card may resolve rubberbanding as well. If you continue to experience latency, we'd like to investigate these one-on-one. If a new pattern emerges, we can consolidate those cases and get more engineering eyes involved as well! Please create a new topic with your traceroute, pathping, and Looking Glass report taken while you are experiencing the issue. Our Tech Support Team is also available by live chat, phone callback and ticket to help troubleshoot issues individually. | ||
