Lag once combat starts

Technical Support
Hi there I have an issue with getting unplayable lag once i engage in any combat.

My ping will be decent 200+ ms (green bar - considered very good for playing in Australia) but the moment i engage any monster the ping skyrockets and becomes unplayable. It will jump to 1.5k+ ping and i usually just end up dead at the end of it.

Anyone else having the same issues or have a way to resolve this?

My internet is fine with everything else, surfing the net / playing other games etc. only in d3 and only once combat starts will my ping skyrocket.
is your lag only once combat starts ?
Hi, I have the same problem. I know that it's a server side lag because when I play other games and buffer youtube videos, they go smoothly unlike in D3, that when combat starts, it's freaking lag. Been experiencing this for 1 week already.
I'm in the same boat. I'm also playin in afghanistan where the lag is bad anyways but most of the time im playing around 750 latency which sucks but is playable. Recently (past 3-4 days) i enter the game at 750-800 latency and everything runs smooth, as soon as i hit mobs in COTA i jump to 2-3k. I at first thought it was COTA because i never farmed it but now i'm unsure.
Hello. I know it might not sound relevant but I had the same problem. In options, sound quality was set to high and i changed it to low sound quality and it solved my lag problems. It might be due to a bug.
Nope that doesnt help me. I'm still doubling or tripling in latency once combat starts. I ran a tracer and this is what it showed me

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 180 ms 397 ms 263 ms 10.5.48.1
2 14 ms 26 ms 94 ms 84.247.46.193
3 542 ms 575 ms 594 ms 172.20.0.1
4 * * * Request timed out.
5 612 ms 560 ms 589 ms 221.120.115.161
6 510 ms 563 ms 558 ms 203.208.190.225
7 615 ms 552 ms 517 ms 203.208.152.225
8 * 710 ms 772 ms 203.208.171.86
9 780 ms 724 ms 798 ms ge-4-0-0-0.laxow-cr1.ix.singtel.com [203.208.183.149]
10 743 ms 739 ms 769 ms 67.17.192.5
11 723 ms 738 ms 793 ms 192.205.34.65
12 768 ms 694 ms 731 ms cr1.la2ca.ip.att.net [12.122.128.98]
13 701 ms 752 ms 696 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 739 ms 788 ms 718 ms 12.122.251.190
15 737 ms 713 ms 742 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.
Nope that doesnt help me. I'm still doubling or tripling in latency once combat starts. I ran a tracer and this is what it showed me

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 180 ms 397 ms 263 ms 10.5.48.1
2 14 ms 26 ms 94 ms 84.247.46.193
3 542 ms 575 ms 594 ms 172.20.0.1
4 * * * Request timed out.
5 612 ms 560 ms 589 ms 221.120.115.161
6 510 ms 563 ms 558 ms 203.208.190.225
7 615 ms 552 ms 517 ms 203.208.152.225
8 * 710 ms 772 ms 203.208.171.86
9 780 ms 724 ms 798 ms ge-4-0-0-0.laxow-cr1.ix.singtel.com [203.208.183.149]
10 743 ms 739 ms 769 ms 67.17.192.5
11 723 ms 738 ms 793 ms 192.205.34.65
12 768 ms 694 ms 731 ms cr1.la2ca.ip.att.net [12.122.128.98]
13 701 ms 752 ms 696 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 739 ms 788 ms 718 ms 12.122.251.190
15 737 ms 713 ms 742 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 * * * Request timed out.

Trace complete.


hop#4-9 are singtel. is that your ISP? because those hops are undoubtedly your problem.
The only address i know for my Isp is 10.5.48.1
04/11/2013 03:47 PMPosted by XxNitewolfxX
The only address i know for my Isp is 10.5.48.1


ah. 1 is usally your pc. which is probably why it looks familar. i was actually asking if you use singtel.

if singtel is your ISP then you need to contact them and find out why your connection is dropping and why you have such high latency.

if that isnt your provider then you are pretty much screwed until it fixes itself.
Well screwed for another 23 days lol.. im playing in afghanistan right now so my latency is usually 750 and i can deal with that. but when i hit combat it jumps to 1600-4000
Having the same problem here. Damn the LAG!
i've been having this problem since they implemented the patch on tues. It is unplayable and the character dies before i can do anything about it. I dont think it is a computer issue or a isp issue, since I can download without any problems. Blizzard. Pls consider your server before implementing patches.....thank you very much
04/13/2013 05:55 AMPosted by Epra
Having the same problem here. Damn the LAG!


