Diablo® III

High Latency

Hi i've had the game for almost a year now and during that time i never really had any latency issues. I've checked with my internet provider to ensure it was them and they said everything was good to go. i've also done a full system scan and had no discrepancies to be noted. Is there anything you guys can do to help me?

Latency is usually anywhere from 150-2000

normally when i played in the past it was always 50 or below
Reply Quote
so they block hong kong players too ?
this doesn't make sense I don't do anything wrong and legit players
now with this high latency totally unplayable
Reply Quote
MVP - Technical Support
View profile
KenLsc, please do not listen to trolls like that. Blizzard does not block players and no, that has nothing to do with latency.

You said you are connecting from Hong Kong, which is quite a long way from the Americas region servers. Some lag is to be expected. You never had a major issue with it before though so we know your PC can handle the game (unless your PC is having issues too). Usually sudden latency is caused by changes to the local networking infrastructure in the home, or more often something in the many hops between you and Blizzard is not working as efficiently anymore.

Please post your tracert and pathping so we can at least start looking for a reason.
https://us.battle.net/support/en/article/performing-a-traceroute
https://us.battle.net/support/en/article/running-a-pathping-test
Edited by MissCheetah#1661 on 7/7/2013 6:31 AM PDT
Reply Quote
funny how you completely contradict yourself. you first say connecting from hong kong has nothing to do with latency, then go on to say some lag is expected because of how far away he is from the americas server. you are the troll here misscheetah. you know damn well how far away someone is from a server has to do with latency, i have nothing against legit players but there is an asia server they should be playing on.

Network Latency = (Distance Delay) + (Serialization Delay) + (Queue Delay) + (Forwarding Delay) + (Protocol Delay)
Edited by LoRdNuKe#1594 on 7/7/2013 2:29 PM PDT
Reply Quote
07/07/2013 02:16 PMPosted by LoRdNuKe
funny how you completely contradict yourself. you first say connecting from hong kong has nothing to do with latency, then go on to say some lag is expected because of how far away he is from the americas server.


i think your either misunderstanding things or purposely trying to twist words around. i havent decided which it is though.

07/07/2013 06:30 AMPosted by MissCheetah
KenLsc, please do not listen to trolls like that. Blizzard does not block players and no, that has nothing to do with latency.


07/07/2013 06:30 AMPosted by MissCheetah
You said you are connecting from Hong Kong, which is quite a long way from the Americas region servers. Some lag is to be expected.


these are the two sections you are complaining about.
the first say that Blizzard doesnt block users and that it (the blocking being suggested) has nothing to do with the lag.

the second says that their distance is the most likely cause of the latency.
Reply Quote
MVP - Technical Support
View profile
I said Blizzard does not block players which seemed to concern Ken. I further said that Asian players are not the cause of lag. that was the first section.

The rest of the post went on to address the real issue here..which is a sudden increase in latency. Some lag is of course expected due to distance, but a sudden change as the OP indicated is reason to look into it. Since this thread was made, we have seen a few more posts indicating latency from the Asia region and that for some it is limited to certain times of day. That points to an ISP issue with bandwidth throttling or some other networking issue between them and Bliz.

The only way to see is to post the tracert and pathping when it is happening.
Reply Quote
I said Blizzard does not block players which seemed to concern Ken. I further said that Asian players are not the cause of lag. that was the first section.

The rest of the post went on to address the real issue here..which is a sudden increase in latency. Some lag is of course expected due to distance, but a sudden change as the OP indicated is reason to look into it. Since this thread was made, we have seen a few more posts indicating latency from the Asia region and that for some it is limited to certain times of day. That points to an ISP issue with bandwidth throttling or some other networking issue between them and Bliz.

The only way to see is to post the tracert and pathping when it is happening.


if i didnt make a good point you would have ignored me because im trolling right? you must not have remembered how horrible the d2 servers were before they created asia servers. it got MUCH better for EVERYONE on the server when all of the koreans moved out of the useast server. more people on the server=more latency. its not just the asians that are getting the lag is what im saying.
Edited by Varraguz on 7/8/2013 12:48 PM PDT
Reply Quote
funny how you completely contradict yourself. you first say connecting from hong kong has nothing to do with latency, then go on to say some lag is expected because of how far away he is from the americas server.


i think your either misunderstanding things or purposely trying to twist words around. i havent decided which it is though.

KenLsc, please do not listen to trolls like that. Blizzard does not block players and no, that has nothing to do with latency.


You said you are connecting from Hong Kong, which is quite a long way from the Americas region servers. Some lag is to be expected.


these are the two sections you are complaining about.
the first say that Blizzard doesnt block users and that it (the blocking being suggested) has nothing to do with the lag.

