Pinging servers are fine but in game latency high

Technical Support
I am kind of getting sick of this to be honest. Everyone always tells me to run a ping test to europe servers. Being in South Africa, our pings are expected to be around 220 to 280, which is completely manageable. So here you can see I ping the Europe servers and all is honky dory from what I can tell with a constant 200+ms ping time:

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=214ms TTL=235
Reply from 185.60.112.157: bytes=32 time=218ms TTL=235
Reply from 185.60.112.157: bytes=32 time=214ms TTL=235
Reply from 185.60.112.157: bytes=32 time=214ms TTL=235

Pinging 185.60.112.158 with 32 bytes of data:
Reply from 185.60.112.158: bytes=32 time=222ms TTL=235
Reply from 185.60.112.158: bytes=32 time=219ms TTL=235
Reply from 185.60.112.158: bytes=32 time=220ms TTL=235
Reply from 185.60.112.158: bytes=32 time=220ms TTL=235


So then can I ask WHY THE HELL in the last few months I have been playing D3 I keep getting above 400-1000ms latency most of the damned time? And it is ONLY D3 that does this. Heroes of the Storm I get a constant 220, Overwatch a constant 219-225, and when I played it Wow was always on 220 even when downloading.

It is ONLY Diablo 3 that keeps doing this ever since I bought the original game before the expansion, but back then it wasn't so bad. It's gotten worse as time went by. I have formatted my PCs, switched ISPs, swapped out network cards, tried wifi, tried mobile data, tinkered with network settings, reinstalled multiple versions of Win 7, 8 and 10, redownloaded the game you name it. Even got an entire new computer. IT IS ALWAYS THE SAME!

I have browsed these forums and others as well for possible solutions. And none of them worked.

And after 4 years of this I am sick and tired! I shall not be buying the Necromancer pack until I have some damned answers. And if my case is a lost cause, then I demand a refund for the game and expansion I purchased in full as I deem the product useless and broken. Might buy the console version instead because there I won't have any "trust" issues with Blizzard to be constantly online all the damn time. But what do we know in Africa? You got our money already right? So f*** us then. Maybe open a server in Africa so we won't have these issues, but "f*** them we got their money" amiright?

I can't run higher level greater rifts because of this. One moment everything is standing in place the next I am dead. Trying to run a thorns crusader is nearly impossible because of all the rubberbanding. And AGAIN: THIS IS ONLY DIABLO 3 THAT DOES THIS!?!?!?!?!?!? Why are the other games having NO problems whatsoever?

Here is my path ping for whatever it's worth. Don't think it will help at all as I have seen other users do the same and get no answers from you people.

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.1.254
2 * * * Request timed out.
3 36 ms 35 ms 36 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 38 ms 36 ms 37 ms 169-1-5-250.ip.afrihost.co.za [169.1.5.250]
5 148 ms 161 ms 147 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 101 ms 98 ms 96 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 38 ms 37 ms 36 ms 41.169.57.216
8 * 141 ms 141 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
9 221 ms 232 ms 216 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 207 ms 207 ms 207 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.97]
11 307 ms 305 ms 327 ms if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
12 * 313 ms 317 ms if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
13 310 ms 309 ms 309 ms if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
14 295 ms 311 ms 305 ms if-ae-2-2.tcore1.WYN-Marseille.as6453.net [80.231.217.1]
15 310 ms 295 ms 291 ms if-ae-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
16 207 ms 208 ms 208 ms if-ae-11-2.tcore1.PVU-Paris.as6453.net [80.231.153.49]
17 311 ms 311 ms 343 ms 80.231.153.66
18 * * * Request timed out.
19 310 ms 315 ms 314 ms BLIZZARD-EN.ear2.Paris1.Level3.net [212.73.205.158]
20 301 ms 292 ms 290 ms 37.244.9.33
21 * * * Request timed out.
22 309 ms 319 ms 321 ms 185.60.112.157

Trace complete.


And I have tried programs like wtfast and even they can't completely fix the issue, making my pings range from 250 when quiet to jumping to 400 when things get busy. Also, why do I have to pay ANOTHER service for better pings when it is the freaking job of the company who makes the games' jobs to be certain that it does play smooth?
Hey, Raionhato!

5 148 ms 161 ms 147 ms jhb-net1.ip.adsl.co.za [169.1.5.52]

It appears you are getting way higher than normal ms rates on a Afrihost node before your connection leaves South Africa.

8 * 141 ms 141 ms ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]

You are also seeing dropped pings on a LIR backbone connection in South Africa.

