Timeouts and Disconnects

Technical Support
Prev 1 6 7 8 10 Next
01/24/2017 08:28 AMPosted by Eloemaz
Hey all,

Looking over the resent reports in this thread looks like most of you are in Malaysia or Australia. The connection test I have seen post are to the North American servers. If you are player in the Americas region the server, you would want to do the test to are the ones located in Australia. To help out find what may be the common cause here please run a WinMTR to the Australian server IP address 103.4.115.248.

WinMTR
    1) Download WinMTR - http://winmtr.net/download-winmtr/
    2) Unzip the WinMTR.zip file to the Desktop.
    3) Open the WinMTR folder and select the one corresponds to your version of Windows (32 or 64 bit version).
    4) Run the WinMTR.exe
    5) Type the IP address 103.4.115.248 in the "Host" field
    6) Click on "Start" while playing
    & Run for at least 10 minutes then click on "Stop" in WinMTR
    7) Click on "Export text" and save to a text file.
    8) Copy and paste the contents of whole file here.
    9) Click on "Start"
    10) Run for 10 minutes then click on "Stop" in WinMTR
    11) Click on "Export text" and save to a text file.
    12) Copy and paste the contents of whole file here.


I am in the Midwest in the USA and I had never had the timeout problem like this .Before the most recent patch I had not had a timeout at ALL in over a year.Of course I don't play as much as a lot of players because I am 61 and disabled......my legs and back do not allow for a long session very often.The timeouts occur between 22 and 32 minutes of play time without exception so far.
01/24/2017 08:28 AMPosted by Eloemaz
Hey all,

Looking over the resent reports in this thread looks like most of you are in Malaysia or Australia. The connection test I have seen post are to the North American servers. If you are player in the Americas region the server, you would want to do the test to are the ones located in Australia. To help out find what may be the common cause here please run a WinMTR to the Australian server IP address 103.4.115.248.

WinMTR
    1) Download WinMTR - http://winmtr.net/download-winmtr/
    2) Unzip the WinMTR.zip file to the Desktop.
    3) Open the WinMTR folder and select the one corresponds to your version of Windows (32 or 64 bit version).
    4) Run the WinMTR.exe
    5) Type the IP address 103.4.115.248 in the "Host" field
    6) Click on "Start" while playing
    & Run for at least 10 minutes then click on "Stop" in WinMTR
    7) Click on "Export text" and save to a text file.
    8) Copy and paste the contents of whole file here.
    9) Click on "Start"
    10) Run for 10 minutes then click on "Stop" in WinMTR
    11) Click on "Export text" and save to a text file.
    12) Copy and paste the contents of whole file here.


While playing D3
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.88.1 - 0 | 706 | 706 | 1 | 2 | 18 | 5 |

| 60.52.74.110 - 0 | 706 | 706 | 3 | 7 | 137 | 6 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 142 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

-----------------------------------------

Not playing D3
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.88.1 - 0 | 711 | 711 | 1 | 1 | 22 | 1 |

| 60.52.74.110 - 1 | 707 | 706 | 3 | 14 | 139 | 22 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 143 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Using pingplotter to check connection to AUS server and here is the result

http://imageshack.com/a/img921/4026/j7WqNM.png

You can see from the image that telstraglobal.net has packet loss.
I just noticed something.....don't know if it means anything or not.After the game freezes I task manager out of it and the window shows that Diablo 3 Retail is running but,Diablo 3 is not.Those 2 entries are separate from the Battlenet entry.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| l7router - 0 | 1029 | 1029 | 0 | 0 | 6 | 1 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 222 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 221 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Amazing, I get the server timed out code(it seems like everyone else). I live in Colorado USA and the server says that it is Americas. But the devs are saying that its the computers fault? Its truly sounding like this last patch is the problem and Blizzard is refusing to take responsibility.
192.168.1.1 1 0 % 300 300 0 0 15 0
192.168.0.1 2 0 % 299 299 0 0 118 0
174.115.72.1 3 0 % 296 296 7 13 51 13
67.231.222.233 4 100 % 151 0 ∞ 0 0 0
209.148.232.37 5 100 % 151 0 ∞ 0 0 0
64.71.241.110 6 100 % 151 0 ∞ 0 0 0
206.126.237.174 7 100 % 151 0 ∞ 0 0 0
37.244.4.33 8 0 % 291 291 22 24 54 24
24.105.31.45 9 100 % 150 0 ∞ 0 0 0
24.105.31.48 10 100 % 150 0 ∞ 0 0 0
24.105.31.20 11 100 % 150 0 ∞ 0 0 0
37.244.0.103 12 0 % 277 277 75 83 119 80
24.105.30.129 13 0 % 277 277 74 84 115 90
HELP ! I have been crashing also. In game play, my screen just freezes. Does anyone know what is going on and is it going to be repaired? Thank you.
Discardedsin,

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


