For everyone having connection issues of various types: UPDATE 6-9-24

This thread is to attempt to put together a comprehensive list of test results for issues with connections such as lag, disconnects, rubberbanding, stalls, drops, whatever that seems network related.

Updates are listed below the tools!


First off the reasons:


I seem to be seeing a fairly repeated pattern of many of you getting connection blocks/dropped packets as they pass through ISPs. Why is this happening? That is part of the question here. But I need more result data.

I will also be linking every connection issue thread to this one. They will be posted at the bottom of this post as a link and I will link those threads to this one as I can.

To the mods of the forum, if need be, pinning this thread would be helpful.


Now first off. The tools:

WinMTR


You can find this tool here: (this was updated to a new location as Blizzard no longer has it available)

https://sourceforge.net/projects/winmtr/files/latest/download

This tool works best if it can be ran while you are having problems during the game play.

Essentially, download the tool, run your game. Once you have an issue start happening, alt tab to the tool and start it. Then resume playing for at least 5-10 minutes if you can. Then use Export to HTML. This will properly format it for the forum. Then simply paste it into your reply.

Please also post the following info:

  • ISP you use.
  • Any VPN service. You can also run two tests, one with and one without a VPN if need be.

PathPing


How to use this tool here:

  1. Open the Start Menu or hit the Windows key on your keyboard.
  2. Type the letters CMD.
  3. Right-click on CMD (Command Prompt) and select Run as Administrator.
  4. Type: pathping xxx.xxx.xxx.xxx > c:\pathping.txt
  5. Replace the Xs with the appropriate server address you want to test against, or a website address. Please note, Blizzard has removed references to the server IP addresses. The following list may not be accurate:
  • |US Central|34.170.230.40|
  • |US West|34.105.4.61|
  • |Europe|35.240.124.178|
  • |Asia|34.64.174.8|
  1. Once you have chosen an address or website, Press Enter after entering it above.
  2. Allow several minutes for the pathping to complete.
  3. A file will be created in your C: drive called pathping.txt.Type exit and press Enter to close the command window.

You can use this as a basic tool to look for any issues in the traffic in case you are unable to play Diablo IV on your PC or you play from a console. While it won't have as detailed info about the game's connection, it will at least show us any direct issues on the path to the server.
Next you can try this tool as well, it does require installation to use and run as its a 3rd party program:

https://www.pingplotter.com/

More info can be found about this tool here from this thread:

-[Main Thread] Charter/Spectrum ISP Latency Spikes since 1.0.3 - #27 by Zuvykree


**Lastly, there is this thread with some tips and stuff on these tools and other info. Feel free to check it as well!**

Closing thoughts:

Update 8-7-23

Here is a suggestion on changing the DNS server option to see if that will provide a work around to fix latency and connection issues. This can be done on PCs and Consoles. Below are steps for Windows PC users:

For PCs, you need to open the adapter properties and there are a couple ways to do this:

Windows 11/10:

  • Go to Settings->Network and Internet.
  • Under here choose the type of connection you are using, WiFi, or Ethernet.
  • Once chosen, then go to Hardware Properties (for WiFi). If you click on Ethernet, it should take you to the same page. Look for DNS Server Assignment.
  • Click “Edit” change Automatic to Manual, turn on IP4, then enter 8.8.8.8 for Preferred DNS. Click Save.

Alternate method:

  • Hit Windows key and R. Type in Control and run it.
  • Go to Network and Internet.
  • Go to Network and Sharing Center.
  • Click Change Adapter Settings.
  • Find the connection you are using. Double Click it.
  • Go to Properties at the bottom left.
  • Look for Internet Protocol Version 4. Double click that.
  • Where it says Obtain DNS automatically, change that to “Use the following DNS server address”.
  • Enter 8.8.8.8 into the location. You may add 8.8.4.4 to the second box if you wish.

A third option if you are techy enough, you can use your router to assign that IP4 DNS address via the DHCP, you just have to remember to re-acquire the IP address after making the change.