It just gets much worse from there, well before it reaches our servers. This appears to be a local connection or ISP issue. If you are on a wireless connection, I would first start by trying a wired Ethernet connection to see if that helps at all.

I would also recommend trying the Connection Troubleshooting article steps before contacting your ISP (Afrihost) to let them know about these routing nodes. Just help narrow down any other possible causes for this poor of a connection when routed to our servers.
I have done exactly everything as you've said:

It appears you are getting way higher than normal ms rates on a Afrihost node before your connection leaves South Africa.


I have switched between 3 different ISP's. All the same results. So in my eyes, it doesn't matter if I contact them. And I must stress again, MY OTHER GAMES WORK FINE! It is only D3 that has this issue since day 1.

You are also seeing dropped pings on a LIR backbone connection in South Africa.


Again, only D3 has the issue, and not Overwatch or Heroes of the Storm. Simple solution: MAKE SERVERS IN AFRICA! But we're living in the boonies as far as the northern hemisphere is concerned it seems and aren't worthy of mighty Blizzard's time :(

If you are on a wireless connection, I would first start by trying a wired Ethernet connection to see if that helps at all.


Sigh....... I said I TRIED A WIRELESS CONNECTION. I am on a 10mbps ADSL line connected with a cable.

I would also recommend trying the Connection Troubleshooting article steps before contacting your ISP (Afrihost)


And again:
I have browsed these forums and others as well for possible solutions. And none of them worked.


So you're just telling me the same as everyone else........ yeah I figured as much and don't know why I deluded myself into thinking I can get answers.

Can I stress again that ONLY D3 does this and not your other games? Or ANY other online game as a matter of fact? Guild Wars 2, Hawken, CS:GO you name it if I connect to europe servers my ping is fiiiiiiiiiine. ONLY D3! Did I repeat that enough already???
As a matter of fact, I just tried another rift and got bombarded with 400-1000 ping again, immediately went into Overwatch and HotS AND LO AND BEHOLD 220. Please I would LOVE to hear the reasoning behind this.

And I know it's not the new update like everyone else is harping on about. This has started for me since 2013.
The information provided is a fact. It is not an opinion. The answer is you have a bad connection to our servers. The route you are taking to get to the server you ran the trace route to is not a solid connection. It appears to be your ISP having issues on certain nodes. I see you have been on the exact same connection for over a year.

I completely understand that it is frustrating, but that is the answer we can give you. If it was our servers, every single other player would have the exact same issue you are experiencing. This is not the case. The best option would be to contact your Internet Service Provider.
And they will just tell me what they have told me before. "Everything is fine on our end and seems fine on your end too. Try contacting Blizzard." And then this pointless cycle continues.

So, the only solution, for me at least, seems like never buy anything Blizzard related in the future as there are no guarantees that this issue won't replicate itself again and again in our country. Of course an Africa server, like what most of us have been complaining about for YEARS, would fix most our issues but it seems like our continent is beneath the attention of a mega company that makes millions each month to care about all players in the world. Maybe Blizzard shouldn't sell games in countries that doesn't have direct access to servers, but oh, then they wouldn't make money now would they.

I don't even know why I try. Uninstalling this piece of garbage. Yes, it's a garbage game, because the other games, some of which runs through the same nodes and ip address's, have no problem but only this game has it. So the "bad" connection works for my other games, but apparently I just have to deal with it in D3. That to me shows it's a broken game that does not want to work for me. And I HATE calling games I know I can enjoy for countless hours garbage because of technical issues. I will even allow my characters and progress wiped at this point if it means I can get a refund, but of course Blizzard won't.

Yes, I use this connection for the last year, because the last ISP we were with did the same thing JUST for D3, and I decided to try another ISP to see if it fixes it. It did not.

And do not presume to understand me and other people in africa's frustration. We pay our arses off in this economy of ours to enjoy your products only to not play your games half the damned time because of networking issues.

I even heard speculation once that servers are only opened in regions that play competitively and there isn't enough demand in Africa for it. We have pleaded for YEARS to get servers this side only to be met with false promises of better P2P connection. I can promise you when servers open up here your player base in africa will explode. But whatever....
I work as a network tech. Ibaraius is correct that your traces look wonky. Often the first-line tech support from the ISP doesn't know how to do much other than tell you to reset your router. Try asking for level 3 tech support and provide them the output from your diagnostics. You can also try running an MTR test, which will give you a much larger sample size than traceroute or ping...

https://us.battle.net/support/en/article/27780
Hi

