Every 5-30 minutes I get "connection interrupted"

While I appreciate you’re trying to be helpful, I need to correct this misconception here to make sure we’re all looking at the same thing. The 100% there is indeed not a problem, it’s just DDoS mitigation. The problem I’m referring to is the one right after the router for this specific player’s test.

I’m referring to the 1% at the beginning. Diablo II Resurrected has anticheat software running that is going to be more suspicious of lower levels of packet loss than other games. If these packets are being dropped in succession, the information we get when we re request the packets may end up garbled. That can cause a disconnect and the 1% loss here describes the issue going on.

As for the IP issue, that’s on the radar and we’re looking into what we can do to get it updated, so the feedback on that is helpful. In the mean time using any of our authentication IP addresses from our other games can catch local issues, which is what we’re looking for here since we’re currently not seeing mass issues. If that changes, we’ll create a thread for specific ISPs having problems/etc.

This is a real issue and it’s not on our ends. If you have anti-cheat software that is running a faulty algorithm, preventing non-cheating players from being able to stay in the game, then this is an issue you guys need to identify, address honestly, and fix.

I tried multiple dozens of times to complete the Den of Evil quest. My assassin is almost level 6 and still hasn’t successfully cleared the cave before the DC happened. I was so excited to enjoy the remaster of this legendary game, as I have with the Starcraft Remaster and WoW Classic.

Please take our feedback to the QA teams and Engineers and understand that the problem is NOT our routers, even if the signals from our routers are triggering your system to disconnect us. We just want to play the game (online) with the updated art.

For now I have requested a refund so the execs notice and put the pressure on for a real fix.

5 Likes

so you’re saying ONLY DIABLO 2 RESURRECTED requires me to get a new modem? No other game on my PC or any system requires it, but THIS ONE remaster does? Come on man.
What a joke.

2 Likes

If 1% packet loss (or even single-digit packet loss, tbh) is enough to cause me to get disconnected that is a major flaw in the fault tolerance of the design. I have sunk hundreds of hours into D3 and OW and have had more disconnections in < 10 hours of D2R than the entirely of playtime in those games. If this is truly “working as designed” I don’t think I have a choice but to refund, unfortunately.

2 Likes

Endeavor,

I’ve given you the best information I can with the information you provided. If you have feedback you can submit that at #general-discussion but this isn’t unique behavior among our games when packet loss like this exists. Not all of them will exhibit this behavior but if you time out like this due to packet loss, we aren’t surprised when players disconnect.

If you get the packet loss fixed we are more than happy to look into more options but until that’s done I can’t provide any more information for you. It’s always possible it’s a false positive, but if you don’t resolve it I can’t rule it out which means further troubleshooting or investigation is meaningless on our end.

Really disappointed to hear that.

It seems that something has been fixed because the issue is no longer happening.

(I had actually bought 2 copies so I can invite friends over to play and tested with my 2nd account :sweat_smile:)

1 Like

every 5 mins dc or crash

been playing ffxiv for 1000h last 6 months, no dc’s, no lag, no crashes

guess it’s our network guys, right?

seems as though something was fixed on your end because several of us can play now but cannot host games. hmmmmm?

The only thing we fixed recently was players getting stuck online. Seems like correlation =/= causation here. Keep in mind if it is an ISP issue it can come and go based on whether or not internet maintenance was done in your area or the time of day. Again, if the issue comes back and the packet loss goes away you can feel free to reach out here or via ticket for more help.

in-game ping jumping from 47 to 574 and 62 to 250

when I not ‘tried’ to play today I also pinged with cmd several none blizzard ip’s (with /t) for long periods, no ping spikes, no packet loss, no problems

Dear Drakuloth,

I ran this test and posted the log here Connection interrupted I hope you can look at it.

Thanks.

I’m trying to decide whether or not to refund the game, so can I just confirm – it is Blizzard’s position that permanently disconnecting users when they encounter a small amount of packet loss, or very brief ISP connectivity issues, with no way to resume the game, is “working as designed”?

I requested a refund sadly. I provided the logs with 0 packet loss multiple times just to be ignored. I tagged Drakuloth several times on this post just to be ignored.

Just been reading this thread and especially the blue posts…

Im amazed blizzard isnt taking responsibility towards all these customers including myself.

There has to be hundreds of posts per day of different players having the same problem.

Its getting close to unplayable for myself really and there’s many more bugs that need to be adressed.

Please try harder.

Since the release I am also experiencing random disconnects, which is so frustrating.

I am one of the affected ones. I play multiple games online and get no disconnects or lag or anything noticeable… I played D2R beta and except for the known server issues, I didn’t get this random disconnect I am getting every couple of minutes now. Nothing’s changed, you need to fix this Blizzard… Make the re-connections more resilient please.

I can confirm the game disconnects after my gateway (router) is unable to respond to my ping command one or two times within a short time window:

ping 192.168.0.1 -n 50000

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64`

Leave it running and see if there’re timeouts, which coincide with D2R disconnects.

I still believe that early disconnects are a terrible game experience, and need to be addressed by Blizzard. WiFi may drop, ISP may black-out for 1 sec, things happen on home networks. I don’t understand why this is the only game I play where this isn’t more leniently handled.

1 Like

I remember the tracert command back in the day from Diablo III launch. However Blizzard employees suggest using the following:

https://eu.battle.net/support/en/article/27780

I am also getting random disconnects.

All my other online games run fine. This is an issue with D2.

1 Like