Diablo® III

Performance and Latency/Lag issue...

Now that I've gathered a bit more information about this.. I'm pretty damn sure that most (almost all) of the lag and latency comes directly from the servers.. You see, the world is not ready for online-only Gaming. You have GOT to allow us to play offline or (somehow) improve or do whatever to your servers, idk enough to argue anymore about this, but from what i know, i just wanna play offline and be allowed to go on the AH.. I can see that you decided against that from point one, probably because of something like cheating or something.. well, im pretty sure that there's a way to fix it somehow, regardless of how hard and complex it might be, its definitely much better than either losing players very frequently, or making us really devoted and passionate players extremely frustrated..
Reply Quote
Most lag is actually generated by (greatly simplified, and holding host settings/home router constant) the distance you are from the servers... For example, if you login from California, and the server is in California, your information (packets) take less time and pass through less infrastructure to reach the server (and vice versa from the server to you).

Now, take a similar scenario but with you logging in from Virginia - since your packets have to go through a few thousand miles of copper and fiber to get to the server (and multiple switches), your latency is going to be higher.

I noticed that when I login from VA and when I login from WA, my latency is significantly different - though I'm usually playing on DSL in WA and fiber optic cable in VA, my latency in WA is usually <50 and in VA is 120-150.

Bottom line - though servers can crash, latency is usually tied to the infrastructure between your home system and the server, not necessarily Blizzard's infrastructure or the game server itself (again, all else constant and excluding "rubberbanding" issues that may be linked to bugs).
Reply Quote
I've been playing almost since the game first launched. Something else is going on besides are connections. When the game first came out. I was getting a solid 65msec connection on mid grade internet. I've since upgraded my internet service, since my connection has gotten worse over time. I am getting over 100msec now. Normally 300msec in the yellow zone on the latency bar, the whole time I play the game. It will come and go, but my connection idles around 100msec now. I've seen it go as low as 65msec but it spikes back up. It doesn't stay there like it use to. Also I've been now going into the red zone on my latency meter. Seems to me like it does have something to do with the servers. I think the game is oversold. The only servers are in cali, might explain the problem.

-Blizzardwon
Reply Quote
MVP - Technical Support
Posts: 11,837
View profile
BW, we can't determine that unless you give us a traceroute/pathping. You can find the necessary instructions for running a pathping test here:

https://us.battle.net/support/en/article/running-a-pathping-test

Post the results of the text file in a post here.
________________________________________________
Technical Support MVP
Official Mac Tech Support Forum Cookie™ (Mint Chocolate Chip)
Guaranteed tasty; Potentially volatile when dipped in General Forums Syrup®
Caution: This cookie bites back.
Reply Quote
this are my results, i'm playing from my macbook 2012 16GB RAM and when i get a lot of monsters, i get reaaaaaally laaaag

1 192.168.1.1 (192.168.1.1) 3.829 ms 1.027 ms 0.874 ms 0.829 ms 0.885 ms 0.820 ms * 1.542 ms 1.144 ms 0.949 ms 0.878 ms * 3.729 ms 0.882 ms 0.878 ms 0.881 ms 0.873 ms

Kind regards

Sebastian
Reply Quote
So I decided to run this test to see what I get and here are the results. Is this saying I'm losing 13% of my packets between my iMac and my router?

