Latency spike issues for ~2 weeks

Technical Support
Welp, this is very frustrating. Since returning to the game about 1.5-2 weeks ago, I have been getting latency spikes which makes my game freeze for 2-3 seconds then 'catches' up again. This lag is very annoying and makes the game unplayable for me. Trying to G-rift when you get 2-3 second spikes constantly just results in a feed festival. I've run the pathping test to hopefully resolve this issue and am looking for any insight on what may be causing this lag (note: the lag starts around 5pm est and lasts until around 1-3am est every day, and only have lag in d3, not in any other game or service I use). Any help would be greatly appreciate.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| INTEL_CE_LINUX - 0 | 640 | 640 | 0 | 3 | 103 | 4 |
| INTEL_CE_LINUX - 0 | 640 | 640 | 8 | 15 | 119 | 11 |
| INTEL_CE_LINUX - 0 | 640 | 640 | 9 | 18 | 121 | 16 |
|pos-1-0.gw01.nmkt.phub.net.cable.rogers.com - 0 | 640 | 640 | 16 | 26 | 133 | 20 |
| INTEL_CE_LINUX - 13 | 427 | 373 | 0 | 28 | 117 | 27 |
| INTEL_CE_LINUX - 0 | 640 | 640 | 15 | 26 | 138 | 17 |
| if-8-2.tcore1.CT8-Chicago.as6453.net - 1 | 620 | 615 | 27 | 36 | 134 | 33 |
| if-22-2.tcore2.CT8-Chicago.as6453.net - 0 | 640 | 640 | 28 | 36 | 118 | 33 |
| INTEL_CE_LINUX - 0 | 640 | 640 | 30 | 42 | 136 | 40 |
| cr2.cgcil.ip.att.net - 0 | 640 | 640 | 29 | 39 | 139 | 42 |
| INTEL_CE_LINUX - 0 | 640 | 640 | 29 | 37 | 137 | 33 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 128 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
03/10/2015 03:01 PMPosted by sikatrix
| INTEL_CE_LINUX - 13 | 427 | 373 | 0 | 28 | 117 | 27 |