Same here as many of the other tests - you've got packet loss between your computer or router. Judging by what you've done so far, you probably need to switch to a wired ethernet cable if you are on wifi. If not, you may need to replace the router as something is going very wrong either at your network card or router.

Jacozilla,

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


Starting here, right after your house, it looks like, there's a huge amount of packet loss in both tests. If you're still having problems and did the troubleshooting you mentioned in your post, you want to reach out to your ISP.
For the folks in Malaysia,

Can we get a copy of a Looking Glass test? This runs a trace from our servers to your house and can bypass a lot of ICMP restrictions.

1. Go to the link for Looking Glass
2. Change "Select the Service" to Diablo III
3. Make sure all three of the boxes for "Select the Tests" are checked
4. Click "Run Test"
5. Click the "Copy Result to Clipboard" button at the top of the Test Result box
6. Paste it in your next post.

NOTE: this is only for the Malaysian users right now. If you have this problem in other areas of the world, we do need winMTRs run while the issue happens to try to identify the problem. Not all of these are ISP issues, but this test can help us identify the problem when it is.

It appears that as Zephyrous said most of these MTR tests are failing because the ICMP is blocked at the router or ISP level. There is no built in way to do a TCP traceroute on Windows, unfortunately, and the only way I'm aware of involves installing frameworks and third party utilities. We may ask some of you to do this in future posts, but for now I'd like to see what the path going from us to you looks like using the utility above.
01/14/2017 07:57 AMPosted by Drakuloth
Heya,

I'd make sure your [url="https://www.battle.net/support/article/31024?utm_source=internal-TechForum&utm_medium=posting&utm_campaign=BlizzardCS&utm_content=solution"]windows and network drivers are up to date[/url] first and foremost. It's a quick check and can help with connection stability, since our games tend to be somewhat more sensitive to lost packets than most of what you'd do with your internet connection. If you're on wifi, that's another major cause of disconnections or spiking latency. I'd recommend seeing if you can get closer to the router, and if even that doesn't work, snagging an ethernet cable and testing on that type of connection instead.

Should that fail, let's get a connection test and see if there's anything glaring on the path between your house and our servers. Your data has different 'roads' it follows through the internet depending on where it's going. It's possible there's a problem on one of those roads (kind of like a traffic jam) on the way to our game servers specifically.

1. Go to the [url="https://winmtrnet.codeplex.com/"]WinMTR.NET site[/url] and download the file from the right hand side of the page. (The purple button.)
2. Double click WinMTR.NET file in your download folder
3. Enter the following in the "Host" blank:
24.105.30.129
4. Click Start and let the test run for 5-10 minutes while playing. You want to make sure you capture some trouble with your connection during this time period, so if you don't have problems for 10 minutes or so (maybe a couple GRifts), just click Stop, then Start to restart the test and keep playing.
5. Click Stop
6. Click Copy text to clipboard
7. Paste your WinMTR test on your next post.
8. Repeat steps 3-7 for the IP 24.105.62.129

I'll check those out and look for 'traffic jams'


How is this happening all within a 12 hour period? Game has been running like a well tuned clock and then BAM.. every 15-25mins error3005..3007 for since lastnight? And it isn't just on one of my PCs. I can play other games and WoW just fine. It's only acting up when i play D3.
01/24/2017 12:30 PMPosted by PerusTC
01/24/2017 08:28 AMPosted by Eloemaz
Hey all,

Looking over the resent reports in this thread looks like most of you are in Malaysia or Australia. The connection test I have seen post are to the North American servers. If you are player in the Americas region the server, you would want to do the test to are the ones located in Australia. To help out find what may be the common cause here please run a WinMTR to the Australian server IP address 103.4.115.248.

