Latency spikes

Technical Support
Hello,

WinMTR results:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 1 | 1878 | 1877 | 0 | 0 | 44 | 0 |
| livebox.home - 0 | 1883 | 1883 | 1 | 1 | 31 | 1 |
| No response from host - 100 | 378 | 0 | 0 | 0 | 0 | 0 |
|ae105-0.ncidf204.Paris13eArrondissement.francetelecom.net - 1 | 1879 | 1878 | 1 | 4 | 112 | 2 |
|ae41-0.niidf202.Paris15eArrondissement.francetelecom.net - 1 | 1879 | 1878 | 1 | 4 | 111 | 7 |
| 193.252.137.74 - 0 | 1883 | 1883 | 1 | 5 | 113 | 2 |
|hundredgige1-5-0-1.auvtr4.aubervilliers.opentransit.net - 0 | 1883 | 1883 | 2 | 8 | 109 | 4 |
| blizzard-1.gw.opentransit.net - 1 | 1879 | 1878 | 2 | 4 | 108 | 2 |
| ae1-br02-eqpa4.as57976.net - 0 | 1883 | 1883 | 13 | 20 | 253 | 14 |
| et-0-0-3-br02-eqam1.as57976.net - 2 | 1768 | 1745 | 16 | 60 | 4667 | 547 |
| et-0-0-67-pe02-eqam1.as57976.net - 0 | 1883 | 1883 | 13 | 15 | 113 | 13 |
| 137.221.66.45 - 0 | 1883 | 1883 | 13 | 15 | 115 | 14 |
| 185.60.112.158 - 0 | 1883 | 1883 | 13 | 15 | 112 | 14 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Seems like there is a problem on et-0-0-3-br02-eqam1.as57976.net
Seems some issues between your computer and router/modem.

I'd suggest you to try step #1 and #2 in this support article first:
https://us.battle.net/support/en/article/112206
Click the text in BLUE color for detailed procedures.

If problem continues, try other steps in that article.

If still continues, you may want your ISP to help investigation.
Done all steps https://us.battle.net/support/en/article/112206

latency 40-100msec normal then can spike to 1000-1800msec for the past week.
Play for 20-30 mins then random lag spike then back down, something normal for couple hours then spike. When lag spike ms after Chi to Lax also spikes

Issues looks like Chi - Lax via https://www.teliacarrier.com/Network-map.html

over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 12 ms 12 ms 12 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 13 ms 16 ms 12 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 37 ms 35 ms 40 ms toro-b1-link.telia.net [62.115.171.248]
5 24 ms 22 ms 22 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 38 ms 31 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 70 ms 70 ms 71 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 70 ms 70 ms 70 ms 137.221.65.132
9 71 ms 70 ms 70 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 70 ms 70 ms 70 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 71 ms 70 ms 71 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 70 ms 71 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 12 ms 12 ms 12 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 15 ms 13 ms 12 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 13 ms 12 ms 13 ms toro-b1-link.telia.net [62.115.171.248]
5 24 ms 23 ms 22 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 22 ms 23 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 70 ms 71 ms 72 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 71 ms 70 ms 70 ms 137.221.65.132
9 70 ms 71 ms 70 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 69 ms 70 ms 70 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 71 ms 71 ms 70 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 70 ms 69 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 13 ms 13 ms 12 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 13 ms 12 ms 13 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 13 ms 12 ms 13 ms toro-b1-link.telia.net [62.115.171.248]
5 22 ms 22 ms 23 ms chi-b21-link.telia.net [62.115.118.230]
6 22 ms 23 ms 23 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 70 ms 71 ms 71 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 71 ms 70 ms 70 ms 137.221.65.132
9 71 ms 124 ms 70 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 70 ms 70 ms 71 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 71 ms 71 ms 71 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 70 ms 70 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 20 ms 12 ms 12 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 12 ms 13 ms 12 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]