The 13% packet loss seen here would certainly impact your D3 performance. You can try talking to your ISP about it but be sure to escalate to a tech who can read a pathping or WinMTR report!
I have had huge lad spikes to point where my game lags and never disconnects (just tried for 10 minute period to see if I was the only one having massive lag issues.

Edit: Can't type
You are not the only one for the past two weeks or so.

Same issue.

I've noticed, strangely, that if I stay for more than one grift / rift -- then I start having issues.
If I close the rift after the RG, leave, and join another group -- then I do not run in to this issue.

I've noticed dashing strike has more of a delay than normal.

http://www.internethealthreport.com/Main.aspx?Period=RH24 is pretty helpful to get a state of what's going on over the past day or so.

I know a D3 addict who only recently (about two weeks ago, go figure) started seeing the same issue. Vault on his DH is also delayed. He's in Michigan, I'm from Texas.

I find it highly unlikely, MissCheetah, that these are all coincidences and it's everyone's local ISP all within that two week window and I've been seeing an elevated amount of complaints lately.
03/10/2015 03:28 PMPosted by MissCheetah
03/10/2015 03:01 PMPosted by sikatrix
| INTEL_CE_LINUX - 13 | 427 | 373 | 0 | 28 | 117 | 27 |


The 13% packet loss seen here would certainly impact your D3 performance. You can try talking to your ISP about it but be sure to escalate to a tech who can read a pathping or WinMTR report!


Well, I took your advice and contacted my ISP, but unfortunately the guy had no clue what a pathping or WinMTR report was (doesn't surprise me, I hate you rogers). However, a technician is coming out on Thursday to do some tests from my house.

In the meantime, I did run another WinMTR report thingy in hopes of seeing if anyone has any clue with what is going on. Again, any and all information is greatly appreciated. Thanks again.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| INTEL_CE_LINUX - 65 | 1856 | 652 | 0 | 4 | 109 | 4 |
| INTEL_CE_LINUX - 65 | 1845 | 647 | 8 | 16 | 145 | 10 |
| INTEL_CE_LINUX - 65 | 1856 | 652 | 10 | 20 | 133 | 14 |
|pos-1-0.gw01.nmkt.phub.net.cable.rogers.com - 66 | 1853 | 647 | 16 | 25 | 157 | 19 |
| INTEL_CE_LINUX - 77 | 1640 | 382 | 16 | 27 | 140 | 31 |
| INTEL_CE_LINUX - 65 | 1845 | 647 | 16 | 25 | 156 | 27 |
| if-8-2.tcore1.CT8-Chicago.as6453.net - 66 | 1848 | 642 | 26 | 36 | 160 | 50 |
| if-22-2.tcore2.CT8-Chicago.as6453.net - 66 | 1853 | 647 | 28 | 36 | 157 | 39 |
| INTEL_CE_LINUX - 65 | 1857 | 652 | 30 | 41 | 164 | 42 |
| cr2.cgcil.ip.att.net - 65 | 1845 | 647 | 29 | 40 | 154 | 36 |
| INTEL_CE_LINUX - 65 | 1855 | 652 | 29 | 39 | 154 | 38 |
| No response from host - 100 | 7200 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7199 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7169 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7187 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7198 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7199 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7168 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7183 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7200 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7199 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7169 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7182 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7198 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7198 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7169 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7198 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7200 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7168 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I too have had constant latency issues. I'm from NC and have TWC as my ISP.

This can't be a coincidence. I don't have these issues on any other game. It makes D3 unplayable. If this keeps up, I will have zero desire to play it at all.
So it's not only me, and even people literally from The Americas are experiencing this issue on random. I wonder what's up Blizz, this is getting old. There's something wrong and I know it's not with the ISP. I'm having problems exclusively with D3 and isolated on The Americas server only.
So then I turned playing on ANZ server after had suffered a lot of frustrating lag spikes, doing boring solo plays. It's been over a week and I don't understand why, my internet connection seemed to be stable at that period of time then I found people complaining the same issue as I got.
I'm from SE Asia, I believe Blizzard must have some explanations regarding to this, I understand that (might be) you have some funding problems o_0 since D3 can be considered as a free to play game.. for some people. Probably turning it to pay to play can help you a little.
03/10/2015 08:56 PMPosted by Roen106
I too have had constant latency issues. I'm from NC and have TWC as my ISP.

This can't be a coincidence. I don't have these issues on any other game. It makes D3 unplayable. If this keeps up, I will have zero desire to play it at all.


Same here man. I have TWC 50Mbps package with arris modem getting around 56Mbps. That's around 6.8MB/s. I've never had these issues before always 92-94 latency. But after the patch !@#$ went downhill. Now lantecy around 130+ with spikes in the hundreds.
03/11/2015 06:29 AMPosted by davidchenx
So then I turned playing on ANZ server after had suffered a lot of frustrating lag spikes, doing boring solo plays. It's been over a week and I don't understand why, my internet connection seemed to be stable at that period of time then I found people complaining the same issue as I got.
I'm from SE Asia, I believe Blizzard must have some explanations regarding to this, I understand that (might be) you have some funding problems o_0 since D3 can be considered as a free to play game.. for some people. Probably turning it to pay to play can help you a little.


This game is already expensive with its retail price. And it's not even a MMORPG, I'm sure half of this game's playerbase are seasonal players so I don't see the point in making this a pay to play if you're hinting at a subscription model. I think the only time they experience a heavy server load is when a new expansion or a major patch is out, then it dwindles after the first few weeks.
I have also been having these horrible Latency spikes for 3 days now.

I'm playing in the Americas servers and latency is quite erratic. Even for the few seconds it stays on green, everything still lags. I tried playing in the Asia and Europe servers just to see if it also has the same problem, low and behold, everything is running smoothly and very little to no lags.

Something is up with the Americas servers and Blizzard is not doing anything until this escalates further and more people are affected. In the meantime, they will just sit around and watch us as we rip out our hair from all this lag.

Can Blizzard explain what is happening?
Dang I thought I was alone in this... I've called my ISP's tech over and found that my internet is great...speed great, ping great...

I play in the Philippines and you're right that this happened 1.5 to two weeks ago.

The only consolation is that I can stop giving my ISP provider hell and instead vent my anger and frustration with Blizzard.

What's up Blizzard? Too cheap to Get more bandwidth or Fix your Servers?
Same here, experiencing lag issues for almost 2 weeks now. Game is unplayable. But when i change my region to Asia the game is perfectly fine without any lag issues (ping around 83ms). Btw SE Asia (Philippines) player here. Hope that you could resolve this issue asap.
Indonesia here, I've been suffering a very bad lag while playing with other players. Yes it's been almost two weeks ! I thought my ISP was the problem , but it never been. No lags while playing rifts on ANZ server.
I'm having the same kind of problem. it started yesterday (mar.11) PHI date.
i assume it all stared after the last update.
also tried to play by changing regions, and it worked absolutely fine.

what happened to Americas?
anyone can help us with this?
Are we going to get any kind of confirmation that this has even been brought up to networking team at Blizzard? This has been going on days...if not weeks... now and it's getting pretty annoying. I've honestly lost track of the last time I actually got to play lag free. I'd like to be able to play the games that I buy.

PING 71.164.199.117 (71.164.199.117) 56(84) bytes of data.
64 bytes from 71.164.199.117: icmp_seq=1 ttl=52 time=44.2 ms
64 bytes from 71.164.199.117: icmp_seq=2 ttl=52 time=43.7 ms
64 bytes from 71.164.199.117: icmp_seq=3 ttl=52 time=43.4 ms
64 bytes from 71.164.199.117: icmp_seq=4 ttl=52 time=44.7 ms

--- 71.164.199.117 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3046ms
rtt min/avg/max/mdev = 43.446/44.036/44.707/0.507 ms

traceroute to 71.164.199.117 (71.164.199.117), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.560 ms 0.778 ms 0.845 ms
2 * * *
3 12.129.199.177 (12.129.199.177) 0.390 ms 0.404 ms 12.129.248.117 (12.129.248.117) 2.463 ms
4 206.16.68.53 (206.16.68.53) 0.505 ms 0.512 ms 12.129.193.249 (12.129.193.249) 0.540 ms
5 cr2.la2ca.ip.att.net (12.122.129.242) 1.258 ms 1.266 ms 1.290 ms
6 cr2.la2ca.ip.att.net (12.122.129.242) 4.483 ms 4.803 ms 4.015 ms
7 gar29.la2ca.ip.att.net (12.122.129.233) 2.558 ms 2.555 ms 2.551 ms
8 192.205.35.162 (192.205.35.162) 1.387 ms 1.398 ms 1.384 ms
9 B200.DLLSTX-LCR-21.verizon-gni.net (130.81.162.153) 36.550 ms P0-0-0-0.DLLSTX-LCR-22.verizon-gni.net (130.81.151.245) 34.428 ms 34.437 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

traceroute to 71.164.199.117 (71.164.199.117), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.573 ms 0.620 ms 0.713 ms
2 * * *
3 12.129.248.117 (12.129.248.117) 0.395 ms 0.416 ms 0.611 ms
4 206.16.68.53 (206.16.68.53) 0.349 ms 0.437 ms 0.537 ms
5 cr2.la2ca.ip.att.net (12.122.129.242) 4.460 ms 4.468 ms 4.469 ms
6 cr2.la2ca.ip.att.net (12.122.129.242) 4.472 ms 4.099 ms 4.088 ms
7 12.123.132.137 (12.123.132.137) 5.252 ms 5.245 ms 5.146 ms
8 192.205.35.162 (192.205.35.162) 1.367 ms 1.359 ms 1.355 ms
9 B100.DLLSTX-LCR-22.verizon-gni.net (130.81.199.67) 36.586 ms 35.216 ms 35.209 ms
10 * * *
11 pool-71-164-199-117.dllstx.fios.verizon.net (71.164.199.117) 43.101 ms 43.109 ms 43.107 ms

HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 1.4 0.3
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 12.129.248.117 0.0% 10 0.4 0.5 0.4 1.1 0.2
4. 206.16.68.53 0.0% 10 0.3 0.6 0.3 0.9 0.2
5. cr2.la2ca.ip.att.net 0.0% 10 4.8 3.6 1.5 5.2 1.3
6. cr2.la2ca.ip.att.net 0.0% 10 1.7 2.7 1.4 5.2 1.3
7. gar29.la2ca.ip.att.net 0.0% 10 4.0 5.1 2.1 15.7 4.1
8. 192.205.35.162 0.0% 10 1.4 1.4 1.4 1.5 0.0
9. B100.DLLSTX-LCR-22.verizon-gni.net 0.0% 10 37.6 37.3 35.5 38.7 1.1
10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11. pool-71-164-199-117.dllstx.fios.verizon.net 0.0% 10 64.0 46.0 43.1 64.0 6.4

Tracing route to 12.168.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 20 ms 8 ms 7 ms L100.DLLSTX-VFTTP-89.verizon-gni.net [71.164.199
.1]
3 13 ms 18 ms 13 ms G0-3-4-6.DLLSTX-LCR-21.verizon-gni.net [100.41.2
01.130]
4 * * * Request timed out.
5 11 ms 10 ms 9 ms 0.ae1.BR1.DFW13.ALTER.NET [140.222.227.169]
6 12 ms 12 ms 10 ms 192.205.37.125
7 87 ms 51 ms 45 ms cr2.dlstx.ip.att.net [12.122.100.90]
8 46 ms 42 ms 40 ms 12.122.2.82
9 42 ms 44 ms 42 ms cr81.gr2ca.ip.att.net [12.122.154.66]
10 * * * Request timed out.
11 * * * Request timed out.
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 * * * 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.
Yep my ISP technician came out today and lo and behold, there are no problems on their end. Signal and wiring is fine, and all diagnostic tests they ran showed everything is working just fine on their end. Somewhat of a disappointment as I was hoping it would've been a problem with my ISP so I could have it instantly fixed, but... I guess now it's a waiting game with blizz =\. Some confirmation that they know there is a problem and they are working on it would be nice though.
Same issue here at the same time.... my internet conection is fine as far as I know... I used the looking glass and it looks like I'm loosing 100% of packages on some unknown server...

Is there anything else I can do to help with the diagnostic?

traceroute to 190.62.147.74 (190.62.147.74), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.501 ms 0.575 ms 0.678 ms
2 * * *
3 12.129.248.117 (12.129.248.117) 0.355 ms 0.430 ms 12.129.199.177 (12.129.199.177) 1.229 ms
4 206.16.68.41 (206.16.68.41) 0.499 ms 12.129.193.245 (12.129.193.245) 0.730 ms 206.16.68.41 (206.16.68.41) 0.598 ms
5 12.122.251.185 (12.122.251.185) 1.119 ms 12-122-254-225.attens.net (12.122.254.225) 1.096 ms 1.080 ms
6 cr1.la2ca.ip.att.net (12.122.85.34) 2.832 ms 2.452 ms cr2.la2ca.ip.att.net (12.123.132.210) 4.619 ms
7 gar29.la2ca.ip.att.net (12.122.129.233) 5.489 ms 5.442 ms 5.437 ms
8 be3013.ccr23.lax05.atlas.cogentco.com (154.54.13.149) 2.305 ms 2.807 ms 2.611 ms
9 be2180.ccr21.lax01.atlas.cogentco.com (154.54.41.57) 2.278 ms be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81) 2.096 ms be2180.ccr21.lax01.atlas.cogentco.com (154.54.41.57) 2.710 ms
10 be2065.ccr21.iah01.atlas.cogentco.com (154.54.5.65) 38.003 ms 37.807 ms 37.807 ms
11 be2069.ccr21.mia01.atlas.cogentco.com (66.28.4.238) 65.044 ms be2071.ccr22.mia01.atlas.cogentco.com (154.54.0.221) 65.057 ms 65.065 ms
12 be2582.ccr22.mia03.atlas.cogentco.com (154.54.31.158) 65.533 ms 65.566 ms 65.530 ms
13 38.88.165.54 (38.88.165.54) 88.529 ms 87.597 ms 87.591 ms
14 * * *
15 * * *

traceroute to 190.62.147.74 (190.62.147.74), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.409 ms 0.519 ms 0.573 ms
2 * * *
3 12.129.199.177 (12.129.199.177) 0.335 ms 0.389 ms 0.531 ms
4 12.129.193.245 (12.129.193.245) 0.414 ms 0.434 ms 0.601 ms
5 12.122.251.185 (12.122.251.185) 9.951 ms 9.964 ms 9.970 ms
6 cr2.la2ca.ip.att.net (12.123.132.210) 2.726 ms 2.299 ms 2.287 ms
7 gar29.la2ca.ip.att.net (12.122.129.233) 2.958 ms 2.954 ms 2.950 ms
8 be3013.ccr23.lax05.atlas.cogentco.com (154.54.13.149) 2.078 ms 2.430 ms 2.778 ms
9 be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81) 2.104 ms 2.309 ms 2.307 ms
10 be2066.ccr22.iah01.atlas.cogentco.com (154.54.7.53) 37.706 ms 37.929 ms 37.892 ms
11 be2071.ccr22.mia01.atlas.cogentco.com (154.54.0.221) 64.983 ms 64.919 ms 65.495 ms
12 be2582.ccr22.mia03.atlas.cogentco.com (154.54.31.158) 65.523 ms 65.567 ms 65.161 ms
13 38.88.165.54 (38.88.165.54) 90.313 ms 89.428 ms 89.449 ms
14 * * *
15 * * *