WinMTR
    1) Download WinMTR - http://winmtr.net/download-winmtr/
    2) Unzip the WinMTR.zip file to the Desktop.
    3) Open the WinMTR folder and select the one corresponds to your version of Windows (32 or 64 bit version).
    4) Run the WinMTR.exe
    5) Type the IP address 103.4.115.248 in the "Host" field
    6) Click on "Start" while playing
    & Run for at least 10 minutes then click on "Stop" in WinMTR
    7) Click on "Export text" and save to a text file.
    8) Copy and paste the contents of whole file here.
    9) Click on "Start"
    10) Run for 10 minutes then click on "Stop" in WinMTR
    11) Click on "Export text" and save to a text file.
    12) Copy and paste the contents of whole file here.


I am in the Midwest in the USA and I had never had the timeout problem like this .Before the most recent patch I had not had a timeout at ALL in over a year.Of course I don't play as much as a lot of players because I am 61 and disabled......my legs and back do not allow for a long session very often.The timeouts occur between 22 and 32 minutes of play time without exception so far.


I am in Eastern USA.. SOOO It isn't a problem with Mal or Aus. This is happening everywhere that this game is available. It is an OBVIOUS PROBLEM with D3 (Blizzard)...and this recent patch. Timing tells ALL Blizzard!!... C'mon seriously?!
01/25/2017 08:41 AMPosted by Drakuloth
For the folks in Malaysia,

Can we get a copy of a Looking Glass test? This runs a trace from our servers to your house and can bypass a lot of ICMP restrictions.

1. Go to the link for [url="http://us-looking-glass.battle.net/"]Looking Glass[/url]
2. Change "Select the Service" to Diablo III
3. Make sure all three of the boxes for "Select the Tests" are checked
4. Click "Run Test"
5. Click the "Copy Result to Clipboard" button at the top of the Test Result box
6. Paste it in your next post.

NOTE: this is only for the Malaysian users right now. If you have this problem in other areas of the world, we do need winMTRs run while the issue happens to try to identify the problem. Not all of these are ISP issues, but this test can help us identify the problem when it is.

It appears that as [url="https://us.battle.net/forums/en/d3/topic/20752551066?page=6#post-119"]Zephyrous said[/url] most of these MTR tests are failing because the ICMP is blocked at the router or ISP level. There is no built in way to do a TCP traceroute on Windows, unfortunately, and the only way I'm aware of involves installing frameworks and third party utilities. We may ask some of you to do this in future posts, but for now I'd like to see what the path going from us to you looks like using the utility above.


Hi, Drakuloth;

PING:
PING 175.136.59.145 (175.136.59.145) 56(84) bytes of data.
64 bytes from 175.136.59.145: icmp_seq=1 ttl=55 time=263 ms
64 bytes from 175.136.59.145: icmp_seq=2 ttl=55 time=265 ms
64 bytes from 175.136.59.145: icmp_seq=3 ttl=55 time=262 ms
64 bytes from 175.136.59.145: icmp_seq=4 ttl=55 time=263 ms

--- 175.136.59.145 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 262.241/263.534/265.137/1.162 ms

25/01/2017 21:15:14 UTC
--------------------

TRACEROUTE:
traceroute to 175.136.59.145 (175.136.59.145), 15 hops max, 60 byte packets
1 24.105.30.2 (24.105.30.2) 1.049 ms 1.013 ms 1.319 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 1.202 ms 1.272 ms 1.307 ms
4 24.105.31.21 (24.105.31.21) 62.725 ms 62.772 ms 62.821 ms
5 24.105.31.49 (24.105.31.49) 62.739 ms 62.788 ms 62.845 ms
6 24.105.31.44 (24.105.31.44) 62.664 ms 62.447 ms 62.506 ms
7 37.244.4.32 (37.244.4.32) 62.530 ms 62.627 ms 62.700 ms
8 equinix.ash.cw.net (206.126.236.73) 62.403 ms 70.377 ms 70.407 ms
9 ae0-xcr2.ash.cw.net (195.2.30.46) 62.623 ms 62.651 ms 62.697 ms
10 xe-8-2-0-xcr1.lax.cw.net (195.2.30.246) 118.305 ms 118.309 ms 118.316 ms
11 vodafoneindia-gw.lax.cw.net (195.2.7.118) 250.088 ms 250.143 ms 250.128 ms
12 * * *
13 175.137.110.50 (175.137.110.50) 246.215 ms 246.174 ms 246.510 ms
14 175.136.59.145 (175.136.59.145) 262.527 ms 263.368 ms 263.453 ms

