Asia server extremely lag

Technical Support
Hi, asia server has been been extremely lag since last week. My physical location is in Malaysia and my latency is between 600 - 1200 ms. Then I tried Americas server and the latency I got is 200 something!
Hey AngrySushi,

Please run a path ping and trace route to the Diablo III servers and post the results so we can take a look at the connection. Since you are in Malaysia for the Americas servers you are likely playing on the server in Australia. Run the tests to the two IP addresses listed below for the servers.

Taiwan 210.242.235.6
Australia 103.4.115.248
Hi there, i am having high ping connecting to US server too. i am from Malaysia.
same here, from Malaysia, latency between 900- 1800... whats happening?
12/27/2016 09:05 AMPosted by ctash
same here, from Malaysia, latency between 900- 1800... whats happening?
bro, which part of Malaysia are you staying?
same issue - it keeps jumping from 300+ - 2000+ ms.
From Malaysia, KL area.

And I've just got one more conquest to do for S8 stash. not cool. :(
I facing the same issue too. Its really make me unhappy :( I cant play D3 smoothly.
Is it me or is the server really lagging? I am on KL, Malaysia and I am playing through the Americas server. I couldn't even get logged on long enough to move before it kicks me out again.. what is happening?
Same here I am having high ping connecting to US server. i am from Malaysia. Its really frustrated :((
11/21/2016 07:36 AMPosted by Eloemaz
Hey AngrySushi,

Please run a [url="https://us.battle.net/support/en/article/718"] path ping[/url] and [url="https://us.battle.net/support/en/article/7648"]trace route[/url] to the Diablo III servers and post the results so we can take a look at the connection. Since you are in Malaysia for the Americas servers you are likely playing on the server in Australia. Run the tests to the two IP addresses listed below for the servers.

Taiwan 210.242.235.6
Australia 103.4.115.248


Can you help?
We do want to help out improve the connection. To be able to help we do need to find out what is causing the increase the latency. Running the connection tests can help us find this out. Please do post a path ping and trace route.
Hello, I am also from KL playing on the Americas servers. For the past two days, D3 has been extremely laggy and I'm constantly losing connection to the network.

These are the results for the Australia servers

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms dsldevice.domain.name [192.168.0.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Tracing route to 103.4.115.248 over a maximum of 30 hops

0 Ranveer.domain.name [192.168.0.11]
1 dsldevice.domain.name [192.168.0.1]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Ranveer.domain.name [192.168.0.11]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% dsldevice.domain.name [192.168.0.1]

Trace complete.
Here is my pathping and traceroute

I'm in Australia, mostly happens during my afternoon and evening

Tracing route to 103.4.115.248 over a maximum of 30 hops

0 DESKTOP-PKCOG4A [192.168.8.100]
1 homerouter.cpe [192.168.8.1]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-PKCOG4A [192.168.8.100]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% homerouter.cpe [192.168.8.1]

Trace complete.
Tracing route to 103.4.115.248 over a maximum of 30 hops

1 2 ms 1 ms 1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 116 ms 32 ms 39 ms 172.24.193.9
4 * * * Request timed out.
5 50 ms 37 ms 39 ms 210.49.49.41
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 63 ms 59 ms 59 ms 59.154.142.46
11 55 ms 61 ms 59 ms 202.139.16.50
12 66 ms 59 ms 59 ms 27.111.251.114
13 55 ms 60 ms 66 ms 103.4.115.248

Trace complete. How can I fix this?
Hi Malaysia players,
There was another similar thread. https://us.battle.net/forums/en/d3/topic/20044677250
Two players' MTR log showed packet loss at Telekom Malaysia.
It is likely a problem at Malaysia ISP. Perhaps you should also contact your ISP to investigate.
12/28/2016 07:07 AMPosted by CottonBall
Can you help?

From my own personal notes:

Run a Pathping
1. Press Windows-key.
2. Type cmd.
3. Right click the Command Prompt shortcut and Run as Administrator.
4. Enter: pathping 24.105.30.129 > C:\pathping.txt
5. Allow pathping to complete.

Run a Traceroute

If the Command Window is still open (if not, repeat steps 1-3 above):

1. Enter: tracert 24.105.30.129 > C:\tracert.txt
2. Allow tracert to complete.
3. Close the Command Window.

Posting Pathping and Tracert in this thread
1. Open the pathping.txt file.
2. Copy the contents of the file.
3. Press Ctrl+V to paste the information in this thread's Reply Window.
4. Open the tracert.txt file.
5. Copy the contents of the file.
6. Press Ctrl+V to paste the information in this thread's Reply Window.
7. Click "Add Reply".

================================

Edit: Please note that the step-by-step instructions above list Host IP for the D3 Americas Region. You may need to change it for your Region:
    Americas 24.105.30.129
    Taiwan 210.242.235.6
    Australia 103.4.115.248
There you go

TRACEROUTE:
traceroute to 210.195.191.124 (210.195.191.124), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.502 ms 0.527 ms 0.799 ms
2 * * *
3 37.244.0.100 (37.244.0.100) 2.616 ms 2.658 ms 2.742 ms
4 * * *
5 * * *
6 37.244.4.32 (37.244.4.32) 66.342 ms 66.324 ms 66.321 ms
7 * * *
8 ae0-xcr2.ash.cw.net (195.2.30.46) 68.868 ms 68.683 ms 68.677 ms
9 xe-8-2-0-xcr1.lax.cw.net (195.2.30.246) 61.256 ms 61.266 ms 61.267 ms
10 telecom-malaysia-gw.lax.cw.net (195.2.7.94) 233.484 ms 231.379 ms 231.389 ms
11 210.195.191.124 (210.195.191.124) 235.207 ms 235.555 ms 234.938 ms

30/12/2016 13:45:34 UTC
--------------------

PING:
PING 210.195.191.124 (210.195.191.124) 56(84) bytes of data.
64 bytes from 210.195.191.124: icmp_seq=1 ttl=52 time=235 ms
64 bytes from 210.195.191.124: icmp_seq=2 ttl=52 time=234 ms
64 bytes from 210.195.191.124: icmp_seq=3 ttl=52 time=235 ms
64 bytes from 210.195.191.124: icmp_seq=4 ttl=52 time=235 ms

--- 210.195.191.124 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3234ms
rtt min/avg/max/mdev = 234.989/235.432/235.720/0.438 ms

30/12/2016 13:45:34 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.4 0.5 0.4 1.2 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.100 0.0% 10 2.6 2.6 2.5 2.8 0.1
4. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
5. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6. 37.244.4.32 0.0% 10 66.5 66.4 66.3 66.5 0.1
7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8. ae0-xcr2.ash.cw.net 0.0% 10 69.3 68.9 68.8 69.4 0.2
9. xe-8-2-0-xcr1.lax.cw.net 0.0% 10 61.3 61.5 61.3 62.7 0.4
10. telecom-malaysia-gw.lax.cw.net 0.0% 10 235.7 233.1 231.4 242.9 3.7
11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12. 210.195.191.124 10.0% 10 235.4 235.4 235.1 235.7 0.2

30/12/2016 13:45:34 UTC
--------------------
@CottonBall, thanks for you test result. Unfortunately, the servers seems have connection issues right now. That means your test was irrelevant.
Would you test again after Blizzard fixes the issue?
12/30/2016 06:46 AMPosted by Maskraider
@CottonBall, thanks for you test result. Unfortunately, the servers seems have connection issues right now. That means your test was irrelevant.
Would you test again after Blizzard fixes the issue?
@CottonBall, seems back to normal now. Please retest.
Playing on Americas server from Malaysia.
Entered a game with green ping 200-280, after a couple of minute, it jumps to 1800.

PATHPING:
Tracing route to 103.4.115.248 over a maximum of 30 hops

0 DESKTOP-EPR5B09 [192.168.1.2]
1 192.168.1.1
2 175.144.91.118
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-EPR5B09 [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% 175.144.91.118

Trace complete.

TRACERT :
Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 10 ms 10 ms 175.144.91.118
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
i am from Ampang part of KL, Malaysia and too having super high latency to NA server. In the afternoon it will be form 800-1400ms but at night its totally unplayable of more than 2000ms.

tracert:

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 2 ms 130 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

PATHPING:

Tracing route to 24.105.30.129 over a maximum of 30 hops

0 Adrian-PC [192.168.0.100]
1 192.168.0.1
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Adrian-PC [192.168.0.100]
2/ 100 = 2% |
1 13ms 2/ 100 = 2% 0/ 100 = 0% 192.168.0.1

Trace complete.

Join the Conversation

Return to Forum