Not ISP based.
Getting the same issue from Pretoria in South africa.
Getting alot of packet loss on the blizz server side.

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=174ms TTL=244
Reply from 185.60.112.157: bytes=32 time=181ms TTL=244
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Request timed out.
Request timed out.
Reply from 185.60.112.157: bytes=32 time=186ms TTL=244
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Reply from 185.60.112.157: bytes=32 time=183ms TTL=244
Reply from 185.60.112.157: bytes=32 time=180ms TTL=244
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Reply from 185.60.112.157: bytes=32 time=186ms TTL=244
Request timed out.
Reply from 185.60.112.157: bytes=32 time=171ms TTL=244
Reply from 185.60.112.157: bytes=32 time=187ms TTL=244
Request timed out.
Request timed out.
Reply from 185.60.112.157: bytes=32 time=177ms TTL=244
Request timed out.
Request timed out.

Ping statistics for 185.60.112.157:
Packets: Sent = 20, Received = 13, Lost = 7 (35% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 187ms, Average = 177ms

To compare here is a ping to the east coast over watch server ping which is a lil high but stable.

Pinging 24.105.44.5 with 32 bytes of data:
Reply from 24.105.44.5: bytes=32 time=279ms TTL=240
Reply from 24.105.44.5: bytes=32 time=266ms TTL=240
Reply from 24.105.44.5: bytes=32 time=297ms TTL=240
Reply from 24.105.44.5: bytes=32 time=289ms TTL=240
Reply from 24.105.44.5: bytes=32 time=368ms TTL=240
Reply from 24.105.44.5: bytes=32 time=371ms TTL=240
Reply from 24.105.44.5: bytes=32 time=367ms TTL=240
Reply from 24.105.44.5: bytes=32 time=314ms TTL=240
Reply from 24.105.44.5: bytes=32 time=275ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=326ms TTL=240
Reply from 24.105.44.5: bytes=32 time=310ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=265ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=257ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=304ms TTL=240
Reply from 24.105.44.5: bytes=32 time=256ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=268ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=257ms TTL=240
Reply from 24.105.44.5: bytes=32 time=284ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=267ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=264ms TTL=240
Reply from 24.105.44.5: bytes=32 time=255ms TTL=240
Reply from 24.105.44.5: bytes=32 time=256ms TTL=240

Ping statistics for 24.105.44.5:
Packets: Sent = 39, Received = 39, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 255ms, Maximum = 371ms, Average = 275ms

I could not find a pingable EU over IP hence why I had to go for NA

But the point remains.. there is packet loss on the Diablo server from sunny SA side.
I have mailed them the quotes that Ibaraius state has slow nodes to them and awaiting a reply. But I am glad to know I am not the only one in SA to have this issue. back in 2013 when I was with Telkom and living in the western cape I had the same issue only with Diablo 3. My uptime that I could actually play the game and not constantly die is about 30% of my total playtime. I'd get nights where I can play about an hour or two and then it just gets out of control again.
DoomsDay all you have shown is that somewhere between you and Blizzard there is packet loss. That is exactly what Ibariaus was saying. What you have not done is show where that loss is. You need to do a WinMTR as Hal linked and let it run for 10 mins or so at a time when you are lagging. That will show each and every hop along with how much packet loss happens at each hop. That data can then be given to ISP support so they can hopefully work with their network techs to fix it.
07/03/2017 12:13 PMPosted by MissCheetah
DoomsDay all you have shown is that somewhere between you and Blizzard there is packet loss. That is exactly what Ibariaus was saying. What you have not done is show where that loss is. You need to do a WinMTR as Hal linked and let it run for 10 mins or so at a time when you are lagging. That will show each and every hop along with how much packet loss happens at each hop. That data can then be given to ISP support so they can hopefully work with their network techs to fix it.


Here is my trace

1 <1 ms 1 ms 1 ms TP-LINK.Home [192.168.1.1]
2 * * * Request timed out.
3 81 ms 52 ms 61 ms 41.193.164.85
4 71 ms 73 ms 52 ms 41.193.164.86
5 41 ms 67 ms 68 ms 41.193.164.92
6 47 ms 44 ms 21 ms 41.193.119.101
7 213 ms 226 ms 237 ms 41.193.119.1
8 214 ms 233 ms 207 ms te0-0-0-4.ccr21.lon02.atlas.cogentco.com [149.6.
149.201]
9 * 210 ms 228 ms be2792.ccr42.lon13.atlas.cogentco.com [154.54.57
.105]
10 225 ms 235 ms 242 ms be12488.ccr42.ams03.atlas.cogentco.com [130.117.
51.42]
11 232 ms 214 ms 226 ms be2447.rcr21.b021535-1.ams03.atlas.cogentco.com
[130.117.50.250]
12 241 ms 220 ms 230 ms blizzard.demarc.cogentco.com [149.6.128.9]
13 235 ms 242 ms 230 ms 37.244.10.35
14 * * 241 ms 37.244.10.103
15 257 ms 256 ms 237 ms 185.60.112.157

From what I can tell hop 14 seems wonky before hitting the server.

so I pinged hop 13

Pinging 37.244.10.35 with 32 bytes of data:
Reply from 37.244.10.35: bytes=32 time=231ms TTL=245
Reply from 37.244.10.35: bytes=32 time=239ms TTL=245
Reply from 37.244.10.35: bytes=32 time=220ms TTL=245
Reply from 37.244.10.35: bytes=32 time=241ms TTL=245
Reply from 37.244.10.35: bytes=32 time=209ms TTL=245
Reply from 37.244.10.35: bytes=32 time=196ms TTL=245
Reply from 37.244.10.35: bytes=32 time=240ms TTL=245
Reply from 37.244.10.35: bytes=32 time=227ms TTL=245
Reply from 37.244.10.35: bytes=32 time=240ms TTL=245
Reply from 37.244.10.35: bytes=32 time=220ms TTL=245
Reply from 37.244.10.35: bytes=32 time=230ms TTL=245
Reply from 37.244.10.35: bytes=32 time=238ms TTL=245
Reply from 37.244.10.35: bytes=32 time=208ms TTL=245
Reply from 37.244.10.35: bytes=32 time=238ms TTL=245
Reply from 37.244.10.35: bytes=32 time=208ms TTL=245
Reply from 37.244.10.35: bytes=32 time=237ms TTL=245
Reply from 37.244.10.35: bytes=32 time=193ms TTL=245

Ping statistics for 37.244.10.35:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 193ms, Maximum = 241ms, Average = 224ms

Those are the pings we can expect from our side breaking out internationally.
On top of that the ping is stable.

If our ISP's where at fualt then that IP should also have show drops, Right?
I bet you if Raionhato pings hop 13 he will also get a stable ping.

This takes points to something aboard that is causing issues.
07/03/2017 12:21 PMPosted by DoomsDay
9 * 210 ms 228 ms be2792.ccr42.lon13.atlas.cogentco.com [154.54.57
.105]


This is where you start dropping packets. Please use the WinMTR tool that Hal linked to in his post. That will give you a much better idea of where issues are vs trying to ping individual servers.
Did what you said

started up Diablo, went to recource manager to see which IP's DIablo was connecting to and used the one that had the most traffic on it.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| TP-LINK.Home - 0 | 528 | 528 | 0 | 1 | 59 | 1 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| 41.193.164.85 - 1 | 520 | 518 | 3 | 9 | 86 | 50 |
| 41.193.164.86 - 0 | 528 | 528 | 3 | 9 | 75 | 6 |
| 41.193.164.92 - 1 | 524 | 523 | 3 | 8 | 76 | 29 |
| 41.193.119.101 - 1 | 521 | 519 | 4 | 9 | 74 | 6 |
| 41.193.119.1 - 6 | 429 | 404 | 0 | 171 | 244 | 168 |
|te0-0-0-4.ccr21.lon02.atlas.cogentco.com - 1 | 524 | 523 | 166 | 172 | 234 | 168 |
| be2792.ccr42.lon13.atlas.cogentco.com - 11 | 377 | 339 | 0 | 169 | 243 | 165 |
| be12488.ccr42.ams03.atlas.cogentco.com - 1 | 520 | 518 | 173 | 179 | 244 | 178 |
|be2447.rcr21.b021535-1.ams03.atlas.cogentco.com - 11 | 373 | 334 | 0 | 176 | 241 | 171 |
| blizzard.demarc.cogentco.com - 12 | 365 | 324 | 0 | 176 | 242 | 171 |
| 37.244.10.33 - 13 | 349 | 304 | 0 | 175 | 241 | 171 |
| 37.244.10.101 - 11 | 369 | 329 | 0 | 175 | 243 | 171 |
| 185.60.114.149 - 11 | 369 | 329 | 0 | 201 | 773 | 170 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 105 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
| 41.193.164.85 - 1 | 520 | 518 | 3 | 9 | 86 | 50 |


This is where your packet loss starts. Minor, but once it starts it can impact games like D3 that require real time connectivity. D3 is not very forgiving of even minor issues.

| 41.193.119.1 - 6 | 429 | 404 | 0 | 171 | 244 | 168 |


This hop here is now up to 6% packet loss. That is pretty significant for an online game.

| be2792.ccr42.lon13.atlas.cogentco.com - 11% | 377 | 339 | 0 | 169 | 243 | 165 |


But this here is where it gets really bad. 11% loss on that hop. It is close enough to the D3 servers that it may mean you are not routed through there when going to servers for different games or websites. Each takes a different route. We see the same packet loss being carried through to more hops down the road.

It looks more like a Cogentco issue to me - at least that is where the worst of it starts. That may not be your ISP nor Blizzard's - but one of the backbone carriers in the middle.

However, I am sure our Blue friend and Hal both could chime in if they see something I don't.
So if the problem is in the middle, the only solution I can see is to bypass it by using something like wtfast that skips all those. And I am not paying anymore for any of that I'm afraid. And I might sound like a parrot always repeating the same thing over and over again:

servers. africa. now please.
07/03/2017 01:32 PMPosted by MissCheetah
| 41.193.164.85 - 1 | 520 | 518 | 3 | 9 | 86 | 50 |


This is where your packet loss starts. Minor, but once it starts it can impact games like D3 that require real time connectivity. D3 is not very forgiving of even minor issues.

| 41.193.119.1 - 6 | 429 | 404 | 0 | 171 | 244 | 168 |


This hop here is now up to 6% packet loss. That is pretty significant for an online game.

| be2792.ccr42.lon13.atlas.cogentco.com - 11% | 377 | 339 | 0 | 169 | 243 | 165 |


But this here is where it gets really bad. 11% loss on that hop. It is close enough to the D3 servers that it may mean you are not routed through there when going to servers for different games or websites. Each takes a different route. We see the same packet loss being carried through to more hops down the road.

It looks more like a Cogentco issue to me - at least that is where the worst of it starts. That may not be your ISP nor Blizzard's - but one of the backbone carriers in the middle.

However, I am sure our Blue friend and Hal both could chime in if they see something I don't.


I see what you mean.
I am finding it hard to find Diablo and Overwatch servers that have ICMP enabled for testing, they seem to have locked all that down making it hard to pinpoint.

Do you perhaps know fo a pingable overwatch IP we can compare with?
I'm intrested to se if it takes the same route to the other servers.
07/04/2017 09:13 AMPosted by DoomsDay
I see what you mean.
I am finding it hard to find Diablo and Overwatch servers that have ICMP enabled for testing, they seem to have locked all that down making it hard to pinpoint.

Do you perhaps know fo a pingable overwatch IP we can compare with?
I'm intrested to se if it takes the same route to the other servers.


Blizzard masks their servers for security reasons so they don't respond to a ping. It can appear that a trace stops when it hits them, although it does not. What you want to do is the WinMTR linked by Hal https://us.battle.net/support/en/article/27780 . The instructions should give you the EU IP address options. You can't ping them, but you can do the WinMTR to them which will show every hop along the way along with packet loss. You can then compare that to your D3 WinMTR path. They do have different servers in diff locations for various Blizz games so it may be that your OW server connection is a diff path than D3.
Same issues here. Didn't play for like a year, used to be fine though. Same rig, same security, etc. started up a bit with last season and then now got back into the game again with RotN. Used to always be green ping, rarely over 100ms (usually <50ms). MTR and pinging doesn't really show any issues. Latency-sensitive games like Counter Strike, TF2, and similar, no issues, and my ping is usually in the teens or below. Other Blizzard games seem to work fine. D3 consistently jumps from 20,30ms to 1000ms or more, randomly and intermittently, and is all over the map in between. Makes the game really unplayable especially higher level rifts (and forget hardcore). Been going on for a few months at least as it was May when I was doing a bit of seasonal to get back into the game that I noticed this issue (and have been plenty of threads on the forums about it too, it seems, without a clear resolution).
I should mention I'm not in South Africa, I'm 10 miles from Blizzard HQ in California :P Just appreciated the frustration in this thread and can relate.
FWIW, since I really wanted to try out the Necro, I spent some time fiddling with things. I have both McAfee Security and Webroot Secure. I had previously disabled both (prior to launching the Battle.net App or the game itself), with no change to the latency situation. This time, I disabled all aspects of the security again, and, crucially, RESTARTED the computer. While this shouldn't matter, it seems one or both security programs might have a process that interferes with D3, that remains active following disabling (if it launched at system startup). Was able to play for the last 2 hours with a consistent <30ms ping like it always used to be. May want to try something similar with your security software and a reboot, did the trick for me anyway.

Join the Conversation

Return to Forum