Game ruining latency, Cape Town South Africa

Technical Support
Hello,

I was advised to make a post here after various back and forth Twitter comments with @Blizzard CS EU

Here are some results from looking glass, My usual in game latency is around 165-180 MS and when its like that I'm like "Awesome! perfect connection" I know that some people won't touch the game at anything over 100ms but being South African I have to rise above that, literally, my latency rises way above that.

Here is a youtube video showing my current gameplay experience https://www.youtube.com/watch?v=7SJBcxb6bJQ&feature=youtu.be

TRACEROUTE:
traceroute to 197.245.140.157 (197.245.140.157), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.472 ms 0.543 ms 0.624 ms
2 * * *
3 37.244.10.102 (37.244.10.102) 1.244 ms 2.719 ms 2.723 ms
4 24.105.31.31 (24.105.31.31) 6.716 ms 6.859 ms 6.947 ms
5 37.244.11.32 (37.244.11.32) 6.691 ms 6.744 ms 6.809 ms
6 vox-linx4-r27.1.voxtelecom.co.za (195.66.237.153) 8.557 ms 8.106 ms 8.096 ms
7 196.41.27.114 (196.41.27.114) 8.388 ms 8.291 ms 8.296 ms
8 vox-cpt-to-ldn-telecity.vox.co.za (196.41.24.173) 148.274 ms 147.831 ms 147.845 ms
9 41.193.120.38 (41.193.120.38) 147.644 ms 147.666 ms 147.633 ms
10 vox-b2b-pts-barrack-ipc-subs.vox.co.za (209.203.1.40) 148.455 ms 148.876 ms 148.863 ms
11 * * *
12 dsl-197-245-140-1.voxdsl.co.za (197.245.140.1) 150.645 ms 149.190 ms 149.081 ms
13 * * *
14 * * *
15 * * *

13/07/2016 14:21:12 UTC
--------------------

PING:
PING 197.245.140.157 (197.245.140.157) 56(84) bytes of data.

--- 197.245.140.157 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms

13/07/2016 14:21:12 UTC
--------------------

MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.1
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.10.102 0.0% 10 2.3 2.3 1.0 3.5 0.8
4. 24.105.31.31 0.0% 10 6.8 7.0 6.7 8.7 0.6
5. 37.244.11.32 0.0% 10 6.8 6.8 6.6 7.9 0.4
6. vox-linx4-r27.1.voxtelecom.co.za 0.0% 10 9.3 9.0 7.8 10.3 0.9
7. 196.41.27.114 0.0% 10 10.6 9.4 7.5 11.3 1.4
8. vox-cpt-to-ldn-telecity.vox.co.za 0.0% 10 151.6 149.6 147.6 151.6 1.4
9. 41.193.120.38 0.0% 10 180.9 153.2 148.1 180.9 9.8
10. vox-b2b-pts-barrack-ipc-subs.vox.co.za 0.0% 10 150.3 149.5 147.7 151.6 1.4
11. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12. dsl-197-245-140-1.voxdsl.co.za 0.0% 10 153.1 151.2 149.3 153.1 1.6
13. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/07/2016 14:21:12 UTC
--------------------
Hello MrGordons,

And thanks a million for the already provided data. Could you please add a pathping and a traceroute with the IPs provided in the article?

Kind regards

_______________________________________
What's your opinion?

https://www.surveymonkey.com/r/Kiemmaki
hi mate

yeah, ALL OF US in SA (irrespective of what game you play) are experiencing this on a daily basis

needless to say ... the problem isn't on our side ... you should see the dc's in the D3 community - countless at a time and countless times a day ... most of them just drop ...

the active SA community across all Blizzard games is literally a couple of ten-thousand strong, and yet we are treated like the underdogs - nobody really cares

don't expect any kind of real interest to be taken or any kind of real solution to be provided to the problem

our money was good enough to take, yet we ourselves on the other, are an entirely different matter - we just need to shut up and be thankful we can play (somewhat)
Tracing route to 185.60.112.158 over a maximum of 30 hops

1 1 ms 1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 4 ms 3 ms 5 ms telkom-upload-vlan-tygerberg-ipc.vox.co.za [41.1
93.121.37]
4 3 ms 2 ms 2 ms vox-upload-teraco-cpt-tygerberg-ipc.vox.co.za [4
1.193.121.38]
5 3 ms 5 ms 2 ms vox-b2b-pts-tygerberg-ipc-int.vox.co.za [196.41.
29.233]
6 28 ms 23 ms 21 ms 41.193.120.33
7 168 ms 162 ms 159 ms vox-ldn-telecity-wacs.vox.co.za [196.41.24.174]

8 180 ms 173 ms 179 ms 196.41.27.113
9 161 ms 169 ms 162 ms 195.66.238.234
10 189 ms 183 ms 184 ms 37.244.11.33
11 205 ms 200 ms 196 ms 24.105.31.30
12 163 ms 165 ms 165 ms 185.60.112.158

Trace complete.
C:\Users\Chris>pathping 185.60.112.158

Tracing route to 185.60.112.158 over a maximum of 30 hops

0 IvyBridge [192.168.1.197]
1 router.asus.com [192.168.1.1]
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 IvyBridge [192.168.1.197]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]

Trace complete.

Join the Conversation

Return to Forum