1 router.asus.com (192.168.1.1) 0.464 ms 1.244 ms 1.259 ms 1.264 ms 0.236 ms 0.260 ms * 0.347 ms 0.292 ms 0.301 ms 1.272 ms 0.243 ms * 0.306 ms 1.266 ms 0.273 ms 0.991 ms 1.006 ms * 1.296 ms 0.232 ms 0.972 ms 1.001 ms 1.247 ms * 0.306 ms 0.995 ms 0.260 ms 0.987 ms 1.010 ms (13% loss)
2 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
3 172.21.1.116 (172.21.1.116) 8.929 ms 9.351 ms 8.286 ms 9.340 ms 9.878 ms 9.588 ms 8.666 ms 8.120 ms 16.422 ms 11.552 ms 16.336 ms 15.397 ms 9.932 ms 17.474 ms 10.341 ms 10.126 ms 10.199 ms 8.480 ms 9.229 ms 15.042 ms 10.771 ms 8.089 ms 11.544 ms 10.300 ms 10.837 ms 9.134 ms 8.532 ms 9.672 ms 7.610 ms 8.450 ms (0% loss)
4 70.169.75.116 (70.169.75.116) 13.548 ms 10.965 ms 11.909 ms 12.320 ms 15.716 ms 12.580 ms 11.332 ms 12.470 ms 11.419 ms 12.057 ms 15.921 ms 17.142 ms 11.402 ms 15.661 ms 12.219 ms 11.584 ms 12.056 ms 11.881 ms 12.032 ms 15.824 ms 12.075 ms 12.112 ms 11.735 ms 12.105 ms 16.832 ms 23.123 ms 21.623 ms 12.512 ms 11.803 ms 20.740 ms (0% loss)
5 70.169.75.153 (70.169.75.153) 12.585 ms 12.053 ms 9.537 ms 12.169 ms * 9.984 ms 11.829 ms 9.811 ms 10.305 ms 15.480 ms * 9.783 ms 10.415 ms 10.421 ms * 11.147 ms 12.820 ms * 11.550 ms * 25.762 ms 11.137 ms 12.560 ms * * 10.611 ms 10.777 ms 10.158 ms 9.780 ms * (26% loss)
6 langbprj02-ae2.rd.la.cox.net (68.1.1.19) 21.735 ms 65.531 ms 22.126 ms 24.158 ms 23.940 ms * 24.913 ms 25.597 ms * 23.774 ms 23.601 ms 23.479 ms 22.793 ms * * 22.720 ms * * * 22.628 ms * 23.060 ms 21.720 ms 26.920 ms * * * * 22.604 ms * (43% loss)
7 216.156.65.25.ptr.us.xo.net (216.156.65.25) 21.221 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 22.732 ms
216.156.65.25.ptr.us.xo.net (216.156.65.25) 22.633 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 25.628 ms
216.156.65.25.ptr.us.xo.net (216.156.65.25) 22.165 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 23.387 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 21.816 ms 22.066 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 23.642 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 26.482 ms
216.156.65.25.ptr.us.xo.net (216.156.65.25) 25.520 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 21.096 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 21.718 ms 21.814 ms 21.972 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 23.818 ms
216.156.65.25.ptr.us.xo.net (216.156.65.25) 22.083 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 21.883 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 21.368 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 21.591 ms
216.156.65.25.ptr.us.xo.net (216.156.65.25) 21.637 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 21.759 ms
216.156.65.25.ptr.us.xo.net (216.156.65.25) 21.875 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 21.380 ms
216.156.65.25.ptr.us.xo.net (216.156.65.25) 25.787 ms 21.676 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 31.078 ms
216.156.65.9.ptr.us.xo.net (216.156.65.9) 24.740 ms 21.650 ms
216.156.65.41.ptr.us.xo.net (216.156.65.41) 24.276 ms (0% loss)
8 207.88.13.86.ptr.us.xo.net (207.88.13.86) 38.160 ms 33.030 ms 35.958 ms 39.602 ms 44.465 ms 37.103 ms 36.395 ms 46.230 ms 35.927 ms 36.185 ms 35.899 ms 48.015 ms 40.225 ms 45.430 ms 46.235 ms 49.159 ms 50.484 ms 33.630 ms 35.937 ms 35.905 ms 35.839 ms 34.757 ms 45.626 ms 39.632 ms 46.716 ms 40.318 ms 33.100 ms 35.702 ms 36.212 ms 36.132 ms (0% loss)
9 207.88.14.226.ptr.us.xo.net (207.88.14.226) 34.123 ms 34.683 ms 34.118 ms 34.327 ms 39.090 ms * 35.026 ms 36.281 ms * 35.371 ms * * 38.407 ms 34.726 ms * * 36.899 ms * 35.835 ms * * 36.144 ms * * * 37.639 ms * * * 38.545 ms (50% loss)
10 192.205.37.189 (192.205.37.189) 32.883 ms 33.612 ms 32.501 ms 33.129 ms 34.365 ms 31.731 ms 35.730 ms 33.925 ms 99.053 ms 74.646 ms 52.923 ms 34.121 ms 31.999 ms 36.498 ms 34.657 ms 32.085 ms 39.927 ms 32.560 ms 31.632 ms 31.924 ms 32.122 ms 34.226 ms 31.257 ms 32.298 ms 31.913 ms 32.038 ms 32.211 ms 31.636 ms 32.656 ms 32.139 ms (0% loss)
11 cr1.sffca.ip.att.net (12.122.200.10) 60.081 ms 54.865 ms 53.354 ms 52.361 ms 61.645 ms 51.473 ms 49.888 ms 55.513 ms 54.587 ms 44.177 ms 51.740 ms 44.714 ms 43.589 ms 46.935 ms 54.279 ms 45.399 ms 43.212 ms 42.177 ms 46.299 ms 43.761 ms 44.909 ms 48.432 ms 45.979 ms 46.270 ms 53.729 ms 52.136 ms 54.719 ms 54.651 ms 51.701 ms 56.351 ms (0% loss)
12 cr1.la2ca.ip.att.net (12.122.3.122) 43.264 ms 42.590 ms 44.556 ms 41.664 ms 46.660 ms 43.449 ms 47.609 ms 45.974 ms 46.074 ms 45.230 ms 42.035 ms 41.170 ms 42.461 ms 39.427 ms 41.465 ms 39.013 ms 40.517 ms 39.452 ms 40.441 ms 39.472 ms 40.379 ms 40.653 ms 45.830 ms 41.147 ms 47.633 ms 49.058 ms 40.859 ms 42.752 ms 43.010 ms 44.391 ms (0% loss)
13 gar20.la2ca.ip.att.net (12.122.128.181) 38.582 ms 39.095 ms 36.223 ms 39.856 ms 37.434 ms 36.454 ms 38.118 ms 44.068 ms 45.980 ms 54.570 ms 38.553 ms 39.253 ms 39.226 ms 38.691 ms 38.033 ms 39.760 ms 43.612 ms 51.899 ms 36.005 ms 36.344 ms 38.353 ms 39.517 ms 36.150 ms 46.683 ms 37.144 ms 38.449 ms 37.442 ms 37.062 ms 39.105 ms 38.199 ms (0% loss)
14 12-122-254-234.attens.net (12.122.254.234) 36.810 ms 36.180 ms 36.128 ms 38.178 ms 36.303 ms 35.945 ms 35.838 ms 42.392 ms 35.148 ms 37.440 ms 37.163 ms 35.237 ms 36.190 ms 36.166 ms 36.653 ms 36.947 ms 38.223 ms 36.732 ms 35.159 ms 36.749 ms 35.716 ms 37.323 ms 36.445 ms 36.128 ms 37.879 ms 35.782 ms 36.136 ms 37.550 ms 36.428 ms 37.559 ms (0% loss)
15 mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 40.568 ms
206.16.68.46 (206.16.68.46) 39.912 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 37.092 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 45.305 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 40.451 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 40.756 ms
206.16.68.46 (206.16.68.46) 44.196 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 39.269 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 43.956 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 41.544 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 63.795 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 40.558 ms
206.16.68.46 (206.16.68.46) 39.019 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 44.380 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 37.504 ms
206.16.68.46 (206.16.68.46) 35.426 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 38.076 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 42.986 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 44.653 ms
206.16.68.46 (206.16.68.46) 45.061 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 44.637 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 37.391 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 45.323 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 42.726 ms
206.16.68.46 (206.16.68.46) 35.665 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 40.463 ms
206.16.68.46 (206.16.68.46) 41.210 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 39.661 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 42.963 ms
206.16.68.46 (206.16.68.46) 34.019 ms (0% loss)
16 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
17 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
18 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
19 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
20 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
21 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
22 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
23 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
24 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
25 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
26 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
27 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
28 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
29 * * * * * * * * * * *traceroute: wrote 12.129.209.68 52 chars, ret=-1
*traceroute: wrote 12.129.209.68 52 chars, ret=-1
Edited by DarkSith#1115 on 10/28/2013 7:24 PM PDT
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)

Reported!

[Close]