I'm also having this issue occur while playing. I felt like this has got to be an issue other players are having and saw that this topic is definitely being talked about. I flashed my router, checked firmware (its up to date), I'm wired to the router, have very stable internet and this is the only game where this occurs. I thought maybe if I didn't go to events (because this happens more often at them for me) but that is not the case, I can be fighting just a few monsters and the internet connection completely drops (router craps out). Hopefully there will be a fix. On a side note, this never happened during server slam.
I wanted to do a test on AMD computer. So I started to install it on that computer. Went to my main computer and started to play D3. I was getting a lot lag.
So I thought I restart everything. Well it didnāt help and saying to myself what hell is going on here. I never ever get lag. I thought maybe it is the other computer down loading the game. I have installed a lot games and never ever had a problem.
I said let me stop the download of the game and see what happens. Everything went back to normal. Started the download again and started have the same problem. Been doing this for about 40yrs and never ever see this happen.
It even cause problems on the internet with very low download speed too. On all of the other computers too.
This is partly why I think everyone is getting more and more instances of latency on those networks that did work. I think even the ISPs are starting to block the traffic.
I have several threads asking for more WinMTR reports. If anyone here would also do some that are having the issues, that would be great:
This also has some info that could be helpful/relate:
Iām going to run three WinMTR reports tonight with Diablo and Battle.net off and three with it on while I alt-tab and while I exit the game. I fully expect that it will show a ton of packet loss with the game running. Iāve run a few this morning with Diablo turned off and my connection to the ISP has been perfect.
Thank you. I look forward to seeing the results. The link to the WinMTR above has options to pick the IP address for Diablo IV servers according to region as well. Test more than one for your country.
The problem is we canāt even download the game. Canāt even run a test cause the ethernet crashes during the downloading process, otherwise I would happily contribute.
Good point. You can also use TraceRT to give some information related to this:
This doesnāt require the game to run. Not as detailed but may help identify some problems.
Either Blizzard fixed something during the downtime or Comcast made some sort of adjustment. I was not able to reproduce the issue last night. Iām going to monitor it for the next few days. I still have Comcast coming out this morning to check cabling and equipment. Happily, I was able to hop on for an hour last night without my home network being impacted!
I am having the same issue, to the point that the game is virtually unplayable. However the connection issues are intermittent. I will have a couple hours randomly where the game is playable, followed by 4-6 hours of the game constantly disconnecting me about 30 seconds after logging in with a character. No other game I play has any internet connection issues, and we have the highest tier of internet available for home purchase from xfinity in our area.
Well, if you can, run those two tests I have a few posts above (WinMTR and PathPing/TraceRT) for checking your connection.
The more of these I can gather, the more it helps us and hopefully Blizzard to fix whatever they can to help the problem too.
Iāve been having this problem since official launch day. Never during early access. Iād rather wait in a que than deal with this. Itās literally reproduceable using D4 and only D4. Takes down the whole network. Specifically the cable modem. My ISP came out last week. Signal levels are great. Guess what? I know a lot more about cable modem now. I can look myself. Beautiful levels.
Now, it does seem better during off peak hours like in the middle of the night, but it returns and with a vengeance most of the day. You get 15-45m at a time like people are saying then your cable modem restarts. A few times it just dropped me to like 2Mbit down with still a hefty up, but performance was abysmal. Restarting it manually fixes itā¦ Well, until you play D4 for a bit.
I have a new modem coming Saturday, but after reading this thread Iām not even going to bother hooking it up. Itās the same model I have, and I was thinking that if it doesnāt work Iāll get a fancy 3.1 model, but Iām pretty sure itās not going to matter. Itās the game.
I donāt understand how, but it is. Sometimes a player will come near me and my game goes nuts. It always flakes out worse and worse before the crash, but itās never butter smooth like it was in early access even when itās playable.
Is it possible that our IP addresses are easily exposed to hackers in this game and they are DDOS people constantly or maybe using some sort of lag switch to harass players?
It started again this evening. I didnāt have the time or patience to test both US Central and US West. Here is US Central the last time I tried to play:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| READYSHARE - 0 | 156 | 156 | 0 | 0 | 6 | 0 |
| 96.120.16.169 - 5 | 137 | 131 | 7 | 12 | 25 | 25 |
| ae-252-1252-rur102.tidwell.tx.houston.comcast.[net] - 7 | 129 | 121 | 7 | 15 | 77 | 51 |
| ae-2-rur101.tidwell.tx.houston.comcast.[net] - 6 | 129 | 122 | 7 | 15 | 71 | 13 |
| 96.110.152.65 - 7 | 129 | 121 | 7 | 11 | 26 | 26 |
| 68.85.245.201 - 8 | 124 | 115 | 8 | 12 | 28 | 28 |
| be-35421-cs02.dallas.tx.ibone.comcast.[net] - 8 | 125 | 116 | 13 | 18 | 36 | 31 |
| be-3201-pe01.1950stemmons.tx.ibone.comcast.[net] - 5 | 136 | 130 | 13 | 17 | 32 | 32 |
| 75.149.231.222 - 5 | 134 | 128 | 13 | 17 | 32 | 16 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
This was the 3rd time it disconnected my router from the ISP. Xfinity came out today and saw no issues. I know the WinMTR makes it look like the first hops are the issue, but this is ONLY happening when Diablo is running.
I did also run Wireshark the other night to see the flood of packets upon exit. I was getting over 4k packets per second when I quit the game. I tried to request a refund, but I know Blizzard wonāt do it. Such a PITA.
Just going to put the game down and come back when itās been fixed.
Yeah, I see you are getting enough loss to cause problems in the first few hops of your ISP.
That has been a common theme with the tests so far. I have also gotten some that have nearly no issues as well, and I even tested my own too, just to see how it fared.
So far, its acting like some ISPs donāt like the D4 traffic. Why I donāt know, but then why do some home modems also go nuts?
Its certainly frustrating.
The guy who came and checked my line suggested that a new cable to the house from the box might be needed, but now they wonāt come do it until I replace my modem.
That said, my levels are steady 36.
This happens to me too. But weirdly only when Iām playing with friends. I played today with my wife just me and her for like 5 hours. My buddy jumps on and we are running Dungeon with 3 and it knocks my hardlined connection off and my wifeās hardlined connection too.
It stays down for like 5 minutes (ISP wont let me back on) then it lets me re-join. this only happens with Diablo 4 because we also play Crab champions together and Darktide and its fine.
It does seem thereās something causing Diablo IV to spike your internet in a way that the ISP drops you. Which seems to be on Diabloās end because other games donāt do this. You might be able to mitigate it with that throttling method mentioned earlier but the symptoms seem closely aligned to your ISP getting triggered by something D4 is doing.
I want to be very clear that this ONLY happens when the Diablo application is running. If Iām not running the game, I have a super fast connection with virtually no packet loss along the way. Itās definitely a Diablo issue. Iām also wondering if ISPs are somehow flagging the comms as DDoS and forcing the modem to reconnect in some automated fashion.
I had a smooth experience between 1:30am-2:30am until I went to bed, but weāll see about during the day today.
Oh, Iām well aware. I donāt think I have indicated otherwise actually.
Okay!
The typical approach is to blame AWFUL netcode/Server behaviour on the customerā¦ I have had this happen myself in 2 titles so far out of hundredsā¦ World of Warships (very rare) and Diablo 4 (more often than i would consider normal in anyway)
Btw. Your reconnect routine FREEZES THE ENTIRE PC 1 out of 2 times and takes forever to come back to life and it will 0 times actually WORK . HORRIBLE . FIX YOUR GAME . (and your godawful VRAM memory leak). My router is absolutely fine btwā¦what happens is that this buggy mess SHOOTS DOWN the Windows 11 network stack completely.