Timeouts and Disconnects

Technical Support
Prev 1 3 4 5 10 Next
I literally can't stay in a game for more than 2 or 3 minutes without getting a 3007 disconnect. Sometimes the game is just hosed when I enter. As a hardcore character, this makes things absolutely unplayable.
01/21/2017 05:53 AMPosted by Discord
I literally can't stay in a game for more than 2 or 3 minutes without getting a 3007 disconnect. Sometimes the game is just hosed when I enter. As a hardcore character, this makes things absolutely unplayable.


Same here. Very stable entire past 3 seasons, but starting this morning only, within few seconds to at most 4-5 min, get constant 3007 disconnects.

FWIW - tried changing to 32bit client and no improvement.
01/20/2017 07:40 PMPosted by Mordrehl
Did somebody just buy a new block of IP's and forget to tell everyone to update the Geo tables? In either case I'm firmly convinced the problem is @ 37.244.5.33


Mordrehl,

Your last question first because it's the easiest. Yes, those IPs were recently acquired and have not been updated in most whois lookups. If you were actually going to Germany, your latency would be MUCH worse than the average of 75 MS you're seeing. Is there any way you can get us a test that actually shows the packet loss? As you can surely see from many of the tests in this thread, not everybody's issue is the same, here. We do monitor those ips which belong to us for issues, and tend to post about any major server side issues. There's no point in us having people troubleshoot if we're aware of a problem on our end that the troubleshooting will not resolve.

192.168.0.1 1 4 % 456 437 0 2 713 2
* 2 100 % 0 0 ∞ 0 0 0
96.34.26.125 3 4 % 449 431 9 12 692 10
96.34.25.148 4 3 % 448 431 11 23 685 18


Discord,

You've got the same situation many of the other users in this thread have. You're dropping large amounts of packets which result in a disconnect. The problem starts between your computer and your router.

If you're on wireless, swap to ethernet. Power cycle your connection, and if that fails, bypass your router.
Update - I took your advice and power cycled my computer, router, and fiber modem. Things have improved amazingly. Thank you. It's the first thing I'll try next time, if I encounter a similar problem again.
10.0.0.1 1 0 % 298 298 1 5 864 2
96.120.41.209 2 0 % 290 290 10 22 558 24
68.85.85.5 3 0 % 290 289 10 21 439 11
68.85.235.249 4 0 % 289 288 14 19 407 16
68.86.90.45 5 0 % 286 286 21 146 510 257
68.86.82.158 6 0 % 288 288 21 147 569 261
173.167.56.238 7 0 % 287 285 20 154 585 275
37.244.1.35 8 0 % 287 287 20 122 520 217
* 9 100 % 0 0 ∞ 0 0 0
37.244.0.103 10 0 % 272 272 73 84 585 82
24.105.30.129 11 0 % 272 271 73 83 568 79
1st one

192.168.1.1 1 0 % 250 250 0 0 6 0
10.11.96.1 2 0 % 247 247 6 11 30 12
100.127.41.66 3 0 % 247 247 7 19 32 28
172.22.51.92 4 0 % 246 246 9 15 26 10
68.1.0.242 5 0 % 246 246 13 15 40 15
70.191.61.6 6 100 % 126 0 ∞ 0 0 0
37.244.4.33 7 0 % 245 245 14 19 54 17
24.105.31.45 8 100 % 126 0 ∞ 0 0 0
24.105.31.48 9 100 % 126 0 ∞ 0 0 0
24.105.31.20 10 100 % 126 0 ∞ 0 0 0
37.244.0.103 11 0 % 231 231 77 80 99 82
24.105.30.129 12 0 % 230 230 78 85 111 85