PING 190.62.147.74 (190.62.147.74) 56(84) bytes of data.

--- 190.62.147.74 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms

HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 1.0 0.5 4.2 1.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 12.129.199.177 0.0% 10 0.3 23.4 0.3 171.3 53.7
4. 12.129.193.245 0.0% 10 0.3 1.7 0.3 12.2 3.7
5. 12.122.251.185 0.0% 10 1.1 8.2 1.1 48.7 15.2
6. cr2.la2ca.ip.att.net 0.0% 10 4.0 2.9 1.3 4.5 1.0
7. gar29.la2ca.ip.att.net 0.0% 10 2.0 3.2 1.6 5.0 1.3
8. be3013.ccr23.lax05.atlas.cogentco.com 0.0% 10 2.2 2.4 1.9 3.8 0.6
9. be2179.ccr22.lax01.atlas.cogentco.com 0.0% 10 2.5 2.2 2.0 2.5 0.1
10. be2066.ccr22.iah01.atlas.cogentco.com 0.0% 10 37.8 37.9 37.8 38.2 0.1
11. be2071.ccr22.mia01.atlas.cogentco.com 0.0% 10 65.2 65.2 65.0 65.3 0.1
12. be2582.ccr22.mia03.atlas.cogentco.com 0.0% 10 65.5 65.5 65.3 65.7 0.1
13. 38.88.165.54 0.0% 10 90.2 89.3 87.4 90.9 1.1
14. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
Just to add: I tried playing on Asia and it was smooth as... never mind... you get the picture... Blizzard... Please fix your Americas Server !!
bump, response please

Join the Conversation

Return to Forum