Diablo® III

Diablo 3 Latency Issues.

So, Diablo 3 is nearly unplayable for me lately. I basically have to keep exiting the game and reopening it and waiting like 30 minutes hoping that the latency becomes playable because it's always spiking form 300ms to 2k+ ms. Any time I click something nothing happens until like 2 minutes later.

But I have no other games that have this issue. I admit that my internet is not good at all, but why would Diablo 3 be the only game I'm having latency issues with? Are there any fixes for this or is this purely a Blizzard-side issue? Getting kinda annoyed at this point... :(

Edit: Since this patch, I've now been stuck at 700+ ms and the game is literally unplayable now.
Edited by Crispy305#1163 on 5/30/2012 5:40 PM PDT
Reply Quote
90 Human Priest
6765
Can't be server side because I don't lag. It's client side.
Reply Quote
I meant that it has to do with the way Diablo 3 is utilizing my bandwidth. Because it doesn't make sense that this is the only game that is unplayable for me.
Reply Quote
05/30/2012 03:56 PMPosted by Crispy305
But I have no other games that have this issue. I admit that my internet is not good at all, but why would Diablo 3 be the only game I'm having latency issues with? Are there any fixes for this or is this purely a Blizzard-side issue? Getting kinda annoyed at this point... :(


I have the same issue, I have always wondered why WoW and other online games work great but this one does not.
Reply Quote
I've seen a few other people with this problem too which makes me curious as to what could possibly be causing this. I have no firewalls up or anything like that.
Reply Quote
I have that exact same problem!

game is unplayable and im sad! :(
Reply Quote
the foul-up with the patching didn't really help thing's for all. server had to compensate for the load thus sending the latency meter's off the chart's.
Reply Quote
Sound to me like the patch Caused all these problems. Hope they fix it soon. Or it's by by 60 bucks
Reply Quote
I had SOME latency issues prior to the patch, but after the patch the game is literally unplayable for me now. Half the time I try to start the game it gives me an error, and if I finally do get in a game I click stuff and nothing happens until like 2 minutes later when everything happens at once.
Reply Quote
the tracert's do not match up with diablo 3. even world of warcraft is more stable then this ><. needed my break in-between but ain't got because of the lag.
Reply Quote
I play normally everyday..but 44 minutes ago, the lag makes impossible to play...
Reply Quote
What modem are you people with the latency issues using?? I have a Motorola Surfboard 6121 and this started for me about 6 day's ago and has never got any better. i've replaced all hardware and also tried different machines in my house. I have take my router totally out of the equation by connecting directly to my pc. I've fowarded ports, ive had comcast out and put me on a complete new line. No other game is having this issue. My friend lives about a mile away and is on comcast and is not having any problems. I also replaced my modem 4 days ago hoping it was the modem. Honestly there is nothing else to try. I will just have to wait until November to play when i move.
Reply Quote
I have no idea what modem I'm using I'm just plugged into the wall in my apt I guess the internet is shared between the rooms in my apt but no one else is home so there's no torrenting or anything going on.
Reply Quote
I can play every other game just fine, (bf3 css etc) all under 30ms ping, but when i comes to d3 i get over 700 ms

thats some bull!@#$!
Reply Quote
Since I saw in another post that this could be a temporary problem connecting to Battle.net servers or something, here is my tracert to the Diablo 3 server

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 * 1 ms 4 ms 66.158.212.65
2 <1 ms <1 ms <1 ms 172.16.6.1
3 8 ms 7 ms * 12.87.85.153
4 71 ms * 70 ms cr1.ormfl.ip.att.net [12.122.143.18]
5 74 ms 71 ms * cr2.hs1tx.ip.att.net [12.122.1.5]
6 67 ms * * cr1.dlstx.ip.att.net [12.122.28.157]
7 70 ms 70 ms 74 ms cr2.dlstx.ip.att.net [12.122.1.210]
8 82 ms 70 ms 69 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 77 ms 195 ms 73 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 67 ms 67 ms 67 ms 12-122-254-238.attens.net [12.122.254.238]
11 67 ms 67 ms * 12.129.193.250
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 12.129.199.178 reports: Destination net unreachable.

bumping so hopefully a blue can make sense of this information although it looks like the connection is just straight up timing out.
Reply Quote
Bumping again. Really hoping I can get a reply and get some perspective on this.
Reply Quote
Sorry to bump again, I'm just really hoping someone can make sense of my tracert
Reply Quote
Same thing is happening with me dude, I think it's the patch's fault. The lag wasn't this extremely bad (it was still bad tho but was practically perfect in the twilight hours pre-patch). Blizzard should definitely investigate the new patch they implemented.
Reply Quote
Yep, I'm in the same boat, too. How many disappointed customers will it take to get some kind of feedback on this????
Reply Quote
Yes, after the patch my ping has made the game unplayable. Same bad results.
Traceroute has started…

traceroute to 12.129.209.68 (12.129.209.68), 64 hops max, 72 byte packets
1 cpe-76-185-64-1.tx.res.rr.com (76.185.64.1) 36.407 ms 21.663 ms 30.697 ms
2 24.164.208.69 (24.164.208.69) 11.162 ms 12.561 ms 12.937 ms
3 tge2-3.dllatx20-tr01.texas.rr.com (24.175.37.226) 29.348 ms 16.309 ms 24.234 ms
4 tge9-1.dllatx20-tr01.texas.rr.com (24.175.36.177) 16.680 ms 17.366 ms 23.922 ms
5 24.175.49.0 (24.175.49.0) 25.094 ms 19.279 ms 12.199 ms
6 ae-8-0.cr0.dfw10.tbone.rr.com (66.109.6.52) 18.046 ms 22.565 ms 15.928 ms
7 ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 32.947 ms 62.769 ms 14.137 ms
8 ip65-47-204-173.z204-47-65.customer.algx.net (65.47.204.173) 18.550 ms 18.849 ms 15.926 ms
9 192.205.36.101 (192.205.36.101) 37.125 ms 34.473 ms 36.004 ms
10 cr2.dlstx.ip.att.net (12.122.100.90) 72.144 ms 75.587 ms 72.668 ms
11 cr2.la2ca.ip.att.net (12.122.28.178) 68.053 ms 68.526 ms 67.506 ms
12 gar29.la2ca.ip.att.net (12.122.129.241) 61.090 ms 70.411 ms 174.482 ms
13 12-122-254-234.attens.net (12.122.254.234) 61.216 ms
12-122-254-238.attens.net (12.122.254.238) 67.531 ms
12-122-254-234.attens.net (12.122.254.234) 63.766 ms
14 mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 68.243 ms 69.890 ms 72.036 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * 12.129.199.178 (12.129.199.178) 67.884 ms !X
20 * * *
21 * * *
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]