Cautions:

Some networks may need to have the local router as a DNS option for some situations. IN those cases, you may want to set the IP address of your router as your primary DNS, and the 8.8.8.8 as your secondary.

Update 8-4-23


There are some settings you can adjust for your network adapter (wired or wireless) on your PC that might help your latency issues while playing Diablo IV. This revolves around power settings. What you need to do is to make sure your network adapter that you use to connect to your internet is not set for power savings. You want it set to maximum performance. You can do this under the power settings in Windows. There are also settings for performance found in the adapter properties page as well. But by default, most Windows installations use power saving features over performance with network adapters, especially on laptops. This has been causing some of you problems, so its something to check for.

UPDATE 7-6-23


I have added another tool to the list of tools to try above. This was provided as an other option to test your connection for certain cases, but I see no reason to not use it for testing your connection in general:

-https://us.battle.net/support/en/article/000339127

I also wanted to put out an update of something to try that might help. It has been noted that disabling hardware acceleration in the Bnet app can affect this for some of you, but I wanted to expand on this by suggesting the following:

  • Open the Bnet App.
  • Go to settings. (the gear cog at the top left under the Battlenet logo)
  • You should be under “App”.
  • Look for “On Game Launch”.
  • Change this to “Exit Battle.net completely”.
  • Click “Done”.

Then see if the game plays any better here.

UPDATE 6-21-23


Try to run a standard ping test to battle.net or any other common website. To do this:

Try adjusting settings regarding DDOS attacks in your router/modem if possible:

Big thank you to Tarball for this suggestion!



UPDATE 6-19-23

Two things I need to update here:

  • With regards to these tests. They are not absolute, nor are they very accurate. They will give us an idea of what might be going on, but may not be correct or believable either good or bad. So while they may shed some light on an issue, we have to accept them as what they are. Tools that sometimes can make mistakes. With that in mind, accept any interpretations of the results as best attempts by those responding.

  • Second. Those using WiFi connections. Please refer to this except from a post in this thread today:

Remember to thank Node for sharing this fix that might help some of you with issues and using WiFi.

I have a theory that its possible some ISPs are having issues with Diablo IV’s traffic and causing connection disruption. Of course that’s a bold theory and I need more of these tests done to help see if we can find some correlation to that end or another reason.

So please take the time to do these. If you have already done them for the forum elsewhere, you don’t need to do them again, unless you want to see if the results have changed. But for now, just try to post one time with your results.

I will be periodically reviewing the posts and helping explain them if you have any questions.

Thank you everyone!

Links to existing threads: (from the past 12 hours, and I will add more as they pop up)

-Cant teleport,ride horse, or leave town after joining friends - #5 by DTMAce-1687

-Constantly Rubberbanding and Disconnecting on PC - #125 by DTMAce-1687

-Latency spikes game is unplayable - #3 by DTMAce-1687

-Major Lags and Rubber Banding on PC - #4 by DTMAce-1687

-https://us.forums.blizzard.com/en/d4/t/diablo-4-ps5-lagging/39800

-Can we PLEASE get some information on all of the latency issues and rubberbanding?! - #33 by DTMAce-1687

-Severe lag & rubber banding - #15 by DTMAce-1687

-Please either fix your servers or enable offline play

-Game causes home network to crash - #90 by DTMAce-1687

-Massive lag spikes going on in game right now

-PC Latency issues ONLY DIABLO NO OTHER GAME

-What's the deal with latency? 1 gig ISP DL speeds, yet, quiet often 200+ latency to D4 servers

3 Likes

I have one that I put together for D3 years ago. It still applies and I have updated the links.


There are always a few posts about lag or connection issues, but when it is the servers we get hundreds of posts at once. It is pretty obvious that the game/Blizz ISP is suffering. However, if that is not going on then you may want to do some further troubleshooting to look at the whole path your data takes.

Feel free to read through this then post your results and someone can help you troubleshoot.

