Any response from Blizzard yet? Still 800ms in Town, this is a frustrating time not being able to play the game. I hope you are not focusing all your attention on Warzone and leaving us hanging here…
1 Like
still no response from blizzard EU, this has been going on for hours.
Well, bumping a 30-day-old thread probably isn’t helping get their attention.
Try this one…
wasnt sure where i should post, ty sir!
big problem for everyone today
Have bad lag spikes too. Usually my ping is at a solid 36, today it’s anything between 54 and 1000ms. Thought it was because I was watching a youtube vid so closed it and it’s still happening. Even doing nothing and standing still my ping shot up to 1027. 
Same here, anything up to 1000ms. Yesterday I was getting 3-4k ms every 5 secs - today isn’t as bad, but not the normal 35ms.
Hi everyone!
If the issue persists, please upload your connection test called an MTR to pastebin.com and reply with the links to the file using the preformatted text option to encapsulate the links.
We would like to look at the connection tests to see the problem when it’s happening, if you don’t have the High Ping when running the test then it won’t show the necessary information. Currently we don’t have anything reported.
I’ve never really had too much of a problem playing Diablo III with a latency of 250ms or thereabouts, but maybe this could help other South Africa players:
https://pastebin.com/jMW90NF2
Those traces are showing approximately 50% packet loss from the third hop and all subsequent hops. A lookup of that hop…
http://whois.domaintools.com/105.187.235.121
…shows it to be South Africa Centurion Telkom Sa Ltd., i.e. your ISP. Probably want to have a word with them and show them the traces.
However, of note is the fact that once again it’s only in the trace to the .157 server that we see an extremely high “worst” of 3730 ms, the trace to the .158 server doesn’t show this.
Oh, I’ve tried! The real trouble is, regardless of who you use as your ISP (Telkom, mWeb, Vodacom, CellC, etc), at some point in the line you must go trough some server owned and controlled by Telkom SA Ltd.
A 250ms latency in Diablo III isn’t that much of a train smash, and just not worth the trouble of trying to have it fixed.
I decided to write again to update my first post. For over 1 month my ping in D3 has been pretty good now. About 90-110 ms in town (good for me). Everyone writes on forums when there are problems and nobody usually cares to say ‘thank you’ to blizzard employees for doing their job good and fixing issues. Thanks
2 Likes
Having intermittent 1016 drops.
Given that this is SA and we have poor internet comms to the rest of the world ping lag is understandable, but being dropped for a lost packet?
Does not make sense.
Is there any solution for this particular issue that does not result in being kicked off during a game?
averaging between ~150 and ~300ms ping lag.
In the past I’ve never been dropped, have had lag up to 1000+ms, but since mid feb this year this issue has rendered the game essentially unplayable.
Please advise
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.1.100 - 0 | 72 | 72 | 0 | 7 | 399 | 2 |
| 10.22.1.37 - 0 | 72 | 72 | 2 | 9 | 405 | 7 |
| 41.76.35.4 - 0 | 72 | 72 | 2 | 11 | 404 | 8 |
| 41.77.200.105 - 0 | 72 | 72 | 2 | 11 | 414 | 7 |
| 41.76.35.5 - 0 | 72 | 72 | 2 | 11 | 412 | 4 |
| 197.159.33.209 - 0 | 72 | 72 | 2 | 11 | 437 | 7 |
| core.xe-1-0-0-gb-ld-te-pbr-1.gb.africainx .net - 0 | 72 | 72 | 142 | 155 | 564 | 147 |
| core.xe-0-0-1-nl-am-eqx-pbr-1.nl.africainx .net - 0 | 72 | 72 | 149 | 160 | 569 | 151 |
| 80.249.208.83 - 0 | 72 | 72 | 150 | 163 | 553 | 158 |
| ae1-br01-eqam1.as57976 .net - 0 | 72 | 72 | 150 | 195 | 820 | 158 |
| et-0-0-35-pe02-eqam1.as57976 .net - 2 | 68 | 67 | 149 | 161 | 560 | 150 |
| 137.221.66.41 - 0 | 72 | 72 | 148 | 158 | 572 | 150 |
| 185.60.112.158 - 0 | 72 | 72 | 150 | 159 | 566 | 156 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
output of traceroute > 185.60.112.158:
Tracing route to 185.60.112.158 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.1.100
2 5 ms 2 ms 3 ms 10.22.1.37
3 4 ms 6 ms 3 ms 41.76.35.4
4 13 ms 101 ms 5 ms 41.77.200.105
5 5 ms 2 ms 4 ms 41.76.35.5
6 4 ms 3 ms 3 ms 197.159.33.209
7 143 ms 149 ms 175 ms 41.84.12.80
8 153 ms 149 ms 155 ms 41.84.13.14
9 * 162 ms 152 ms 80.249.208.83
10 * 3374 ms 1821 ms 137.221.78.33 <- unusually high MTR, packet loss
11 150 ms 155 ms 184 ms 137.221.78.75
12 152 ms 149 ms 148 ms 137.221.66.41
13 151 ms 150 ms 151 ms 185.60.112.158
Trace complete.
still having this accursed error on EU.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|
-internal-
| 192.168.1.100 - 1 | 186 | 185 | 0 | 5 | 41 | 1 |
router -> ISP:
| 10.22.1.188 - 1 | 186 | 185 | 0 | 8 | 55 | 4 |
| 41.76.35.6 - 1 | 186 | 185 | 0 | 7 | 46 | 4 |
| 41.76.35.5 - 1 | 186 | 185 | 0 | 6 | 47 | 5 |
From here, my ISP to upstream ISP:
| 197.159.33.209 - 0 | 192 | 192 | 2 | 7 | 41 | 3 |
//this one owned by AfricaINX, with significantly high ping
–>| 41.84.12.80 - 1 | 188 | 187 | 0 | 148 | 208 | 147 |<–
//this ip is in the UK:
–>| 195.66.226.234 - 0 | 192 | 192 | 144 | 151 | 204 | 146 <–|
| 137.221.79.33 - 0 | 192 | 192 | 149 | 201 | 450 | 150 |
| No response from host - 100 | 38 | 0 | 0 | 0 | 0 | 0 |
| 137.221.65.77 - 0 | 192 | 192 | 150 | 282 | 979 | 151 |
| 137.221.78.57 - 0 | 192 | 192 | 149 | 156 | 225 | 151 |
| 137.221.66.43 - 0 | 192 | 192 | 150 | 157 | 203 | 153 |
| 10.105.1.149 - 0 | 192 | 192 | 149 | 155 | 201 | 150 |
| 37.244.28.102 - 0 | 192 | 192 | 149 | 155 | 201 | 149 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
how much do we have to pay activision to get them to get this game working properly again? servers have been getting more finecky every single season. dont assume all of us to be computer geeks. You do it, you run your tests. Look at my account or whatever, and fix the issues. Cant you guys see who logs in on which account, and check your servers connection history to that (IP? ISP? whatever its called) How much to give a shit about the player’s experience? Give me a number…
The last 2-3 days I got high ping or high lag spikes in the evenings.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.lan - 0 | 64 | 64 | 0 | 0 | 3 | 1 |
| 100.68.0.1 - 0 | 64 | 64 | 2 | 5 | 16 | 3 |
| 172.22.1.2 - 0 | 64 | 64 | 2 | 4 | 20 | 3 |
| 94.20.50.145 - 0 | 64 | 64 | 2 | 5 | 33 | 3 |
| 10.50.10.42 - 0 | 64 | 64 | 5 | 7 | 10 | 7 |
| msk-m9-cr3.irb-2500.rascom.as20764.net - 42 | 24 | 14 | 39 | 41 | 55 | 39 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| frm-nt-cr1.be8.rascom.as20764.net - 42 | 24 | 14 | 75 | 77 | 79 | 75 |
| pr01.eqfr5.blizzardonline.net - 42 | 24 | 14 | 76 | 82 | 111 | 80 |
| ae1-br01-eqfr5.as57976.net - 38 | 27 | 17 | 82 | 91 | 185 | 82 |
| et-0-0-2-br01-eqam1.as57976.net - 50 | 20 | 10 | 83 | 1628 | 4351 | 83 |
| 137.221.65.75 - 42 | 24 | 14 | 82 | 84 | 90 | 82 |
| 137.221.78.49 - 55 | 20 | 9 | 82 | 88 | 122 | 83 |
| 185.60.112.158 - 42 | 24 | 14 | 82 | 84 | 89 | 84 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
TRACEROUTE:
traceroute to 188.253.237.29 (188.253.237.29), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.304 ms 0.282 ms 0.276 ms
2 37.244.24.131 (37.244.24.131) 231.803 ms 232.117 ms 232.428 ms
3 Blizzard Blizzard 0.846 ms 0.850 ms 0.852 ms
4 137.221.66.42 (137.221.66.42) 0.931 ms 0.935 ms 0.932 ms
5 137.221.78.48 (137.221.78.48) 6.394 ms 6.399 ms 6.398 ms
6 * * *
7 137.221.65.28 (137.221.65.28) 6.582 ms 6.570 ms 6.564 ms
8 137.221.80.32 (137.221.80.32) 6.539 ms 6.543 ms 6.540 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
26/12/2020 18:17:16 UTC
MTR:
Start: Sat Dec 26 18:17:16 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 37.244.24.131 0.0% 10 311.8 217.9 137.6 311.8 60.1
3.|-- Blizzard 0.0% 10 0.8 0.8 0.7 0.8 0.0
4.|-- 137.221.66.42 0.0% 10 0.5 0.5 0.3 0.7 0.0
5.|-- 137.221.78.48 0.0% 10 6.2 12.9 6.2 45.3 14.3
6.|-- 137.221.65.74 0.0% 10 4371. 4318. 4049. 4496. 132.4
7.|-- 137.221.65.28 0.0% 10 6.3 7.0 6.2 13.8 2.3
8.|-- 137.221.80.32 0.0% 10 6.3 9.4 6.3 36.1 9.4
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0