2nd one
192.168.1.1 1 0 % 93 93 0 0 6 0
10.11.96.1 2 0 % 92 92 7 8 24 8
100.127.40.226 3 0 % 92 92 8 11 99 9
172.22.51.92 4 0 % 92 92 9 13 46 11
68.1.0.242 5 0 % 92 92 13 15 37 16
70.191.61.6 6 100 % 47 0 ∞ 0 0 0
37.244.4.33 7 0 % 91 91 14 15 30 15
24.105.31.13 8 100 % 47 0 ∞ 0 0 0
24.105.62.129 9 0 % 88 88 48 50 91 49
192.168.0.1 1 19 % 807 651 1 0 924 0
76.1.136.1 2 20 % 788 627 24 0 945 0
71.0.83.97 3 20 % 785 622 24 0 957 0
208.110.248.241 4 21 % 772 607 43 0 855 0
* 5 100 % 0 0 ∞ 0 0 0
67.14.28.222 6 100 % 486 0 ∞ 0 0 0
65.120.78.2 7 20 % 778 617 41 0 964 0
37.244.4.33 8 20 % 780 618 38 0 962 0
24.105.31.45 9 100 % 486 0 ∞ 0 0 0
24.105.31.48 10 100 % 484 0 ∞ 0 0 0
24.105.31.20 11 100 % 485 0 ∞ 0 0 0
37.244.0.103 12 22 % 741 575 112 0 389 0
24.105.30.129 13 22 % 740 576 115 0 793 0

This is what I get with the test. I know that I'm experiencing huge latency issues, and getting discontinued connections. I've reset my router multiple times, double checked to make sure that I'm up to date on all updates for my computer, I've also renewed my ipconfig. Not sure what to do next.
24.105.30.129:

192.168.1.1 1 0 % 14 14 0 2 5 5
60.52.75.206 2 0 % 14 14 7 7 11 7
* 3 100 % 0 0 ∞ 0 0 0
* 4 100 % 0 0 ∞ 0 0 0
* 5 100 % 0 0 ∞ 0 0 0
* 6 100 % 0 0 ∞ 0 0 0
* 7 100 % 0 0 ∞ 0 0 0
* 8 100 % 0 0 ∞ 0 0 0
* 9 100 % 0 0 ∞ 0 0 0
* 10 100 % 0 0 ∞ 0 0 0
* 11 100 % 0 0 ∞ 0 0 0
* 12 100 % 0 0 ∞ 0 0 0
* 13 100 % 0 0 ∞ 0 0 0
* 14 100 % 0 0 ∞ 0 0 0
* 15 100 % 0 0 ∞ 0 0 0


24.105.62.129:

192.168.1.1 1 0 % 8 8 1 1 8 1
60.52.75.214 2 0 % 7 7 7 7 8 8
* 3 100 % 0 0 ∞ 0 0 0
* 4 100 % 0 0 ∞ 0 0 0
* 5 100 % 0 0 ∞ 0 0 0
* 6 100 % 0 0 ∞ 0 0 0
* 7 100 % 0 0 ∞ 0 0 0
* 8 100 % 0 0 ∞ 0 0 0
* 9 100 % 0 0 ∞ 0 0 0

yesterday still able to play but now....
01/21/2017 06:25 AMPosted by Drakuloth
01/20/2017 07:40 PMPosted by Mordrehl
Did somebody just buy a new block of IP's and forget to tell everyone to update the Geo tables? In either case I'm firmly convinced the problem is @ 37.244.5.33


Mordrehl,

Your last question first because it's the easiest. Yes, those IPs were recently acquired and have not been updated in most whois lookups. If you were actually going to Germany, your latency would be MUCH worse than the average of 75 MS you're seeing. Is there any way you can get us a test that actually shows the packet loss? As you can surely see from many of the tests in this thread, not everybody's issue is the same, here. We do monitor those ips which belong to us for issues, and tend to post about any major server side issues. There's no point in us having people troubleshoot if we're aware of a problem on our end that the troubleshooting will not resolve.

[/quote]

I'll try and capture when a lag delay or disconnect happens. The problem with WinMTR is if you're constantly running it the amount of data it's captured over time will mask minor interuptions.
The situation has now gotten even worse - recap and new info:

-until this morning, my connection has been reliable and great (3+ seasons)
-starting this morning, constant 3007 disconnects from seconds to few minutes of starting game client