the second says that their distance is the most likely cause of the latency.


if latency is created by long distances
more people connecting from that long distance create lag aka koreans etc.
that is the contradiction i speak of.

they want in the americas servers because of rmah? i dont know why else. they have everything else on the asia server no? on d2 there was no reason for them not to move to the asia server for less latency.

its just stupid to complain about lag on a server that is 5000+ miles away when he has ASIA SERVER. im done with this thread and this sub-forum. what a joke.
Edited by LoRdNuKe#1594 on 7/7/2013 4:20 PM PDT
Reply Quote
90 Human Warrior
16530
I too am getting some pretty insane lag problems today so I doubt it's just a distance thing. Some of the mobs that are supposed to spawn things on death (like Grotesques) aren't even doing that right now hah.
Reply Quote
So this is what i got so far:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 5 ms 3 ms 3 ms 192.168.1.1
2 13 ms 10 ms 10 ms 10.165.32.1
3 12 ms 12 ms 12 ms vistcmtk04-gex030001.sd.sd.cox.net [68.6.12.42]
4 * * * Request timed out.
5 12 ms 14 ms 22 ms fed1sysc01-gex0901.sd.sd.cox.net [68.6.8.100]
6 40 ms 40 ms 41 ms 68.1.5.188
7 35 ms 34 ms 35 ms ae-6.r05.plalca01.us.bb.gin.ntt.net [129.250.194.141]
8 41 ms 44 ms 41 ms ae-2.r06.plalca01.us.bb.gin.ntt.net [129.250.5.238]
9 42 ms 35 ms 35 ms ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
10 39 ms 38 ms 39 ms 192.205.37.57
11 40 ms 38 ms 38 ms cr1.sffca.ip.att.net [12.122.114.30]
12 41 ms 41 ms 38 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 46 ms 47 ms 46 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 38 ms 38 ms 37 ms 12.122.251.190
15 37 ms 36 ms 37 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 * * * Request timed out.
17 *

And on the second test this is what i got:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Marvin-PC [192.168.1.7]
1 192.168.1.1
2 10.165.32.1
3 vistcmtk04-gex030001.sd.sd.cox.net [68.6.12.42]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Marvin-PC [192.168.1.7]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.165.32.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% vistcmtk04-gex030001.sd.sd.cox.net [68.6.12.42]

Trace complete.
Reply Quote
@RAiN

call your ISP. it looks like you are getting timeouts from within the COX network.
your ISP should be able to help you as far as whats going on with their side of things.

other then that everything else looks normal.
Reply Quote
MVP - Technical Support
View profile
^ I second what Morogoth said. The timeout on hop 4 is part of the cox network and certainly would cause your issue. The rest is, indeed, normal.
Reply Quote
Thanks guys i got a technician coming out tomorrow. hopefully it fixes everything.
Reply Quote
MVP - Technical Support
View profile
Beware....they tend to not tell the truth at the local level.

Hop 1 was the router in your house
Hop 2 was the first cox link
Hop 3 was the second cox link
Hop 4 was the third cox link

They can tell if hop 4 has an issue without going to your house. At your house they can only look at your router (hop 1) and the next hop to the ISP (hop2), which are both fine. Unless they are willing to look at a tracert and comment on it...
Edited by MissCheetah#1661 on 7/8/2013 7:16 PM PDT
Reply Quote
Before the closest maintenance I have only about 170-200 latency so I don't think the lag cause from the distance problem.

I don't good in IT and connection problem so I don't know what should I do. I can just following your instruction to do the txt files.

Here the following is the pathping.txt:

1 sr-1-32-141-118-on-nets.com [118.141.32.1]
2 10.30.21.49
3 10.28.21.9
4 218.189.98.5
5 if-12-3.icore1.HK2-HongKong.as6453.net [116.0.67.65]
6 if-6-1143.tcore1.TV2-Tokyo.as6453.net [180.87.180.37]
7 if-9-2.tcore2.PDI-PaloAlto.as6453.net [180.87.180.17]
8 if-5-2.tcore2.SQN-SanJose.as6453.net [64.86.21.1]
9 Vlan2146.icore1.SQN-SanJose.as6453.net [209.58.116.137]
10 192.205.37.65
11 cr1.sffca.ip.att.net [12.122.86.198]
12 cr1.la2ca.ip.att.net [12.122.3.122]
13 gar20.la2ca.ip.att.net [12.122.128.181]
14 12-122-254-234.attens.net [12.122.254.234]
15 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 * * *

And this is what the tracert.txt notice for:
在上限 30 個躍點上追蹤 12.129.209.68 的路由

