I’m experiencing some pretty bad latency issues in Diablo 3 ever since I installed it yesterday. My latency in game varies WILDY from ~75ms up to 900+ (I’m on the East Coast, Western NY). It will often sit at 200-400ms. About half the time my latency is 900ms and I’m rubberbanding a crap ton in game. The last thing I want to do is make a cliche, “omg this is unplayable, laggggg” post. Was hoping someone could give me so assistance.
Windows 10, fresh machine (within 2 months), netgear nighthawk router, spectrum ISP
Things that I have tried so far:
- Restarting router
- Renewing IP
- Clear DNS cache
- Shut off Blizzard Update Agent
- Uninstalled Battle.net and Reinstalled
- Double checked Windows Firewall exceptions and made sure D3 was on for both public and privite
I downloaded WinMTR and ran a test targeting Diablo 3’s server according to the common connection and latency issues guide in this forum
Here are my results when I ran WinMTR from my machine
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 1999 | 1999 | 0 | 0 | 21 | 0 |
| 142.254.217.49 - 1 | 1995 | 1994 | 8 | 13 | 1394 | 15 |
| agg63.wbstnyaj01h.northeast.rrcom - 1 | 1995 | 1994 | 12 | 50 | 386 | 280
| agg61.hnrtnyaf02r.northeast.rrcom - 1 | 1995 | 1994 | 10 | 15 | 33 | 14 |
| be28.albynyyf01r.northeast.rrcom - 1 | 1995 | 1994 | 17 | 25 | 46 | 24 |
|bu-ether14.hstqtx0209w-bcr00.tbone.rrcom - 1 | 1995 | 1994 | 25 | 33 | 52 | 30 |
| 66.109.5.119 - 1 | 1995 | 1994 | 24 | 30 | 72 | 29 |
| 24.27.236.137 - 1 | 1995 | 1994 | 25 | 33 | 133 | 29 |
| ae1-br01-eqny8.as57976net - 1 | 1995 | 1994 | 78 | 85 | 194 | 81 |
| et-0-0-2-br02-eqch2.as57976net - 1 | 1995 | 1994 | 83 | 91 | 198 | 87 |
| et-0-0-29-br01-eqch2.as57976net - 1 | 1972 | 1971 | 78 | 147 | 2458 | 242 |
| 137.221.65.132 - 1 | 1977 | 1976 | 83 | 145 | 3211 | 333 |
| et-0-0-2-br01-eqla1.as57976net - 1 | 1993 | 1992 | 82 | 99 | 1861 | 88 |
| 137.221.68.81 - 1 | 1995 | 1994 | 78 | 85 | 201 | 112 |
| lax-eqla1-ia-bons-03.as57976net - 1 | 1995 | 1994 | 83 | 88 | 106 | 87 |
| 24.105.30.129 - 1 | 1995 | 1994 | 83 | 87 | 108 | 88 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Which led me to believe that there was no issue that it could pick up.
I then used Blizzards LookingGlass interface and seemed to maybe discover and issue? I ran it with looking at MTR, Traceroute, and PING for Diablo3 and Battle.net Authentication.
Here’s LGs results for D3
TRACEROUTE:
traceroute to 67.240.237.204 (67.240.237.204), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.551 ms 0.548 ms 0.549 ms
2 24.105.18.131 (24.105.18.131) 0.794 ms 0.868 ms 0.956 ms
3 137.221.105.16 (137.221.105.16) 1.161 ms 1.167 ms 1.168 ms
4 137.221.66.22 (137.221.66.22) 1.169 ms 1.170 ms 1.171 ms
5 137.221.83.86 (137.221.83.86) 16.685 ms 16.688 ms 16.693 ms
6 137.221.65.68 (137.221.65.68) 6.348 ms 7.357 ms 7.333 ms
7 137.221.68.32 (137.221.68.32) 7.224 ms 5.960 ms 5.970 ms
8 ae34.pr1.lax10.tbone.rrcom (66.109.9.160) 16.960 ms 14.549 ms 14.522 ms
9 66.109.5.134 (66.109.5.134) 47.971 ms 51.697 ms 51.676 ms
10 bu-ether12.snjucacl67w-bcr00.tbone.rrcom (66.109.6.6) 57.595 ms 57.608 ms 55.307 ms
11 bu-ether12.snvacaid17w-bcr00.tbone.rrcom (66.109.6.9) 58.704 ms 55.753 ms 55.731 ms
12 bu-ether14.chcgildt87w-bcr00.tbone.rrcom (66.109.6.15) 60.842 ms 56.811 ms 56.762 ms
13 66.109.6.73 (66.109.6.73) 67.257 ms 65.946 ms 65.915 ms
14 agg1.wbstnyaj02h.northeast.rrcom (24.58.52.21) 77.188 ms 80.754 ms 80.719 ms
15 agg2.wbstnyaj01m.nyroc.rrcom (24.58.233.62) 75.115 ms 75.008 ms 75.000 ms
24/03/2020 23:19:02 UTC
PING:
PING 67.240.237.204 (67.240.237.204) 56(84) bytes of data.
— 67.240.237.204 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
24/03/2020 23:19:02 UTC
MTR:
Start: Tue Mar 24 23:19:02 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 1.7 0.5 12.0 3.5
3.|-- 137.221.105.16 0.0% 10 0.8 0.9 0.6 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 0.4 4.8 0.4 42.2 13.1
5.|-- 137.221.83.86 0.0% 10 114.2 126.4 27.8 254.9 70.7
6.|-- 137.221.65.68 0.0% 10 5.8 10.8 5.7 24.8 8.0
7.|-- 137.221.68.32 0.0% 10 38.3 15.5 5.9 38.3 13.8
8.|-- ae34.pr1.lax10.tbone.rrcom 0.0% 10 5.4 7.4 5.4 18.0 4.2
9.|-- 66.109.5.134 0.0% 10 50.8 48.0 45.5 50.9 2.1
10.|-- bu-ether12.snjucacl67w-bcr00.tbone.rrcom 0.0% 10 51.1 54.1 51.1 57.8 2.3
11.|-- bu-ether12.snvacaid17w-bcr00.tbone.rrcom 0.0% 10 56.7 54.6 51.5 57.0 2.1
12.|-- bu-ether14.chcgildt87w-bcr00.tbone.rrcom 0.0% 10 56.5 53.7 50.1 56.7 2.3
13.|-- 66.109.6.73 0.0% 10 69.3 66.7 64.2 69.6 2.1
14.|-- agg1.wbstnyaj02h.northeast.rrcom 0.0% 10 75.2 110.8 74.8 307.7 76.2
15.|-- agg2.wbstnyaj01m.nyroc.rrcom 0.0% 10 74.9 75.0 74.9 75.1 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
24/03/2020 23:19:02 UTC
Here is LGs results for Battle.net Authenitcation
TRACEROUTE:
traceroute to 67.240.237.204 (67.240.237.204), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.835 ms 1.816 ms 1.892 ms
2 24.105.18.131 (24.105.18.131) 2.588 ms 2.606 ms 2.632 ms
3 137.221.105.16 (137.221.105.16) 2.601 ms 2.603 ms 2.606 ms
4 137.221.66.22 (137.221.66.22) 1.947 ms 1.962 ms 1.965 ms
5 137.221.83.86 (137.221.83.86) 8.299 ms 8.327 ms 8.332 ms
6 137.221.65.68 (137.221.65.68) 8.349 ms 6.211 ms 6.186 ms
7 137.221.68.32 (137.221.68.32) 6.520 ms 6.536 ms 6.536 ms
8 ae34.pr1.lax10.tbone.rrcom (66.109.9.160) 6.026 ms 5.893 ms 5.887 ms
9 66.109.5.134 (66.109.5.134) 51.095 ms 51.142 ms 51.146 ms
10 bu-ether12.snjucacl67w-bcr00.tbone.rrcom (66.109.6.6) 52.873 ms 52.086 ms 52.054 ms
11 bu-ether12.snvacaid17w-bcr00.tbone.rrcom (66.109.6.9) 54.534 ms 51.433 ms 51.478 ms
12 bu-ether14.chcgildt87w-bcr00.tbone.rrcom (66.109.6.15) 57.266 ms 57.281 ms 54.379 ms
13 66.109.6.73 (66.109.6.73) 64.121 ms 63.715 ms 63.702 ms
14 agg1.wbstnyaj02h.northeast.rrcom (24.58.52.21) 203.618 ms 123.481 ms 123.438 ms
15 agg2.wbstnyaj01m.nyroc.rrcom (24.58.233.62) 75.197 ms 74.892 ms 74.941 ms
24/03/2020 23:19:47 UTC
PING:
PING 67.240.237.204 (67.240.237.204) 56(84) bytes of data.
— 67.240.237.204 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
24/03/2020 23:19:47 UTC
MTR:
Start: Tue Mar 24 23:19:47 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.7 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.8 0.4 2.6 0.5
3.|-- 137.221.105.16 0.0% 10 1.0 0.9 0.6 1.2 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 6.5 0.3 59.9 18.8
5.|-- 137.221.83.86 0.0% 10 107.9 73.3 5.8 198.7 69.1
6.|-- 137.221.65.68 0.0% 10 5.9 13.3 5.7 65.6 18.6
7.|-- 137.221.68.32 0.0% 10 59.5 11.3 5.8 59.5 16.9
8.|-- ae34.pr1.lax10.tbone.rrcom 0.0% 10 5.5 5.6 5.5 5.7 0.0
9.|-- 66.109.5.134 0.0% 10 48.5 48.3 45.4 51.3 2.2
10.|-- bu-ether12.snjucacl67w-bcr00.tbone.rrcom 0.0% 10 56.6 54.0 51.1 56.7 2.2
11.|-- bu-ether12.snvacaid17w-bcr00.tbone.rrcom 0.0% 10 53.3 53.4 50.1 56.0 2.2
12.|-- bu-ether14.chcgildt87w-bcr00.tbone.rrcom 0.0% 10 53.7 54.4 51.1 56.8 2.1
13.|-- 66.109.6.73 0.0% 10 66.1 67.5 63.5 71.3 2.9
14.|-- agg1.wbstnyaj02h.northeast.rrcom 0.0% 10 75.8 97.1 67.5 267.6 60.1
15.|-- agg2.wbstnyaj01m.nyroc.rrcom 0.0% 10 74.9 75.0 74.8 75.1 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
24/03/2020 23:19:47 UTC
The thing that puzzles me is the MTR report for looking glass. It shows step 16 as ??? and with a 100% loss. Would that mean information is being sent out, received by Blizzard, being sent back, and then not getting back to me on the last step???
Thanks for anyone that spends time looking at this. Pretty frustrating issue.