25/01/2017 21:15:14 UTC
--------------------

MTR:
Start: Wed Jan 25 21:15:14 2017
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.30.2 0.0% 10 0.8 1.5 0.5 5.7 1.5
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 37.244.0.102 0.0% 10 1.3 1.2 1.2 1.3 0.0
4.|-- 24.105.31.21 0.0% 10 62.7 62.6 62.6 62.7 0.0
5.|-- 24.105.31.49 0.0% 10 62.6 62.9 62.6 64.8 0.5
6.|-- 24.105.31.44 0.0% 10 64.7 62.9 62.5 64.7 0.6
7.|-- 37.244.4.32 0.0% 10 62.6 62.6 62.5 62.6 0.0
8.|-- equinix.ash.cw.net 0.0% 10 62.2 64.4 62.2 78.8 5.3
9.|-- ae0-xcr2.ash.cw.net 0.0% 10 62.5 63.2 62.4 66.7 1.3
10.|-- xe-8-2-0-xcr1.lax.cw.net 0.0% 10 118.4 121.3 118.4 144.9 8.3
11.|-- vodafoneindia-gw.lax.cw.net 0.0% 10 250.1 250.5 250.1 252.3 0.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- 175.137.110.50 0.0% 10 246.5 246.9 243.7 254.1 2.8
14.|-- 175.136.59.145 0.0% 10 262.1 262.9 262.1 263.6 0.0

25/01/2017 21:15:14 UTC
--------------------
Dear Blizzard,I am aware that problems can arise with routers,ISP's,connections etc.But,to infer that routers ALL over the globe are timing out at the same time is irresponsible.Taking into consideration that said connections are provided by 100's of different providers and manufacturers of routers it is really strange of you to take this position given the proven track record of REALLY caring about your customers.
I personally use a direct wired connection that was working fine until 2 days ago when my Diablo updater showed a 30-60MB(can't remember the exact size as I didn't watch it closely) download AFTER the Season patch.Then a major StarCraft 2 update was installed as well.My freezes come between 22-32 minutes of gameplay.This problem is NOT local to users.Thank you
01/25/2017 08:41 AMPosted by Drakuloth
For the folks in Malaysia,

Can we get a copy of a Looking Glass test? This runs a trace from our servers to your house and can bypass a lot of ICMP restrictions.

1. Go to the link for [url="http://us-looking-glass.battle.net/"]Looking Glass[/url]
2. Change "Select the Service" to Diablo III
3. Make sure all three of the boxes for "Select the Tests" are checked
4. Click "Run Test"
5. Click the "Copy Result to Clipboard" button at the top of the Test Result box
6. Paste it in your next post.

NOTE: this is only for the Malaysian users right now. If you have this problem in other areas of the world, we do need winMTRs run while the issue happens to try to identify the problem. Not all of these are ISP issues, but this test can help us identify the problem when it is.

It appears that as [url="https://us.battle.net/forums/en/d3/topic/20752551066?page=6#post-119"]Zephyrous said[/url] most of these MTR tests are failing because the ICMP is blocked at the router or ISP level. There is no built in way to do a TCP traceroute on Windows, unfortunately, and the only way I'm aware of involves installing frameworks and third party utilities. We may ask some of you to do this in future posts, but for now I'd like to see what the path going from us to you looks like using the utility above.


--------------------------------------------------------------