1 1 ms 1 ms 1 ms sr-1-32-141-118-on-nets.com [118.141.32.1]
2 3 ms 3 ms 3 ms 10.30.21.49
3 20 ms * 4 ms 10.28.21.9
4 1 ms 1 ms 1 ms 218.189.98.5
5 * 9 ms * if-12-3.icore1.HK2-HongKong.as6453.net [116.0.67.65]
6 50 ms 50 ms 51 ms if-6-1143.tcore1.TV2-Tokyo.as6453.net [180.87.180.37]
7 155 ms 155 ms 155 ms if-9-2.tcore2.PDI-PaloAlto.as6453.net [180.87.180.17]
8 157 ms 158 ms 160 ms if-5-2.tcore2.SQN-SanJose.as6453.net [64.86.21.1]
9 * * * 要求等候逾時。
10 157 ms 156 ms 157 ms 192.205.37.65
11 173 ms 170 ms 171 ms cr1.sffca.ip.att.net [12.122.86.198]
12 174 ms 171 ms 171 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 178 ms * 167 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 167 ms * 167 ms 12-122-254-238.attens.net [12.122.254.238]
15 169 ms 169 ms 169 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 * * * 要求等候逾時。
17 * * * 要求等候逾時。
18 * * * 要求等候逾時。
19 * * * 要求等候逾時。
20 * * * 要求等候逾時。
21 * * * 要求等候逾時。
22 * * * 要求等候逾時。
23 * * * 要求等候逾時。
24 * * * 要求等候逾時。
25 * * * 要求等候逾時。
26 * * * 要求等候逾時。
27 * * * 要求等候逾時。
28 * * * 要求等候逾時。
29 * * * 要求等候逾時。
30 * * * 要求等候逾時。

追蹤完成。

Thank you very much for the help.
Reply Quote
@KenLsc
You should probably check with your ISP. Your connection is dropping as early as hop#3 and continues to have problems after that.

If you are on a wireless connection try using wired.
Edited by Morogoth#1321 on 7/9/2013 12:27 PM PDT
Reply Quote
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 5 ms 3 ms 4 ms 192.168.1.1
2 10 ms 11 ms 11 ms 10.165.32.1
3 18 ms 10 ms 12 ms vistcmtk04-gex030001.sd.sd.cox.net [68.6.12.42]
4 * * * Request timed out.
5 13 ms 13 ms 12 ms fed1sysc01-gex0901.sd.sd.cox.net [68.6.8.100]
6 102 ms 201 ms 63 ms 68.1.5.188
7 213 ms 68 ms 139 ms ae-6.r05.plalca01.us.bb.gin.ntt.net [129.250.194.141]
8 65 ms 206 ms 201 ms ae-15.r06.snjsca04.us.bb.gin.ntt.net [129.250.5.33]
9 91 ms 118 ms 201 ms ae-3.r07.snjsca04.us.bb.gin.ntt.net [129.250.5.59]
10 210 ms 37 ms 163 ms 192.205.37.57
11 3450 ms 161 ms 38 ms cr1.sffca.ip.att.net [12.122.114.30]
12 248 ms 41 ms 125 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 156 ms 146 ms 35 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 70 ms 201 ms 81 ms 12-122-254-238.attens.net [12.122.254.238]
15 306 ms 122 ms 288 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.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Marvin-PC [192.168.1.7]
1 192.168.1.1
2 10.165.32.1
3 vistcmtk04-gex030001.sd.sd.cox.net [68.6.12.42]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Marvin-PC [192.168.1.7]
0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.165.32.1
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% vistcmtk04-gex030001.sd.sd.cox.net [68.6.12.42]

Trace complete.

So i just had the ISP come out and take a look. they replaced my modem and router. Also claimed that everything is good on their end. im still having pretty bad latency. is there anything else i can do?
Reply Quote
07/09/2013 02:47 PMPosted by RAiN
So i just had the ISP come out and take a look. they replaced my modem and router. Also claimed that everything is good on their end. im still having pretty bad latency. is there anything else i can do?


the way im looking at it a service tech would likely tell you that. your modem and the signal to it likely isnt the cause. that is what a service technician is going to check. they will come out to ensure the modem is functioning properly and that the signal on the line is within accepted limits.

since you can get to out to the COX network without problems and the problem only happens after the first hop of the COX network then its likely their servers.

here is something else to try real quick. do another tracert, but do it to www.google.com
see if the connection drops out the same way.

my opinon is that you will need to speak to escalate to a L2 tech or manager before you can get the help you need. the L1 techs that man the phones when you first call dont really know much. all they really are is script monkeys. the real techs you have to get transfered to.
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]