Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
Same here. I've been having the same problem since today morning. I didn't have this yesterday. I frequently get 10-20 seconds of lag. Maps can't load, monsters and players stop responding, nobody moves but me. My connection is fine, I didn't have this problem till today. I think there is something wrong with the servers.
Edited by Cihan#1980 on 11/1/2012 3:11 PM PDT
+1 For this, Downloaded CPUID Hardware monitor and noticed the following:
true, my duel gtx 470s run over 90 on d3 lol, when i have vsync on.... without vsync they go over 100c lolz, they always have on d3 since release for some reason haha
Ok the lag started again since about 2 days. Still cant play. Blizzard only says to do stuff we already did. They dont give us a response. Dont know what else to do. Calling on the phone says they cant us; to post here on the forums. I took my time to gather post and tell people to post on 1 post so we can have it organized, but still blizzard doesnt care about it and dont even respond here. So id say keep spamming new posts to see if they at least try to help us out since they wont respond here or have a sticky of any kind.
SPAM NEW TOPICS OF CONSTANT LAGS!!
Game has become unplayable since 1.05. Granted, I don't have the best computer (I'm running it off my laptop), but before 1.05 I had zero problems. I tried dumbing down every setting and there was no change in the amount of lag I'm suffering from. My repair costs have gone through the roof as I find myself getting demolished by arcane sentries that are nowhere near me or by devastator pools that haven't even spawned on my screen yet. I was really excited when the new patch came out, but this is ridiculous. I want my Diablo back! FIX THIS ISH!
this time lags started for me as well, never had problems with it, now few days the game is barely playable
I love lagging in a single player run, its fantastic. No seriously its awesome because I died by a skull cleaver while I was frozen then got disconnected! /sarcasm off
The decision to have solo play require an internet connection is dumb at best. I've lagged out once every day for the past 3 days in a row.
Network lag here.
Usually about the time I get 5 stacks, but generally at random intervals, I am getting booted. To troubleshoot, I ran a ping -t to the default gateway of my DSL's subscriber subnet( eliminating connectivity between my demarcation point )also to the provider's central switch, one of my provider's core routers, my provider's DNS box, and google.
Here's a tracert to the US battle.net IP
Tracing route to 184.108.40.206 over a maximum of 30 hops
1 1 ms 1 ms 2 ms PK5001Z.PK5001Z [192.168.0.1]
2 43 ms 44 ms 49 ms fl-67-233-208-1.dhcp.embarqhsd.net [220.127.116.11
3 47 ms 49 ms 49 ms fl-67-235-246-45.dhcp.embarqhsd.net [67.235.246.
4 47 ms 48 ms 40 ms fl-67-232-254-233.sta.embarqhsd.net [67.232.254.
5 45 ms 41 ms 41 ms 208-110-248-137.centurylink.net [18.104.22.168
6 49 ms 59 ms 59 ms bb-atlngamv-jx9-01-xe-10-1-0.core.cenrurytel.net
7 57 ms 119 ms 49 ms bb-atlngamv-jx9-02-ae0.core.centurytel.net [206.
8 78 ms 79 ms 79 ms atx-edge-03.inet.qwest.net [22.214.171.124]
9 128 ms 149 ms 87 ms nap-brdr-01.inet.qwest.net [126.96.36.199]
10 170 ms 183 ms 184 ms 188.8.131.52
11 117 ms 119 ms 120 ms 184.108.40.206
12 119 ms 119 ms 119 ms cr2.ormfl.ip.att.net [220.127.116.11]
13 128 ms 116 ms 114 ms cr1.ormfl.ip.att.net [18.104.22.168]
14 113 ms 129 ms 121 ms cr2.hs1tx.ip.att.net [22.214.171.124]
15 120 ms 119 ms 119 ms cr1.dlstx.ip.att.net [126.96.36.199]
16 118 ms 119 ms 129 ms cr2.dlstx.ip.att.net [188.8.131.52]
17 126 ms 119 ms 119 ms cr2.la2ca.ip.att.net [184.108.40.206]
18 257 ms 178 ms 178 ms gar29.la2ca.ip.att.net [220.127.116.11]
19 247 ms 121 ms 117 ms 12-122-254-234.attens.net [18.104.22.168]
20 116 ms 119 ms 119 ms 22.214.171.124
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
At the same time, I had a ping -t going to google with no drops during this time. The best publicly provided info I can find to further test is doing a tracert only to 126.96.36.199, but, alas, this ( probably wisely so ) doesn't respond to pings.
Is there another address that could be substituted as a proof of concept that traffic going through my ISP's network is not reaching battle.net in anything resembling a timely fashion? Not that I am asking for my own Autonomous System number in BGP or anything like that, but you would think that an ISP who is all someone can get in certain areas would make an effort to have serviceable routes to some of the larger content providers in the world.
I have had quite a few rounds with tech support who really are only trained to tell me to reset my modem...
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.