Here is a list of the usual culprits (not in order of frequency):

  • Home network issues/interference (PC, network card, router, modem, people downloading a lot of stuff)
  • Local ISP
  • Backbone Internet services (hardest to fix as you are not their customer nor is Blizz)
  • Blizzard’s ISP
  • Blizzard servers
  • DDOS attacks
  • Game graphics interactions that cause DCs
  • Hardware issues that can cause DCs, esp when interacting with the game.

Some Troubleshooting Steps to Try:

  • Power cycle your home network and PC. Yes, this is simple but a reboot fixes many things! https://us.battle.net/support/en/article/power-cycle-your-network-devices

  • Double check that all your cables are securely plugged in. They can come loose when you least expect it. (Cats, kids, tripping accidents)

  • If you are on wireless try connecting directly to the router via eithernet cable. If that works then you know it is your wireless connection or interference with it.

  • Try connecting directly to the modem instead of the router if yours is separate. If that works you know you have a router issue.

  • Try running the game in selective startup mode so that all other software is disabled (note antivirus will be off). Blizzard Support - Closing Background Applications If that works then you know some other software on your machine is causing the issue. The most common software issue is security software even if you don’t think so. MS updates can play havoc sometimes as well. Another culprit for crashes and DCs is overlays or Razor software.

  • Consider updating your network card drivers and router firmware. I had to update both to fix my own DC issue.

  • Do you share a connection where others are streaming or downloading things? That can sometimes cause issues.

  • Look for issues with the ISP. To do that you can run a WinMTR then post it here. Let it run for 10 mins or so at a time you are having issues. That captures all the packet and route data for your traffic to the servers. Blizzard Support - Running WinMTR

  • Some people find that a DNS flush helps. Blizzard Support - IP Release, Renew, and Flush DNS

Personally, I had to replace my modem to resolve my DC issue. The lag issues I had turned out to be Comcast when I did the network testing. Those were resolved when Comcast fixed their issue in my area. Here is the checklist I use when troubleshooting. If it is not a connection issue, I move on to graphics/game glitches.

Not sure if I did this right… I have Spectrum. No VPN. Everything was fine two days ago, now the lag spikes are constant and the game is unplayable. Thanks for your help
Edit* If I got another copy to play on console(I was already thinking about it) I would just have the same issue, right, if its something to do with my ISP?

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
SAX1V1R.lan - 0 412 412 0 0 1 0
cpe-66-69-112-1.satx.res.rr. com - 1 405 403 6 21 73 28
lag-62.snaptxwm02h.netops.charter. com - 2 397 393 17 43 219 31
lag-30.mcr12snaptxwm.netops.charter. com - 1 405 403 9 28 125 18
lag-23.mcr11snantxvy.netops.charter. com - 1 405 403 0 21 56 18
lag-23.rcr01dllatx37.netops.charter. com - 1 409 408 12 29 175 19
142.250.170.142 - 1 405 403 20 36 121 31
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
No response from host - 100 83 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

PATHPING
Tracing route to 40.230.170.34.bc.googleusercontent. com [34.170.230.40]
over a maximum of 30 hops:
0 DESKTOP-H7LQ22M.lan [192.168.1.132]
1 SAX1V1R.lan [192.168.1.1]
2 cpe-66-69-112-1.satx.res.rr. com [66.69.112.1]
3 lag-62.snaptxwm02h.netops.charter. com [24.28.132.209]
4 lag-30.mcr12snaptxwm.netops.charter. com [24.175.33.116]
5 lag-23.mcr11snantxvy.netops.charter. com [24.175.32.184]
6 lag-23.rcr01dllatx37.netops.charter. com [24.175.32.146]
7 142.250.170.142
8 * * *
Computing statistics for 175 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-H7LQ22M.lan [192.168.1.132]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% SAX1V1R.lan [192.168.1.1]
0/ 100 = 0% |
2 21ms 0/ 100 = 0% 0/ 100 = 0% cpe-66-69-112-1.satx.res.rr. com [66.69.112.1]
0/ 100 = 0% |
3 44ms 2/ 100 = 2% 2/ 100 = 2% lag-62.snaptxwm02h.netops.charter. com [24.28.132.209]
0/ 100 = 0% |
4 26ms 15/ 100 = 15% 15/ 100 = 15% lag-30.mcr12snaptxwm.netops.charter. com [24.175.33.116]
0/ 100 = 0% |
5 23ms 8/ 100 = 8% 8/ 100 = 8% lag-23.mcr11snantxvy.netops.charter. com [24.175.32.184]
0/ 100 = 0% |
6 28ms 0/ 100 = 0% 0/ 100 = 0% lag-23.rcr01dllatx37.netops.charter. com [24.175.32.146]
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% 142.250.170.142