TRACEROUTE:
traceroute to 175.142.243.218 (175.142.243.218), 15 hops max, 60 byte packets
1 24.105.30.2 (24.105.30.2) 1.030 ms 1.062 ms 1.062 ms
2 * * *
3 37.244.0.100 (37.244.0.100) 1.293 ms 1.348 ms 1.410 ms
4 24.105.31.53 (24.105.31.53) 66.882 ms 66.938 ms 66.992 ms
5 24.105.31.12 (24.105.31.12) 66.869 ms 67.005 ms 67.082 ms
6 37.244.4.32 (37.244.4.32) 66.775 ms 66.684 ms 66.741 ms
7 equinix.ash.cw.net (206.126.236.73) 66.412 ms 66.444 ms 66.447 ms
8 ae0-xcr2.ash.cw.net (195.2.30.46) 131.932 ms 134.490 ms 134.585 ms
9 xe-11-2-1-xcr1.chg.cw.net (195.2.28.42) 83.191 ms 83.213 ms 83.217 ms
10 xe-4-2-0-xcr1.lax.cw.net (195.2.30.21) 139.778 ms 139.731 ms 137.199 ms
11 telecom-malaysia-gw.lax.cw.net (195.2.7.94) 294.881 ms 294.915 ms 294.928 ms
12 * * *
13 60.52.74.98 (60.52.74.98) 243.745 ms 247.803 ms 238.110 ms
14 * * *
15 * * *

26/01/2017 08:21:46 UTC
--------------------

PING:
PING 175.142.243.218 (175.142.243.218) 56(84) bytes of data.

--- 175.142.243.218 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

26/01/2017 08:21:46 UTC
--------------------

MTR:
Start: Thu Jan 26 08:21:46 2017
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.30.2 0.0% 10 1.1 0.7 0.5 1.1 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 37.244.0.100 0.0% 10 1.4 1.3 1.2 1.4 0.0
4.|-- 24.105.31.53 0.0% 10 66.8 66.9 66.8 67.0 0.0
5.|-- 24.105.31.12 0.0% 10 66.9 67.0 66.9 67.0 0.0
6.|-- 37.244.4.32 0.0% 10 66.9 66.8 66.7 66.9 0.0
7.|-- equinix.ash.cw.net 0.0% 10 66.4 66.5 66.4 66.6 0.0
8.|-- ae0-xcr2.ash.cw.net 0.0% 10 123.5 123.7 123.3 124.7 0.3
9.|-- xe-11-2-1-xcr1.chg.cw.net 0.0% 10 81.5 81.5 81.2 82.6 0.3
10.|-- xe-4-2-0-xcr1.lax.cw.net 0.0% 10 127.9 129.0 127.9 134.6 2.4
11.|-- telecom-malaysia-gw.lax.cw.net 0.0% 10 286.5 299.6 286.5 366.7 28.3
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- 60.52.74.98 0.0% 10 246.4 255.9 237.5 308.0 21.6
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

26/01/2017 08:21:46 UTC
--------------------

I have posted this about 2 days before but here's a new MTR test anyway, done today.
Thank you for looking into this issue!
surprise surprise...minutes after I posted MTR test, I login and tadaaaaa, everything was working fine!!

Best gift for the CNY holidays ^^
aannnnd its back again, though not so bad as previously, lag is about ~600ms
Heya,

If this were happening with all players or a large number of players, we wouldn't be trying to troubleshoot a connection issue. I've done some digging and looked at our active users when these reports are coming in. There don't appear to be large numbers of players dropping when we're getting reports on this thread.

If you want information on whether or not a connection issue is a server issue, check out our Twitter around the time it happens. You can also keep an eye out for blue posts confirming issues when they arise.

We do our best to help correct all types of connection issues. The tests we're asking for are hopefully to help pinpoint the issue. Without them, unfortunately, there's not much we can do to help outside of providing basic troubleshooting steps.
Hi , I am also another player frm Malaysia. I have done every tweaking and even updated my video card.. and yet the fts is usually only 0-6. It's bad. It started happening this week.

PING:
PING 175.141.87.39 (175.141.87.39) 56(84) bytes of data.
64 bytes from 175.141.87.39: icmp_seq=1 ttl=56 time=340 ms
64 bytes from 175.141.87.39: icmp_seq=2 ttl=56 time=340 ms
64 bytes from 175.141.87.39: icmp_seq=3 ttl=56 time=340 ms
64 bytes from 175.141.87.39: icmp_seq=4 ttl=56 time=340 ms

--- 175.141.87.39 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 340.234/340.364/340.471/0.096 ms

26/01/2017 15:36:55 UTC
--------------------