4 13 ms 12 ms 12 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 22 ms 23 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 23 ms 22 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 70 ms 70 ms 71 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 * * * Request timed out.
9 * 1467 ms 660 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 71 ms 71 ms 70 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 71 ms 72 ms 71 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 71 ms 70 ms 71 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 13 ms 12 ms 13 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 13 ms 13 ms 13 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 12 ms 12 ms 12 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 22 ms 22 ms chi-b21-link.telia.net [62.115.118.230]
6 22 ms 23 ms 23 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 170 ms 219 ms 219 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 70 ms 70 ms 70 ms 137.221.65.132
9 * * * Request timed out.
10 70 ms 70 ms 70 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 71 ms 72 ms 71 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 71 ms 70 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 13 ms 11 ms 12 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 14 ms 12 ms 12 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 12 ms 12 ms 13 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 23 ms 23 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 23 ms 22 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 70 ms 70 ms 70 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 71 ms 71 ms 70 ms 137.221.65.132
9 70 ms 70 ms 71 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 70 ms 70 ms 71 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 70 ms 72 ms 71 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 70 ms 70 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 12 ms 12 ms 13 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 17 ms 13 ms 13 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 13 ms 12 ms 13 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 23 ms 22 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 23 ms 22 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 71 ms 70 ms 70 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 87 ms 70 ms 70 ms 137.221.65.132
9 82 ms 70 ms 71 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 71 ms 71 ms 71 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 70 ms 71 ms 71 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 70 ms 69 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 12 ms 11 ms 13 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 32 ms 12 ms 12 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 13 ms 13 ms 13 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 22 ms 23 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 23 ms 23 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 75 ms 71 ms 71 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 70 ms 70 ms 70 ms 137.221.65.132
9 71 ms 71 ms 70 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 70 ms 69 ms 71 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 70 ms 71 ms 70 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 71 ms 71 ms 71 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 494 ms 39 ms 13 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 13 ms 12 ms 12 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 13 ms 12 ms 13 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 23 ms 23 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 23 ms 22 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 71 ms 70 ms 71 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 76 ms 71 ms 71 ms 137.221.65.132
9 70 ms 72 ms 71 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 70 ms 70 ms 70 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 677 ms 1345 ms 1484 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 70 ms 70 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 17 ms 12 ms 12 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 19 ms 14 ms 13 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 12 ms 14 ms 12 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 23 ms 23 ms chi-b21-link.telia.net [62.115.118.230]
6 23 ms 22 ms 23 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 86 ms 81 ms 99 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 71 ms 71 ms 71 ms 137.221.65.132
9 * * * Request timed out.
10 70 ms 70 ms 70 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 72 ms 70 ms 70 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 71 ms 70 ms 70 ms 24.105.29.40

Trace complete.

Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ControlPanel.Home [192.168.1.1]
2 12 ms 12 ms 12 ms lo0-0-lns04-tor.teksavvy.com [206.248.155.241]
3 12 ms 12 ms 12 ms ae0-2150-bdr01-tor.teksavvy.com [69.196.136.172]
4 17 ms 15 ms 12 ms toro-b1-link.telia.net [62.115.171.248]
5 23 ms 23 ms 23 ms chi-b21-link.telia.net [62.115.118.230]
6 22 ms 24 ms 23 ms blizzard-ic-322962-chi-b21.c.telia.net [213.248.
78.163]
7 71 ms 70 ms 70 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
8 70 ms 70 ms 70 ms 137.221.65.132
9 831 ms 1473 ms 1493 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
10 1501 ms 1658 ms 1896 ms be1-pe02-eqla1.as57976.net [137.221.68.69]
11 2272 ms 1421 ms 71 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
12 * * * Request timed out.
13 70 ms 70 ms 70 ms 24.105.29.40

Trace complete.
I also have this issue eqam1.as57976.net is dropping packets like it is turning down for what
07/03/2019 10:58 AMPosted by absol
I also have this issue eqam1.as57976.net is dropping packets like it is turning down for what
Those nodes are configured to de-prioritize ICMP packets. They are NOT an issue.
Please read full explanation from the support:
https://us.battle.net/forums/en/d3/topic/20771137533#post-4
03/08/2019 09:52 AMPosted by Jambrix
Hey DudleyDR,

The three nodes that you're referring to are indeed part of the Blizzard network, however they are not having problems. Our nodes are configured to de-prioritize ICMP packets (which are used by tracert, pathping, and WinMTR) so you may see large latency spikes due to this. It simply means that those nodes are delaying these connection tests packets, while your game packets (TCP and UDP) are getting through quickly and efficiently.

Knowing this, I can see that the WinMTR that you posted does not really show any real issues. What kind of issues are you experiencing in the game? What troubleshooting have you tried already? Have you tried using a different internet connection, like a mobile hotspot or even a VPN connection, to see if the issue goes away?
Lag spikes 200-500