Trace complete.

1 Like

This has the worst packet loss of 2%

However if I’m reading the lines right on the second test, its showing up to a 15% loss as it goes through a couple of Charter’s IPs.

So the ISP may be causing your issues as well. Ugh. But thanks for the post! I appreciate the time taken!

1 Like

You did it correctly. Looks like the old roadrunner/Charter lines.

Your issues start

Those two hops show packet loss (the first number in bold). It is small, but would impact real time games like D4. Buffered things like video streaming would still be ok.

You can see similar results in your second test. Those packet loss issues are likely on your local ISP’s hardware.

1 Like

I appreciate the additional information, thank you.

I also ran the test, twice, just to be sure. And I was a bit, well… Shocked:

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.11.1 (my DSL Modem) 19 397 324 0 0 0 0
97-112-0-254.chcg.centurylink.net 1 680 679 44 49 81 48
chcg-agw1.inet.qwest.net 1 672 669 44 47 82 48
4.68.72.153 2 641 630 44 47 75 46
ae1.3501.edge3.Chicago10.level3.net 1 680 679 45 51 83 48
Google-level3-Chicago10.Level3.net 1 680 679 46 51 107 70
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0
No response from host 100 138 0 0 0 0 0

This has me a bit stumped, if I’m being honest. Not only is it showing a 19% loss at my modem, but the game is playing perfectly fine.

WTF.

I will be running more tests tonight, I need to narrow down if I have that done right or not. Got me scratching my head for sure.

1 Like

Yeah, that should not be playable with those results. Although with the networking setup you have I would wager it is a bit more complicated than average right?

You have a multi home setup vs most folks on a single home with multiple users.

I do. But not connected to it. I use this DSL modem for just gaming. My PC is literally the only thing connected to it, and its hardwired. And no other devices are on it.

1 Like
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
10.0.0.1 0 67 67 0 2 14 1
96.120.107.113 0 67 67 10 16 51 14
po-301-1203-rur01.newtowson.md.bad.comcast.net 0 67 67 9 18 51 10
96.216.81.57 0 67 67 12 20 51 20
be-31441-cs04.beaumeade.va.ibone.comcast.net 0 67 67 13 21 59 13
be-3407-pe07.ashburn.va.ibone.comcast.net 0 67 67 14 23 51 20
50.248.116.190 0 67 67 13 22 51 19
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0
No response from host 100 13 0 0 0 0 0

lags andrubber bands constantly on ps5 - every hour of every day, results from my pc playing w/ d3 literally right next to it

1 Like

Yeah, according to that, yours shows 0 issue.

