Diablo® III

Lag once combat starts

Yea mine looks pretty bad too. Tonight I had 2 disconnects and gave up. I cant remember the last time I had a disconnect....

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 8 ms 7 ms 7 ms 10.250.128.1
2 8 ms 7 ms 7 ms dtr01thbdla-tge-2-3.thbd.la.charter.com [96.34.8
9.17]
3 12 ms 10 ms 13 ms dtr02slidla-vln-3.slid.la.charter.com [96.34.89.
2]
4 13 ms 11 ms 11 ms dtr04slidla-tge-0-7-0-1.slid.la.charter.com [96.
34.88.138]
5 12 ms 11 ms 15 ms bbr02slidla-tge-0-1-0-6.slid.la.charter.com [96.
34.1.188]
6 28 ms 35 ms 36 ms bbr01atlnga-bue-4.atln.ga.charter.com [96.34.0.3
5]
7 39 ms 35 ms 35 ms be-10-405-pe01.56marietta.ga.ibone.comcast.net [
75.149.231.149]
8 43 ms 39 ms 38 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.
149.228.86]
9 85 ms 71 ms 71 ms cr1.attga.ip.att.net [12.122.141.182]
10 71 ms 72 ms 71 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 71 ms 71 ms 71 ms cr2.la2ca.ip.att.net [12.122.28.178]
12 244 ms 101 ms 69 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 70 ms 77 ms 71 ms 12.122.251.190
14 72 ms 69 ms 70 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
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.

Trace complete.
Reply Quote
04/16/2013 06:26 PMPosted by Jackal
Yea mine looks pretty bad too. Tonight I had 2 disconnects and gave up. I cant remember the last time I had a disconnect....


your trace looks normal. it doesnt look like there is really any excessive lag or connection drops in there.

id say if you are still having problems though the day after a patch then you may try a pathping as well. it shows packet loss. it could indicate where something may be wrong, and if its on your side or your ISP you may be able to do something. if not though then it will still tell you what is likely happening.

i suggest doing traceroutes and pathpings while you are experiencing server lag btw. since it can fluctuate sometimes its best to do it when you lag so you can find out where the problem is. doing it while everything is fine likely will only give you a result that is fine.
Reply Quote
Hey Morg - thanks for the analysis.....but I am guessing Blizz either screwed up in the patches/maints or are turning off their servers simply because fewer people play - but this is truely unfair to those who remain loyal to the game and they would lose EVEN MORE players and generate lesser revenue from the expansion releases...

SO PLEASE WAKE UP!!
Reply Quote
I strongly doubt that they are turning off servers due to people not playing. Whats a little server overhead compared to $50 a player plus whatever they get off RMAH.

No, seriously, I have been playing lag free ever since the beta. Oven over WiFi, which I thought would be an issue, but no, its been nice......

Up until the patching a few days ago.

Then....lag city. When I reach an area I haven't been to since the patching, it lags hard. I fight, and die. If I go back in, I can usually play fairly well up to the point I die, then its back to lag. It feels like caching or something. Just not sure.

TraceRT looks good. PathPing shows some drops. I think its the patches as well. Pathping and traceRT until Blizzard is done.

Tracing route to 12.129.209.68 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.2.1
2 13 ms 11 ms 13 ms 10.65.128.1
3 9 ms 10 ms 10 ms ten9-0-1.bkfd04-ser1.bhn.net [72.31.200.223]
4 10 ms 13 ms 13 ms 72-31-201-166.net.bhntampa.com [72.31.201.166]
5 16 ms 15 ms 23 ms te0-7-0-0-lsanca4-rtr3.socal.rr.com [66.75.161.104]
6 29 ms 15 ms 16 ms 107.14.17.132
7 15 ms 14 ms 14 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 19 ms 13 ms 15 ms ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
9 14 ms 13 ms 17 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
10 14 ms 13 ms 15 ms 66.110.59.42
11 13 ms 17 ms 15 ms cr1.la2ca.ip.att.net [12.122.82.246]
12 13 ms 15 ms 112 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 51 ms 207 ms 208 ms 12.122.251.190
14 37 ms 51 ms 192 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
15 * * * Request timed out.
repeat "Request timed out"....to 30.

PathPing - could be an issue with my ISP.... that is a bummer

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 xxxxxxxxxxxx [192.168.2.2]
1 192.168.2.1
2 10.65.128.1
3 ten9-0-1.bkfd04-ser1.bhn.net [72.31.200.223]
4 72-31-201-166.net.bhntampa.com [72.31.201.166]
5 te0-7-0-0-lsanca4-rtr3.socal.rr.com [66.75.161.104]
6 107.14.17.132
7 ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
8 ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
9 if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
10 66.110.59.42
11 cr2.la2ca.ip.att.net [12.122.84.70]
12 gar29.la2ca.ip.att.net [12.122.129.241]
13 12-122-254-234.attens.net [12.122.254.234]
14 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Daddy-PC.Belkin [192.168.2.2]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.65.128.1
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% ten9-0-1.bkfd04-ser1.bhn.net [72.31.200.223]
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 72-31-201-166.net.bhntampa.com [72.31.201.166]
0/ 100 = 0% |
5 21ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-0-lsanca4-rtr3.socal.rr.com [66.75.161.104]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% 107.14.17.132
0/ 100 = 0% |
7 19ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
0/ 100 = 0% |
8 18ms 0/ 100 = 0% 0/ 100 = 0% ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
0/ 100 = 0% |
9 18ms 0/ 100 = 0% 0/ 100 = 0% if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
0/ 100 = 0% |
10 21ms 0/ 100 = 0% 0/ 100 = 0% 66.110.59.42
100/ 100 =100% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.84.70]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.
Reply Quote
This is still happening today. I'm not posting a pathping because this thread is almost a year old and still nothing has been done.

Thanks Blizzard, for helping me decide to pass on Reaper of Souls. How about less expansion, more fixing this problem that has plagued your game for YEARS now?
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]