TRACEROUTE:
traceroute to 175.141.87.39 (175.141.87.39), 15 hops max, 60 byte packets
1 24.105.30.2 (24.105.30.2) 0.777 ms 0.781 ms 0.794 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 1.242 ms 1.291 ms 1.342 ms
4 24.105.31.21 (24.105.31.21) 62.992 ms 63.100 ms 63.384 ms
5 24.105.31.49 (24.105.31.49) 62.682 ms 62.722 ms 62.788 ms
6 24.105.31.44 (24.105.31.44) 62.558 ms 62.510 ms 62.560 ms
7 37.244.4.32 (37.244.4.32) 62.483 ms 62.542 ms 62.595 ms
8 equinix.ash.cw.net (206.126.236.73) 62.129 ms 62.251 ms 62.238 ms
9 ae0-xcr2.ash.cw.net (195.2.30.46) 123.885 ms 123.845 ms 123.768 ms
10 xe-11-2-1-xcr1.chg.cw.net (195.2.28.42) 77.846 ms 78.707 ms 78.547 ms
11 xe-4-2-0-xcr1.lax.cw.net (195.2.30.21) 123.605 ms 123.629 ms 123.692 ms
12 telecom-malaysia-gw.lax.cw.net (195.2.7.94) 386.899 ms 386.932 ms 387.152 ms
13 175.141.87.39 (175.141.87.39) 339.497 ms 339.987 ms 340.077 ms

26/01/2017 15:36:55 UTC
--------------------

MTR:
Start: Thu Jan 26 15:36:55 2017
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.30.2 0.0% 10 0.5 0.6 0.5 0.8 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 37.244.0.102 0.0% 10 1.2 1.2 1.1 1.3 0.0
4.|-- 24.105.31.21 0.0% 10 62.7 62.7 62.6 62.7 0.0
5.|-- 24.105.31.49 0.0% 10 62.7 62.9 62.7 64.9 0.6
6.|-- 24.105.31.44 0.0% 10 62.8 62.7 62.6 63.4 0.0
7.|-- 37.244.4.32 0.0% 10 62.6 62.6 62.5 62.7 0.0
8.|-- equinix.ash.cw.net 0.0% 10 62.2 62.2 62.2 62.5 0.0
9.|-- ae0-xcr2.ash.cw.net 0.0% 10 125.2 124.1 123.9 125.2 0.3
10.|-- xe-11-2-1-xcr1.chg.cw.net 0.0% 10 77.1 77.0 77.0 77.1 0.0
11.|-- xe-4-2-0-xcr1.lax.cw.net 0.0% 10 123.6 123.7 123.6 123.7 0.0
12.|-- telecom-malaysia-gw.lax.cw.net 0.0% 10 387.0 387.3 386.9 387.5 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- 175.141.87.39 0.0% 10 340.7 340.3 340.0 340.7 0.0

26/01/2017 15:36:55 UTC
--------------------
Blizzard Mods,

I've been having nothing but disconnects within an hour of playing for days now. Weeks ago all was well, and it happened only once in awhile, but now its reoccurring all the time.

I've done all the trouble-shooting I know of: flush dns, shutdown, poweroff, and restart hardware, tested wi-fi signal strength, etc. etc.

* Please note: this is only happening when playing Blizzard online games like D3. I can play Guild Wars 2 w/o these issues. Why?

Here's what you asked for:

10.0.0.1 1 1 % 1241 1219 2 14 903 25
96.120.75.53 2 2 % 1223 1193 10 23 993 33
68.86.154.177 3 2 % 1222 1192 11 17 789 14
68.86.152.22 4 2 % 1221 1191 11 20 993 26
68.86.152.149 5 2 % 1218 1187 16 18 778 18
68.86.90.21 6 2 % 1214 1184 17 24 800 24
68.86.85.78 7 2 % 1214 1185 17 24 982 21
173.167.57.150 8 2 % 1214 1184 16 22 800 19
37.244.3.33 9 2 % 1214 1186 17 25 897 26
* 10 100 % 0 0 ∞ 0 0 0
* 11 100 % 0 0 ∞ 0 0 0
37.244.0.103 12 2 % 1139 1105 83 89 982 87
24.105.30.129 13 2 % 1139 1105 83 90 982 92

Join the Conversation

Return to Forum