Okay so you asked for some trace routes:
google.com:
Tracing route to google.com [74.125.233.0]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 * * * Request timed out.
3 308 ms 44 ms 46 ms 41.181.178.18
4 10 ms 8 ms 18 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
5 10 ms 8 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
6 16 ms 8 ms 66 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
7 198 ms 209 ms 251 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
8 208 ms 193 ms 187 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
9 191 ms 206 ms 241 ms 209.85.255.76
10 232 ms 198 ms 189 ms 66.249.95.9
11 187 ms 187 ms 194 ms 72.14.237.239
12 235 ms 186 ms 186 ms jnb01s07-in-f0.1e100.net [74.125.233.0]
Trace complete.
Dota 2 server Johannesburg
Tracing route to 196.38.180.1 over a maximum of 30 hops
1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 * * * Request timed out.
3 40 ms 26 ms 8 ms 41.181.221.249
4 8 ms 32 ms 123 ms 41.181.221.250
5 8 ms 23 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
6 23 ms 8 ms 8 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
7 36 ms 20 ms 23 ms 41.181.180.10
8 7 ms 23 ms 28 ms 196.44.0.72
9 10 ms 10 ms 19 ms 41-208-29-125.mtnns.net [41.208.29.125]
10 10 ms 24 ms 9 ms core1a-pkl-te-1-1.ip.isnet.net [196.26.0.60]
11 69 ms 43 ms 68 ms 196.38.180.1
Trace complete.
And latest speedtest:
http://www.speedtest.net/my-result/3885166998
It's just up and down every few seconds. Last night was even worse. 300+ ping to the local game servers, which would even be sort of playable if it weren't for the massive spikes.
Can someone explain to me how we went from a functioning system to this bull****? Are your paying customers here to stress test your under-development system?