I have the same problem with demon hunter for the last 2 days
my freind and me got the same problem whit the lag spikes.
we do play demon hunter
Can blizzard please realise that this have only been a problem after the update. My game ran fine before this. So no it canāt be my isp. all of a sudden. Fix it ffs.
Yeah so i have also Massive lag in my game.
ran winmtr and it show only packages being dropped at the blizzard side of the network. so it seems you equinix am1 datacenter at Luttenbergweg 4 1101 EC Amsterdam The Netherlands, is having some problems with dropped packages in their data center, you might wanna call this number to let them know (tel:+31.20.808.0015)
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| ubnt - 0 | 156 | 156 | 0 | 0 | 1 | 0 |
| albertslund-edge1-lo.net.gigabit.dk - 0 | 156 | 156 | 23 | 29 | 115 | 30 |
| customer-185-24-168-XXX.ip4.gigabit.dk - 0 | 156 | 156 | 22 | 25 | 85 | 23 |
| -blizzard-1.equinix-am1.nl-ix.net. - 2 | 148 | 146 | 37 | 42 | 111 | 45 |
| -ae1-br02-eqam1.as57976.net. - 2 | 148 | 146 | 37 | 43 | 154 | 38 |
| -et-0-0-67-pe01-eqam1.as57976.net. - 3 | 144 | 141 | 37 | 43 | 113 | 41 |
| 137.221.66.43 - 2 | 148 | 146 | 37 | 39 | 54 | 38 |
| 185.60.112.157 - 2 | 148 | 146 | 37 | 39 | 53 | 38 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| ubnt - 0 | 184 | 184 | 0 | 0 | 0 | 0 |
| albertslund-edge1-lo.net.gigabit.dk - 0 | 184 | 184 | 23 | 29 | 132 | 25 |
| customer-185-24-168-XXX.ip4.gigabit.dk - 0 | 184 | 184 | 22 | 26 | 88 | 23 |
| -blizzard-1.equinix-am1.nl-ix.net. - 4 | 164 | 159 | 37 | 43 | 93 | 47 |
| -ae1-br01-eqam1.as57976.net. - 3 | 168 | 164 | 37 | 41 | 121 | 47 |
| -et-0-0-31-pe02-eqam1.as57976.net. - 2 | 176 | 174 | 37 | 42 | 132 | 71 |
| 185.60.112.158 - 2 | 176 | 174 | 37 | 38 | 74 | 51 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I have also experienced the same issue.
Here is my pathping results.
1 192.168.1.1 (192.168.1.1) 0.608 ms 0.469 ms 0.332 ms 0.314 ms 0.280 ms 0.283 ms 0.284 ms * 0.552 ms 0.390 ms 0.409 ms 0.387 ms 0.351 ms 0.346 ms 0.341 ms * 0.558 ms 0.404 ms 0.354 ms 0.357 ms (10% loss)
2 155.93.169.1 (155.93.169.1) 2.224 ms 2.100 ms 1.984 ms 3.342 ms 6.658 ms 3.458 ms 2.471 ms 2.529 ms 2.431 ms 2.375 ms 2.645 ms 2.295 ms 2.094 ms 2.130 ms 2.271 ms 2.313 ms 12.198 ms 9.506 ms 2.180 ms 2.551 ms (0% loss)
3 154.0.3.97 (154.0.3.97) 2.728 ms 20.779 ms 5.258 ms 7.841 ms 6.063 ms 6.649 ms 8.351 ms 5.846 ms 3.492 ms 6.119 ms 9.763 ms 5.583 ms 6.545 ms 2.495 ms 8.972 ms 6.164 ms 6.843 ms 6.624 ms 7.675 ms 6.546 ms (0% loss)
4 154.0.5.1 (154.0.5.1) 1.252 ms 1.005 ms 0.892 ms
154.0.5.2 (154.0.5.2) 0.922 ms 0.941 ms
154.0.5.1 (154.0.5.1) 0.954 ms 0.973 ms
154.0.5.2 (154.0.5.2) 0.765 ms 0.860 ms
154.0.5.1 (154.0.5.1) 0.923 ms 0.946 ms
154.0.5.2 (154.0.5.2) 0.758 ms 0.784 ms
154.0.5.1 (154.0.5.1) 0.835 ms *
154.0.5.2 (154.0.5.2) 1.089 ms 0.873 ms 0.863 ms 0.829 ms
154.0.5.1 (154.0.5.1) 1.043 ms (5% loss)
5 154.0.5.129 (154.0.5.129) 1.006 ms 0.875 ms 0.901 ms 0.826 ms 0.859 ms 1.121 ms 0.841 ms 0.888 ms 0.767 ms 0.858 ms 0.905 ms 0.903 ms 0.879 ms 0.861 ms 0.864 ms 0.776 ms 0.870 ms 0.760 ms 0.756 ms 0.771 ms (0% loss)
6 154.0.5.100 (154.0.5.100) 1.455 ms 1.214 ms 1.424 ms 1.354 ms 1.326 ms 1.359 ms 1.468 ms * 1.776 ms 1.766 ms 1.366 ms 1.417 ms 1.364 ms 1.326 ms 1.321 ms * 1.617 ms 1.399 ms 1.535 ms 1.560 ms (10% loss)
7 154.0.4.254 (154.0.4.254) 165.568 ms 165.445 ms 165.661 ms 165.482 ms 165.307 ms 165.308 ms 165.384 ms 165.238 ms 165.312 ms 165.318 ms 165.354 ms 165.417 ms 165.458 ms 165.261 ms 165.571 ms 165.341 ms 165.431 ms 165.444 ms 165.362 ms 165.548 ms (0% loss)
8 * * * * * * * * * * * * * * * * * * * * (100% loss)
9 *
Here are the trace route results.
1 192.168.1.1 (192.168.1.1) 0.633 ms 0.324 ms 0.260 ms
2 155.93.169.1 (155.93.169.1) 5.046 ms 2.967 ms 5.666 ms
3 154.0.3.97 (154.0.3.97) 5.414 ms 4.137 ms 6.046 ms
4 154.0.5.1 (154.0.5.1) 1.266 ms 0.913 ms
154.0.5.2 (154.0.5.2) 0.938 ms
5 154.0.5.130 (154.0.5.130) 1.100 ms 0.993 ms 0.941 ms
6 154.0.5.99 (154.0.5.99) 1.568 ms 1.378 ms 1.349 ms
7 154.0.4.254 (154.0.4.254) 165.624 ms 165.313 ms 165.499 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * *
MAC
You have 10% packet loss at 192.168.xxx.xxx which is inside your local network and is most often the IP address assigned to your local router. Power cycle everything and if youāre using wireless, re-test with an Ethernet cable instead.
Two hops in the 154.0.5.x range are losing 5% and 10% of packets respectively. Those network ranges belong to Vumatel, which appears to be a South African ISP.
Combined with your local network dropping packets, Iād suggest you need to speak to your ISP and first ascertain if your router is broken, then show them your PATHPING and ask them to determine why some of their nodes are dropping so many packets.
No general issue with servers ? I have the exact same problem with as57976 loosing packages. And my ends are %0.
The high ping of as57976.net had been explained by support:
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.
Source: https://us.battle.net/forums/en/d3/topic/20771137533#post-4
If you doubt, paste the whole log for support to analyse.
The lag problem started today for me on the Crusader. Were no problems yesterday but have been lag issues all day today.
I had the same ridiculous lag issues that other people have been reporting. My internet was totally fine, and so was my PC and all other connections - it was just D3 freezing up entirely like never before. It started exactly with the S18 season start, even lost a HC char to lag for the first time.
What worked for me is to set the battlet net launcher to āclose the launcher when starting a gameā under settings -> general. Apparently the launcher does some stuff in the background that affects game performance (even if you turn off updates while playing etc).
Give it a try and let me know if this works - itās annoying having to restart the launcher every time again, but it immediately stopped all issues for me.
Tried a group game and got super laggy/rubberbanding and both happened when a WW barb with PE found a mob. It has also happened to me when I used overpenetration with DH on a huge mob but as soon as the mob is decimated it goes back to normal.
Also having massive spikes and regular disconnect issues.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| HG6Box - 3 | 402 | 392 | 0 | 4 | 205 | 3 |
| 142.254.149.73 - 3 | 402 | 392 | 8 | 17 | 203 | 11 |
| agg63.marnohip01h.midwest.rr.com - 3 | 406 | 397 | 9 | 20 | 139 | 22 |
| be86.clmkohpe02r.midwest.rr.com - 2 | 410 | 402 | 11 | 25 | 198 | 16 |
| be27.clmkohpe01r.midwest.rr.com - 3 | 402 | 392 | 11 | 23 | 104 | 23 |
| 107.14.17.252 - 3 | 406 | 397 | 20 | 34 | 221 | 29 |
|bu-ether11.chcgildt87w-bcr00.tbone.rr.com - 3 | 406 | 397 | 21 | 35 | 218 | 42 |
| 66.109.5.225 - 3 | 406 | 397 | 19 | 31 | 216 | 43 |
| 66.109.9.149 - 3 | 406 | 397 | 19 | 35 | 216 | 42 |
| ae1-br01-eqch2.as57976.net - 11 | 298 | 267 | 63 | 269 | 3666 | 2419 |
| Destination host unreachable. - 3 | 405 | 395 | 63 | 91 | 2185 | 68 |
| et-0-0-2-br01-eqla1.as57976.net - 5 | 369 | 352 | 60 | 114 | 3781 | 66 |
| be1-pe01-eqla1.as57976.net - 3 | 406 | 397 | 63 | 74 | 231 | 65 |
| lax-eqla1-ia-bons-02.as57976.net - 3 | 406 | 397 | 64 | 76 | 217 | 66 |
| 24.105.30.129 - 2 | 410 | 402 | 62 | 77 | 292 | 66 |
|________________________________________________|______|______|______|______|______|______|
as57976 - net servers for at least the last 24 hours have been the indicated issue.
Hello Rassekali:
The high ping you have noticed in the as57976.net servers was explained by Blizzard Support here:
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.
Source: https://us.battle.net/forums/en/d3/topic/20771137533#post-4
Your issues start on the first hopā¦
Your modem/router is losing 3% of the data packets your computer sent; the worst ping (205 ms) is also high ā this should be less than 10 msā¦ ideally, lower.
How is your computer connected to your modem/router ?
If you are using a cable, ensure it is well plugged inā¦ at both ends.
If you are using Wi-fi, try using an Ethernet cable.
Also, give the steps suggested in Blizzard Support - Diablo III Latency Problems a go and see if the connection improves.
1 Like
Since yesterday i have lags in GR. In town it might be ok but in 4m party in GR i got like 200ms+ lags. Hardly playable. WinMTR shows packed loss at blizzard servers.
I canāt link or write WinMTR logs because i got error āYou canāt include links.ā. Why is that? how can I report problems without linking any relevant data???
The WinMTR can be copied and pasted directly in your replyā¦ itās usually a small amount of text.
As for the more general question of why you cannot include a linkā¦ It has to do with your ātrust levelā (I hate this name, but thatās what they decided to call it). The trust level is an indication of your activity on the forums. Everyone starts at trust level 0ā¦ with time and forum participation, your trust level increases. See this post for more details:
Until you reach Trust Level 3:
To post a link, write it (or copy-paste it) as you would normally in your post, highlight the entire link and click on the </> button in the formatting bar at the top of the input window. That will transform your link into āPreformatted textā and will be allowed by the forum software. Your link will appear as : https://www.google.com
1 Like
I have lags only in the evenings between 19:00 - 23:00 or 00:00 (90% in party when I play solo thereās no heavy lag spikes. In party though ping can increase up to 200-250ms). And packet loss only at blizzard servers. For some reason now my route is via milano seabone hops (?? ) there was nothing like that before. Those two hops are really laggy btw.ā
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 77 | 77 | 0 | 1 | 7 | 0 |
| 10.10.70.191 - 0 | 77 | 77 | 6 | 9 | 30 | 9 |
| 192.168.191.1 - 0 | 77 | 77 | 5 | 15 | 29 | 11 |
| 109.235.192.93 - 0 | 77 | 77 | 6 | 10 | 18 | 10 |
| 10.240.0.34 - 0 | 77 | 77 | 7 | 10 | 29 | 11 |
| as6762.0.111.netix.net - 0 | 77 | 77 | 71 | 76 | 92 | 77 |
| ae11.milano58.mil.seabone.net - 0 | 77 | 77 | 81 | 88 | 122 | 86 |
| blizzard.milano58.mil.seabone.net - 2 | 74 | 73 | 80 | 85 | 176 | 81 |
| ae1-br01-eqml2.as57976.net - 3 | 70 | 68 | 86 | 91 | 127 | 86 |
| xe-0-0-1-1-br01-eqpa4.as57976.net - 0 | 77 | 77 | 91 | 95 | 147 | 95 |
| et-0-0-29-br02-eqpa4.as57976.net - 3 | 70 | 68 | 86 | 91 | 139 | 87 |
| et-0-0-3-br02-eqam1.as57976.net - 2 | 74 | 73 | 97 | 117 | 471 | 97 |
| et-0-0-67-pe01-eqam1.as57976.net - 0 | 77 | 77 | 90 | 97 | 159 | 137 |
| 137.221.66.43 - 2 | 74 | 73 | 91 | 94 | 104 | 91 |
| 185.60.112.157 - 0 | 77 | 77 | 90 | 96 | 104 | 92 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderIt is unbelieveable ! up to 4k + ping at blizz servers. Can you do something about it?? Fix your servers !!
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 429 | 429 | 0 | 0 | 3 | 0 |
| 10.10.70.191 - 0 | 429 | 429 | 5 | 6 | 24 | 5 |
| 192.168.191.1 - 0 | 429 | 429 | 5 | 7 | 36 | 6 |
| 109.235.192.93 - 0 | 429 | 429 | 5 | 6 | 28 | 7 |
| 10.240.0.34 - 0 | 429 | 429 | 6 | 7 | 24 | 9 |
| as6762.0.111.netix.net - 0 | 429 | 429 | 67 | 68 | 107 | 67 |
| ae11.milano58.mil.seabone.net - 7 | 345 | 324 | 81 | 84 | 132 | 85 |
| blizzard.milano58.mil.seabone.net - 2 | 409 | 404 | 77 | 82 | 162 | 78 |
| ae1-br01-eqml2.as57976.net - 3 | 396 | 388 | 86 | 89 | 123 | 86 |
| xe-0-0-1-1-br01-eqpa4.as57976.net - 4 | 374 | 362 | 86 | 123 | 4734 | 104 |
| et-0-0-29-br02-eqpa4.as57976.net - 3 | 379 | 368 | 86 | 124 | 4129 | 92 |
| et-0-0-3-br02-eqam1.as57976.net - 0 | 429 | 429 | 97 | 117 | 1375 | 97 |
| et-0-0-67-pe01-eqam1.as57976.net - 0 | 429 | 429 | 98 | 102 | 178 | 108 |
| 185.60.112.157 - 0 | 429 | 429 | 98 | 99 | 115 | 99 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderThe Blizzard servers de-prioritize ICMP packets ā those used by trace route, pathping, WinMTR ā which is why you see large pings. See Diablo 3 Forums for more info.
In both WinMTR you have submitted, the issue seems to start at seabone.net (Telecom Italia) which is losing 7% of all the data you sent through during the WinMTR; Telecom Italia is not part of the Blizzard network, nor does Blizzard control what is happening in that server.
Question : In your post yesterday, you said:
Did you change DNS server by any chance ?
I was hoping a Customer Service Rep would answer you todayā¦ I saw your post yesterday, but do not feel confident enough to interpret the WinMTR and recommend a course of action. If I am correct in stating that the issue is within Telecom Italiaā¦ you will likely need to speak with your Interset Service Provider and see if they can, somehow, change the routing your data takes from your home to Blizzard (near Paris, France). Another way of doing that might be to change DNS server ā there are a few well known public DNS server such as Google and CloudFlareā¦ but I think this type of suggestion should come from professionalsā¦ not me 
Another alternative to the forums is to submit a ticketā¦
https://eu.battle.net/support/en/help/contact/1397/ticket
1 Like
Hi, Gilavar! o/
The advice you are given by Boubou is pretty much on point. I would say that the issue may be starting earlier, since we see that the latency goes from around 6-7 to around 70 in just one jump, but I donāt think it would cause the issues you are mentioning, so I would do as Boubou says and worry more about the package loss itself in the seabone.net nodes.
Another important thing to point out is this:
I have lags only in the evenings between 19:00 - 23:00 or 00:100:
When you experience connection issues at specific times, that usually means that thereās a node you are going through that is unable to keep up with demand. Think about it, 19:00 is around the time people are getting home from work, and 23:00/00:00, the time people are going to sleep. So between those times is when most people are going to be connected to the internet. If a node has a problem that only appears once demand starts rising, that explains why it always happens at the same time (and if Iām right, youāll probably experience it more and for longer on Fridays/Saturdays than on Mondays).
So, yeah, I would check with your ISP to see if they can give you any insight into those packages getting lost.
1 Like
I know about it but when I have lag spikes in D3 WinMTR represents that with high ping shown in logs too. When everything is ok in the game then the logs show low ping. Is that just a coincidence?
No I didnāt. Just a coulple of weeks ago (and since I started playing D3 nevere there was those āseaboneā hops in the routing to D3 servers.
Did that just yesterday they answered that they donāt have any power to control the traffic outside their network (which ends at hop 5 in the log given above).
I do use the Google DNS service though
So what I can do about it exactly? My ISP canāt reroute it.
Thank both of you guys for your replies though. I know you try to help and appreciate it.