I just re-ran mine on both my DSL (first) and then my multi-layered network with Starlink (second). I removed the extra no response servers, no help there anyway:

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.11.1 DSL Modem 0 320 320 0 0 0 0
97-112-0-254.chcg.centurylink.net 0 320 320 45 47 56 46
chcg-agw1.inet.qwest.net 0 320 320 44 46 76 46
4.68.72.153 1 312 310 44 46 52 45
ae1.3501.edge3.Chicago10.level3.net 1 316 315 45 49 83 59
Google-level3-Chicago10.Level3.net 0 320 320 46 50 93 92
No response from host 100 65 0 0 0 0 0
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
195.165.35.1 AX6000 0 311 311 0 0 1 0
192.168.0.1 ER605 0 311 311 1 1 1 1
169.254.11.21 0 311 311 1 1 2 1
192.168.1.1 0 311 311 1 1 3 2
100.64.0.1 2 296 292 22 55 218 66
172.16.250.66 2 292 287 23 55 101 76
undefined.hostname.localhost 2 292 287 23 55 101 76
undefined.hostname.localhost 3 288 282 21 53 108 62
142.250.170.202 2 296 292 25 54 218 66
No response from host 100 63 0 0 0 0 0

Apparently I ran it wrong the first time above. The Starlink is much faster speed, but has 3 households worth of traffic, and is multi-layered. The first two hops are here before it gets to the ISP. The first one on DSL is just the modem and the PC by themselves.

But overall they both look decent. I do have issues with some fringe tree blockage on Starlink and that causes me issues, which is why I game from the DSL line.

Who’s next?

Your data looks great, but it skips some key steps in the pathway - the console and any authentication and routing that are done by Playstation. It means your pathway using the two devices is not going to be the same.

BUT it does rule out your basic internet hardware and the PC route as being part of the issue.

1 Like

Would this issue be possibly resolved if I changed ISP?
@DTMAce if you know too.

Maybe… but a lot of times a different ISP uses many of the same hardware lines, so it depends. Your ISP may also be able to fix their issues if they know about them.

Something easy to try is a VPN. A VPN routes your data differently around possible “traffic jams”. So while the starting point and the end point are the same, it takes you on a detour.

That may help, depending on how close to home your issues really are.

1 Like

As MissCheetah said, maybe.

Keep in mind too, VPNs can add latency to your connection, but its not a bad suggestion as it might help.

I thought I’d add my results in this thread too, to try and make it easier for everyone to view. No VPN active. Have got the same results on my mobile/cell phone internet also (different ISP to the results below).

Host IP: 34.116.85.89 (Australian server)
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                               VX420-G2H -    0 |  184 |  184 |    1 |    2 |   20 |    2 |
|                              10.20.20.2 -    0 |  184 |  184 |    9 |   11 |   41 |   11 |
|      adl-apt-pir-crt1-be200.tpgi.com.au -    0 |  184 |  184 |   22 |   25 |   49 |   23 |
|       nme-sot-dry-crt1-be70.tpgi.com.au -    0 |  184 |  184 |   23 |   25 |   43 |   24 |
|          27-32-160-5.static.tpgi.com.au -    0 |  184 |  184 |   22 |   24 |   42 |   24 |
|                             72.14.213.0 -    0 |  184 |  184 |   23 |   25 |   49 |   25 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   38 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Tracert to 34.116.85.89 (Australia server)
-------------------------------------------
Tracing route to 89.85.116.34.bc.googleusercontent.com [34.116.85.89]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  VX420-G2H [192.168.1.1]
  2    11 ms    18 ms    11 ms  10.20.20.2
  3    23 ms    22 ms    23 ms  adl-apt-pir-crt1-be200.tpgi.com.au [203.219.182.65]
  4    25 ms    26 ms    25 ms  nme-sot-dry-crt1-be70.tpgi.com.au [203.219.107.189]
  5    23 ms    23 ms    23 ms  27-32-160-5.static.tpgi.com.au [27.32.160.5]
  6    23 ms    24 ms    24 ms  72.14.213.0
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 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.
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   69 |   69 |    0 |    0 |    0 |    0 |
|                            96.120.24.89 -    0 |   69 |   69 |    9 |   16 |  162 |   16 |
|po-310-1252-rur102.romeoville.il.chicago.comcast.net -    0 |   69 |   69 |    9 |   14 |   19 |   16 |
|                          162.151.46.217 -    0 |   69 |   69 |   10 |   14 |   19 |   16 |
|                            68.87.231.93 -    0 |   69 |   69 |    9 |   14 |   19 |   16 |
|                            68.85.176.13 -   83 |   17 |    3 |    0 |   18 |   20 |   15 |
|                          96.216.150.114 -    0 |   69 |   69 |   11 |   17 |   61 |   18 |
|be-32241-cs24.350ecermak.il.ibone.comcast.net -    0 |   69 |   69 |   13 |   18 |   25 |   15 |
|be-2413-pe13.350ecermak.il.ibone.comcast.net -    0 |   69 |   69 |   12 |   17 |   22 |   19 |
|                            75.149.231.2 -    0 |   69 |   69 |   13 |   19 |   39 |   20 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   14 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