-now, after taking some hours off in hope problem resolved itself, and doing all suggested tasks (power cycle, bnet article on 3007 fixes, etc), can't even type in clan chat.

-can view clan page, but typing in clan chat goes into limbo, it's as if I can't connect to the chat server

-also, even looking up leaderboards in game now I get 3006 disconnects

-bottom line, went from this morning being able to login and play few minutes before 3007 disconnect, to now can't even type in clan chat or lookup in-game services like leaderboards.

Please tell me Bliz has realized something changed today, perhaps with the new IPs they put in, and it is affecting players who had zero connection issues before.
Disconnect issues have gotten worse. Not only constant 3007 disconnect within seconds to few minutes of new game session, but now can't even type in clan chat or lookup leaderboards.

Get a 3006 looking up leaderboards, and clan chat goes into limbo, as if cant connect to chat servers.

Perhaps related to new IPs bliz deployed, perhaps nothing to do with it. But clearly, something changed this morning. Was absolutely fine last night + all 3 seasons prior of play.

Only this morning, and only for connection to D3 is my connection unstable. Same computer, same ISP, all other online games the connection is fine - just as it was with D3 till this morning.
As requested, my WinMTR logs for constant 3007 disconnects starting this morning only (very stable connection for 3+ seasons, problem started only today)

Log#1 to IP 24.105.30.129
192.168.1.1 1 0 % 190 190 0 0 28 1
10.0.0.1 2 0 % 190 189 1 1 7 2
96.120.88.153 3 25 % 152 113 9 11 29 13
68.85.190.41 4 13 % 168 146 9 12 43 15
162.151.78.253 5 27 % 150 109 9 11 33 14
68.86.90.93 6 18 % 160 130 9 13 54 16
68.86.86.98 7 22 % 155 120 18 12 65 0
68.86.83.30 8 32 % 144 97 17 17 56 19
173.167.56.218 9 35 % 141 91 17 10 60 0
37.244.0.33 10 21 % 156 122 17 10 73 0
24.105.30.129 11 38 % 138 85 18 12 73 0

Log#2 to IP 24.105.62.129
192.168.1.1 1 0 % 130 130 0 0 3 1
10.0.0.1 2 0 % 130 130 1 1 2 1
96.120.88.153 3 23 % 105 80 9 12 63 14
68.85.190.41 4 8 % 119 109 9 11 42 14
162.151.78.253 5 23 % 105 80 9 12 77 13
68.86.90.93 6 25 % 104 78 10 16 41 26
68.86.86.98 7 34 % 97 64 17 20 80 21
68.86.83.26 8 17 % 110 91 17 8 66 0
173.167.56.218 9 30 % 100 70 17 10 64 0
37.244.0.33 10 34 % 97 64 17 8 78 0
* 11 100 % 0 0 ∞ 0 0 0
24.105.62.129 12 28 % 98 69 63 40 92 70
Been playing again since Christmas 2016 after 4 years of not touching this game. It was all good even right after the new patch. Even started a seasonal hero for S9. But, definitely something has changed since the last update last week and the constant disconnect is now frustrating.
I haven't been having to many issues except for this weekend. The problem seems to be in the usual spot for me unfortunately:
8.|-- be-10919-cr01.1601milehigh.co.ibone.comcast.net 90.0% 10 52.8 52.8 52.8 52.8 0.0

Usually when I get random disconnects its this particular place that shows random problems.
Getting frequent spike and disconnection like others also...
Area: Malaysia
Region: America
Server pool: Aus
Yes. I'm getting the same problem about 10 hours ago. I gave up yesterday and I went to sleep. The problem is still not solve yet. I'm getting latency of more than 2000ms every 10 minutes and sometimes I'll be disconnected from the server.
I was able to play season 9 properly even while getting ping in the 300. But the past 2 days its unplayable with my ping over 2000. When I'm in the town, the ping constantly changing from green to yellow and then to red while doing nothing.

I have no issue with any of other Blizzard game, only DIABLO.

I have done all standard advice that you tell us to do and still having the issue. I have also reduced my graphics setting and audio and changed to 32bit.

Join the Conversation

Return to Forum