Getting disconnected after a few minutes

Technical Support
1

I’m not able to play 15 minutes continuously and being kicked out because there was a connection issue.
I let the ping battle.net -t running and after playing for 5 min, I got disconnected. The brief “log” is below:
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=40ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=40ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=39ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=40ms TTL=50
Reply from 137.221.106.104: bytes=32 time=103ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=39ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=41ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=40ms TTL=50
Reply from 137.221.106.104: bytes=32 time=41ms TTL=50
Reply from 137.221.106.104: bytes=32 time=40ms TTL=50
Reply from 137.221.106.104: bytes=32 time=39ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=40ms TTL=50
Reply from 137.221.106.104: bytes=32 time=40ms TTL=50
Reply from 137.221.106.104: bytes=32 time=46ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=36ms TTL=50
Reply from 137.221.106.104: bytes=32 time=35ms TTL=50
Reply from 137.221.106.104: bytes=32 time=36ms TTL=50
Reply from 137.221.106.104: bytes=32 time=42ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Request timed out.
Request timed out.
Reply from 137.221.106.104: bytes=32 time=48ms TTL=50
Reply from 137.221.106.104: bytes=32 time=39ms TTL=50
Reply from 137.221.106.104: bytes=32 time=36ms TTL=50
Reply from 137.221.106.104: bytes=32 time=62ms TTL=50
Reply from 137.221.106.104: bytes=32 time=35ms TTL=50
Reply from 137.221.106.104: bytes=32 time=57ms TTL=50
Reply from 137.221.106.104: bytes=32 time=35ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=38ms TTL=50
Reply from 137.221.106.104: bytes=32 time=35ms TTL=50
Reply from 137.221.106.104: bytes=32 time=36ms TTL=50
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50
Reply from 137.221.106.104: bytes=32 time=44ms TTL=50
Reply from 137.221.106.104: bytes=32 time=35ms TTL=50
Reply from 137.221.106.104: bytes=32 time=34ms TTL=50
Reply from 137.221.106.104: bytes=32 time=34ms TTL=50
Request timed out.
Reply from 137.221.106.104: bytes=32 time=37ms TTL=50

I’m from US Central. Does anyone have the same issue?

2

It would have been nice to see what the final result was. It would show the % of loss.

However.

That doesn’t help ultimately, as the servers you play from are not the servers for battle.net.

The latter is more of a common hub for some of the log in and access portals. Each game has their own servers in different regions.

The problem with Diablo IV, is its a world wide concurrent server network. Meaning no sub divisions for regions. While they do have regional servers, the game in general is world wide and players can literally play in any region to access their characters. Unlike Diablo 3 for example, where you had specific regions you could play in and could in essence have several places to play the game like a new game or with different saves.

Bottom line, Diablo IV is a finicky beast when it comes to network reliability.

You can find more tools to test your connection with here:

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

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.