If this helps: After some testing, I found out that using ExitLag, the rubberbanding problem has gone down drastically, it still happens and it is still annoying as hell, but its a massive improvement.

Before, i literally would log into the game and after a 30 sec to a minute or so usually, the game would just lag out completely and remain stuck until I relogged or for a very long time.

Now, with Exitlag, interestingly, the game is mostly stable BUT I still have random disconnects, sometimes it works for 1-2 hours, sometimes 5 minutes, it has no consistency to when it happens but it KINDA seems it has something to do when changing zones which in turn also either changes server OR restarts your connection to it.

Another interesting thing is the connection crashes that happen now also give me a message of disconnect and I get put back in char select screen. Before using it, I was not getting any warning at all and the game just stopped connecting at some point.

My theory is either a. What OP said or b. Something sus happens when switching zones and reconnecting/changing server (which happens every single time you switch zone - which is A LOT btw) and its almost like a gamble of either “catching” so to speak a good connection or getting pulled out of the server.

Someone well versed in these things would definitely be able to do a lot more than I thou, so Ill leave this here for OP and anyone interested.

Both of your data sets look great. I don’t see any packet loss or latency on any of the hops. You only let it run for a short time though as I see only 184 total data packets sent. Feel free to run WinMTR for a good 10 mins or so when you are having issues if you want to do another check.

No packet loss there, but your worst latency on your modem/router device is 162 which is not great. Does not always mean an issue, but cycling your devices would not hurt.

THIS is not good. 83% packet loss on that Comcast hop would be enough to stop most internet functionality for you if that is reflective of an actual issue.

What I don’t see though is that packet loss continuing after that hop which usually means it is an issue with the hardware at that hop not responding accurately to the data request. When there is actual packet loss it usually shows up in the data results for every hop after the bad one.

In your case, I would probably cycle my local hardware, make sure nobody is doing massive downloads/streaming when I wanted to play, and consider using a VPN to see if routing around that Comcast hop helps. It may not matter if that is not actually an issue and is just non-responding hardware.

Neither of those things will cause harm, so can be worth trying if the issue persists.

Certainly possible. I don’t think Blizzard has explained how their zone tech is working and if that could cause DCs or not. It does not in other Blizzard games. They have instance servers, but those apply to dungeons and such, not the open world.

Issues zoning are more likely related to local drive and memory trying to load the new zone. At least in some cases. Does not mean the person has a bad computer. Just that it is not playing well with the game.

Could be, not sure tho, tried it on 2 pcs and one laptop all to the same connection, seems hardware does not affect it at all. Very weird how their connection works, when I did my WinMTR I had 0 packet loss and all was fine, then suddenly host fails to respond. At the same time Blizz servers still seem to be in order so it does not look like its them either ( not sure tho). Somewhere in the middle the connection breaks, I think OP might be on to something, not sure how all connects but it is weird to say the least.

When a server or server block does not respond at all it is usually security masking. It is configured not to respond to data requests. It is not really going into the abyss!

If you see it in the middle of a trace then check the data coming out the other side. If that is good, then it is configuration at that hop, not actual loss. Otherwise the data packets would not continue to be sent.

How Blizz is handling the actual server instances though, I have no idea. I have not personally had any DCs in D4, but maybe I am just lucky. Comcast East Coast.