TRACEROUTE:
traceroute to 210.195.195.18 (210.195.195.18), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.343 ms 0.337 ms 0.335 ms
2 24.105.18.131 (24.105.18.131) 0.606 ms 0.725 ms 0.852 ms
3 137.221.105.12 (137.221.105.12) 1.069 ms 1.081 ms 1.085 ms
4 137.221.66.16 (137.221.66.16) 1.084 ms 1.086 ms 1.085 ms
5 137.221.83.66 (137.221.83.66) 6.752 ms 6.768 ms 6.916 ms
6 137.221.65.68 (137.221.65.68) 15.090 ms 13.873 ms 13.846 ms
7 137.221.68.32 (137.221.68.32) 7.470 ms 7.000 ms 7.014 ms
8 lax-ge1.tm.net.my (206.223.123.94) 5.391 ms 5.432 ms 5.478 ms
9 * * *
10 210.195.195.18 (210.195.195.18) 184.017 ms 171.748 ms 172.959 ms

05/07/2019 09:08:55 UTC
--------------------

PING:
PING 210.195.195.18 (210.195.195.18) 56(84) bytes of data.
64 bytes from 210.195.195.18: icmp_seq=1 ttl=53 time=172 ms
64 bytes from 210.195.195.18: icmp_seq=2 ttl=53 time=172 ms
64 bytes from 210.195.195.18: icmp_seq=3 ttl=53 time=185 ms
64 bytes from 210.195.195.18: icmp_seq=4 ttl=53 time=174 ms

--- 210.195.195.18 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 172.220/175.946/185.084/5.338 ms

05/07/2019 09:08:55 UTC
--------------------

MTR:
Start: Fri Jul 5 09:08:55 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.8 1.3 0.4 5.6 1.5
3.|-- 137.221.105.12 0.0% 10 0.5 0.5 0.4 0.7 0.0
4.|-- 137.221.66.16 0.0% 10 1.2 3.5 0.8 21.8 6.5
5.|-- 137.221.83.66 0.0% 10 20.4 9.3 5.6 27.1 7.7
6.|-- 137.221.65.68 0.0% 10 10.6 10.0 5.5 43.9 12.0
7.|-- 137.221.68.32 0.0% 10 40.1 15.8 5.8 70.0 21.8
8.|-- lax-ge1.tm.net.my 0.0% 10 5.4 11.3 5.3 48.4 13.9
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 210.195.195.18 0.0% 10 190.4 187.2 184.3 190.4 2.5

05/07/2019 09:08:55 UTC
--------------------
@Ensky01
No issue found in your logs. Try getting a WinMTR log.
How to run WinMTR: https://us.battle.net/support/en/article/27780

Note that there are 3 servers for Americas region:
- North America
- South America (Brazil)
- Australia

If I'm correct, you are South East Asia player. You may be connected to Australia server. So make sure you use the correct IP in the WinMTR test.

You may force the launcher to connect to the server your prefered. Read this post for the steps: https://us.battle.net/forums/en/d3/topic/12372787193
ran with NA IP address

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 0 | 304 | 304 | 0 | 1 | 20 | 1 |

| 210.195.159.254 - 0 | 304 | 304 | 2 | 11 | 70 | 3 |

| 10.55.49.91 - 0 | 304 | 304 | 167 | 169 | 222 | 169 |

| 10.55.100.120 - 0 | 304 | 304 | 9 | 12 | 34 | 11 |

| 10.55.96.167 - 0 | 304 | 304 | 165 | 169 | 237 | 188 |

| eqix-ix-la1.blizzard.com - 0 | 304 | 304 | 167 | 172 | 237 | 168 |

| ae1-br01-eqla1.as57976.net - 0 | 304 | 304 | 166 | 175 | 276 | 216 |

| be1-pe02-eqla1.as57976.net - 0 | 304 | 304 | 167 | 168 | 205 | 168 |

| 24.105.30.129 - 0 | 304 | 304 | 167 | 178 | 205 | 170 |

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

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
07/07/2019 08:45 AMPosted by Ensky01
| 24.105.30.129 - 0 | 304 | 304 | 167 | 178 | 205 | 170 |
The last hop (server) shows pings btw 167-205, average 178ms. I'd say normal for a connection between SEA and NA. The numbers agreed with the result of MTR log you posted earlier.
No data packet loss.
I don't find any issue here.

Q:
Are you sure you are connecting to NA, not AU? May be, run a test with AU IP as well.

Did you run the test WHILE you're experiencing lag? If not, try again when you get laggy.

Otherwise, the laggy might not be caused by something else, not by network. Try the steps in this support article: https://us.battle.net/support/en/article/112206

Edit: I just did a quick test run on NA server, no laggy experienced. I'm from a different country in Asia, with average ping higher than yours.
He Ensky01,

If you still have an issue, go ahead and create a new thread for your situation. This is an old thread and it can get confusing when new people keep posting.

Join the Conversation

Return to Forum