Diablo® III

Latency/spiking issues

I have played diablo 3 since beta. Most of the time its absolutely find runs smoothe as butter with no issues.

In the last couple weeks and more importantly the last few days I have had a ton of issues. The mornings seem fine for the most part but afternoon/evening/night it gets unplayable.

I have run everything possible that I can think of to narrow down the problem. It only happens with diablo 3 and ironically diablo 2 spikes as well. Every other game, streaming online, downloads online are all perfectly fine.

I will be playing d3 and latency jumps up to 300-400 and in cases where im in public games or a lot is going on my latency jumps to over 1200. It literally becomes unplayable. I go to cast a skill and it doesn't go off for 3-4 seconds, im holding down archon beam and let go and it doesn't stop shooting for 3 seconds afterward.

Please tell me if there is something I am doing wrong or some test I can run to narrow down the problem even more.

Im 99% sure it is some diablo server issues and it seems to be happening since LAST WEEKS maintenance, before that it was perfectly fine.
Reply Quote
I am having the same issue it started about 2 weeks ago. I have been told on this forum to bring all my settings down to low. Drop my sound settings to the lowest settings and nothing is changing. I get massive lag spikes and rubberbanding. My latency shows between. 62 to 79 when this is happening.

I am running 2 ATI radeon 5900 HD Crossfired. I have 12 gigs of ram, AMD Phenom II X4 980.

My internet is steady over 500 mbps downloading.

Could use some advice.
Reply Quote
Unreal huge fps drops too, 50-60 all morning and early afternoon. 5:00 hits and fps starts dropping down more and more by the minute by 5:30-6:00 down to 15-20 by 7:00 and on its at like 4-5 fps.

Just got so bad last game (playing solo) i froze for 30 seconds got kicked off bnet and couldnt connect back for a minute.

All other games work/running fine
Reply Quote
Huge issue with lag for the last 2 days.
Reply Quote
I have also been having some serious latency issues since the last update. I will start Diablo and can play fine for about 15-20 minutes. After that my latency begins to increase from ~100 to 400-500. After that the rubberbanding begins and my latency continues to climb until I get frustrated and quit. Game is pretty much unplayable at most times.
Reply Quote
Trying to figure out why im limited to playing morning/early afternoon hours only because at all other times its nearly unplayable.

This is the most frustrating thing ever.

Also have no idea if it deals with anything, but i live north east US. Buffalo Ny area.
Reply Quote
And forced to stop playing for the day because of the game servers

Is this problem ever going to get fixed?
Reply Quote
Just to throw it out there

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 55 ms 26 ms 33 ms cable-mac1.bflonytj-ar4002.nyroc.rr.com [74.77.96.1]
2 12 ms 10 ms 9 ms 98.0.2.129
3 10 ms 11 ms 10 ms ae8-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.30]
4 28 ms 27 ms 27 ms bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
5 29 ms 26 ms 27 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
6 27 ms 24 ms 26 ms ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
7 25 ms 29 ms 27 ms 216.1.94.65
8 78 ms 72 ms 74 ms 207.88.13.253.ptr.us.xo.net [207.88.13.253]
9 * 63 ms 65 ms 207.88.14.178.ptr.us.xo.net [207.88.14.178]
10 52 ms 51 ms 54 ms 206.111.13.246.ptr.us.xo.net [206.111.13.246]
11 131 ms 138 ms 132 ms cr1.n54ny.ip.att.net [12.122.81.106]
12 128 ms 131 ms 151 ms cr2.cgcil.ip.att.net [12.122.1.2]
13 127 ms 131 ms 131 ms cr1.cgcil.ip.att.net [12.122.2.53]
14 134 ms 131 ms 130 ms cr2.dvmco.ip.att.net [12.122.31.85]
15 * 134 ms 130 ms cr1.slkut.ip.att.net [12.122.30.25]
16 133 ms 131 ms 129 ms cr2.la2ca.ip.att.net [12.122.30.30]
17 128 ms 129 ms 127 ms gar20.la2ca.ip.att.net [12.122.128.181]
18 130 ms 126 ms 147 ms 12-122-254-234.attens.net [12.122.254.234]
19 131 ms 128 ms 129 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Devin-PC [192.168.0.2]
1 cable-mac1.bflonytj-ar4002.nyroc.rr.com [74.77.96.1]
2 98.0.2.129
3 ae8-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.30]
4 bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
5 ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
6 ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
7 216.1.94.65
8 207.88.13.253.ptr.us.xo.net [207.88.13.253]
9 207.88.14.178.ptr.us.xo.net [207.88.14.178]
10 206.111.13.246.ptr.us.xo.net [206.111.13.246]
11 cr1.n54ny.ip.att.net [12.122.81.106]
12 cr2.cgcil.ip.att.net [12.122.1.2]
13 cr1.cgcil.ip.att.net [12.122.2.53]
14 cr2.dvmco.ip.att.net [12.122.31.85]
15 cr1.slkut.ip.att.net [12.122.30.25]
16 cr2.la2ca.ip.att.net [12.122.30.30]
17 gar20.la2ca.ip.att.net [12.122.128.181]
18 12-122-254-234.attens.net [12.122.254.234]
19 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
20 * * *
Computing statistics for 475 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Devin-PC [192.168.0.2]
0/ 100 = 0% |
1 12ms 0/ 100 = 0% 0/ 100 = 0% cable-mac1.bflonytj-ar4002.nyroc.rr.com [74.77.96.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 98.0.2.129
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% ae8-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.30]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
0/ 100 = 0% |
5 28ms 0/ 100 = 0% 0/ 100 = 0% ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
0/ 100 = 0% |
6 44ms 0/ 100 = 0% 0/ 100 = 0% ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% 216.1.94.65
0/ 100 = 0% |
8 71ms 0/ 100 = 0% 0/ 100 = 0% 207.88.13.253.ptr.us.xo.net [207.88.13.253]
0/ 100 = 0% |
9 69ms 0/ 100 = 0% 0/ 100 = 0% 207.88.14.178.ptr.us.xo.net [207.88.14.178]
5/ 100 = 5% |
10 63ms 5/ 100 = 5% 0/ 100 = 0% 206.111.13.246.ptr.us.xo.net [206.111.13.246]
95/ 100 = 95% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.81.106]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.2.53]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
19 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.
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]