04/13/2013 06:17 AMPosted by cthh82
i've been having this problem since they implemented the patch on tues. It is unplayable and the character dies before i can do anything about it. I dont think it is a computer issue or a isp issue, since I can download without any problems. Blizzard. Pls consider your server before implementing patches.....thank you very much


post a tracert that is done during when you are lagging in game.
1 361 ms 4 ms 1 ms gateway.gateway.2wire.net [192.168.1.254]
2 15 ms 4 ms 9 ms bb115-66-67-254.singnet.com.sg [115.66.67.254]
3 11 ms 6 ms 9 ms 202.166.126.14
4 16 ms 12 ms 4 ms ae2-10.qt-ar03.singnet.com.sg [202.166.126.13]
5 6 ms 3 ms 3 ms 202.166.121.101
6 9 ms 9 ms 4 ms ae6-0.singha.singnet.com.sg [202.166.120.186]
7 9 ms 3 ms 3 ms ae3-0.pepsi.singnet.com.sg [202.166.126.125]
8 33 ms 5 ms 3 ms 203.208.190.141
9 4 ms 4 ms 4 ms 203.208.152.213
10 278 ms 270 ms 201 ms ge-0-1-0-0.sngc3-ar4.ix.singtel.com [203.208.183
.46]
11 200 ms 254 ms 191 ms 203.208.171.113
12 186 ms 195 ms 186 ms 67.17.192.141
13 * * * Request timed out.
14 * * * Request timed out.
15 * 200 ms * gar29.la2ca.ip.att.net [12.122.129.241]
16 220 ms * 189 ms 12.122.251.190
17 198 ms 208 ms 206 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
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.
i never had any issues before tues....and this is after the server maint last tues

Will be great if someone can help. thanks in advance
Cant be an internet issue cos internet is fine doing other stuff. I love how blizzard reps always ifnore these kinda posts or just say its a client side issue and ask for tracerts and end up just asking you to call your ISP :(

1 361 ms 4 ms 1 ms gateway.gateway.2wire.net [192.168.1.254]
2 15 ms 4 ms 9 ms bb115-66-67-254.singnet.com.sg [115.66.67.254]
3 11 ms 6 ms 9 ms 202.166.126.14
4 16 ms 12 ms 4 ms ae2-10.qt-ar03.singnet.com.sg [202.166.126.13]
5 6 ms 3 ms 3 ms 202.166.121.101
6 9 ms 9 ms 4 ms ae6-0.singha.singnet.com.sg [202.166.120.186]
7 9 ms 3 ms 3 ms ae3-0.pepsi.singnet.com.sg [202.166.126.125]
8 33 ms 5 ms 3 ms 203.208.190.141
9 4 ms 4 ms 4 ms 203.208.152.213
10 278 ms 270 ms 201 ms ge-0-1-0-0.sngc3-ar4.ix.singtel.com [203.208.183.46]
11 200 ms 254 ms 191 ms 203.208.171.113
12 186 ms 195 ms 186 ms 67.17.192.141
13 * * * Request timed out.
14 * * * Request timed out.
15 * 200 ms * gar29.la2ca.ip.att.net [12.122.129.241]
16 220 ms * 189 ms 12.122.251.190
17 198 ms 208 ms 206 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
18 * * * Request timed out.
19 * * * Request timed out.

Trace complete.


that is a very very bad trace.
im wondering how you even get 300ms+ on the first hop.. lol.
anyway, further down you can see you drop most everything in the ATT.net servers. so it is possible it is a blizzard issue or it could be those connection right before them where you latency spikes that is causing problems as well.
04/15/2013 06:53 PMPosted by Jason
Cant be an internet issue cos internet is fine doing other stuff. I love how blizzard reps always ifnore these kinda posts or just say its a client side issue and ask for tracerts and end up just asking you to call your ISP :(


wheres your tracert and pathping? :)
https://us.battle.net/support/en/article/performing-a-traceroute
https://us.battle.net/support/en/article/running-a-pathping-test

it could be you... ya know. wont know till you post things. right?
lag as of today is HORRIBLE!!! Australia here

Join the Conversation

Return to Forum