 | Latency up from 150-200 normal to 800-3500ms unplayable.(1) | Category: Technical SupportAugust-31-2015 1:32 PM PDT (9 years ago)  |
| Hi there. I have (since the new patch) had unplayable latencies. Pre-patch I was running normal on about 170ms but the last few nights I have nothing better than 800, sometimes going up to almost 4000ms. I don't seem to have these issues on WoW, HS and HoTS. Nothing changed, except for patch update on D3. I am wired to a router and then WiFi to AP. I tried a reset on both the router and the WiFi receiver, nothing helped. (which I don't think is the issue in any case otherwise I would have expected it on other applications as well.) I am on Win10, with all the latest drivers installed. Tracert as follows: Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 6 ms 5 ms 14 ms 172.31.1.86 3 10 ms 7 ms 8 ms 172.19.16.73 4 11 ms 9 ms 10 ms 192.168.129.84 5 15 ms 29 ms 8 ms 192.168.180.5 6 16 ms 11 ms 10 ms 192.168.145.12 7 32 ms 10 ms 10 ms cr2-vl369-brp-gwf.sonicwireless.co.za [41.79.195.69] 8 30 ms 10 ms 10 ms er2-e12-nete-cr2-gwf.sonicwireless.co.za [41.79.195.162] 9 18 ms 10 ms 10 ms acrt1-gwf-gi00-ac-snc01-vl236.wolcomm.net [197.157.64.137] 10 30 ms 33 ms 29 ms cr1-gwf-agr1-vl14.wolcomm.net [197.157.77.0] 11 * * * Request timed out. 12 45 ms 29 ms 29 ms agr1-isd-cr1-vl14.wolcomm.net [197.157.77.9] 13 33 ms 39 ms 35 ms 3-1-16.bear1.Johannesburg2.Level3.net [212.73.206.29] 14 239 ms 240 ms 232 ms ae-127-3513.edge6.Amsterdam1.Level3.net [4.69.162.226] 15 220 ms 215 ms 219 ms 4.68.111.178 16 * * * Request timed out. from 16 it times out till 30. Pathping as follows: Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233] over a maximum of 30 hops: 0 Christo-PC.lan [192.168.1.116] 1 192.168.1.1 2 172.31.1.86 3 172.19.16.73 4 192.168.129.84 5 192.168.180.5 6 192.168.145.12 7 cr2-vl369-brp-gwf.sonicwireless.co.za [41.79.195.69] 8 er2-e12-nete-cr2-gwf.sonicwireless.co.za [41.79.195.162] 9 acrt1-gwf-gi00-ac-snc01-vl236.wolcomm.net [197.157.64.137] 10 cr1-gwf-agr1-vl14.wolcomm.net [197.157.77.0] 11 * * * Computing statistics for 250 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 Christo-PC.lan [192.168.1.116] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 11ms 0/ 100 = 0% 0/ 100 = 0% 172.31.1.86 0/ 100 = 0% | 3 14ms 0/ 100 = 0% 0/ 100 = 0% 172.19.16.73 0/ 100 = 0% | 4 14ms 0/ 100 = 0% 0/ 100 = 0% 192.168.129.84 0/ 100 = 0% | 5 15ms 0/ 100 = 0% 0/ 100 = 0% 192.168.180.5 0/ 100 = 0% | 6 15ms 0/ 100 = 0% 0/ 100 = 0% 192.168.145.12 0/ 100 = 0% | 7 16ms 0/ 100 = 0% 0/ 100 = 0% cr2-vl369-brp-gwf.sonicwireless.co.za [41.79.195.69] 0/ 100 = 0% | 8 16ms 1/ 100 = 1% 1/ 100 = 1% er2-e12-nete-cr2-gwf.sonicwireless.co.za [41.79.195.162] 0/ 100 = 0% | 9 22ms 0/ 100 = 0% 0/ 100 = 0% acrt1-gwf-gi00-ac-snc01-vl236.wolcomm.net [197.157.64.137] 100/ 100 =100% | 10 --- 100/ 100 =100% 0/ 100 = 0% cr1-gwf-agr1-vl14.wolcomm.net [197.157.77.0] Trace complete. I would really appreciate some support on the matter. Looking forward to your response. Thanks. | ||
 | Latency up from 150-200 normal to 800-3500ms unplayable.(2) | August-31-2015 1:42 PM PDT (9 years ago) |
| Hi Tansika, Thanks for posting here in the forum. Your trace looks ok. Did you run this trace when you were lagging? A WinMTR can take a longer sample, and you can leave it running in the background while you play. ________________________________________________ Rate me! https://www.surveymonkey.com/s/Velnrak "They say the oaks are just too lofty And they grab up all the light." | ||
