so what have we gathered so far...
the connection from our routers to the first hop is fine and the problem lies between there and the next hop. 'somewhere between the DSLAM and the ESR' apparently. the problem is linked to traffic congestion and is getting worse over time and affecting more and more people (presumably as traffic increases). throughput is being affected with speedtest results about 2mbps down (on a 4mbps account) which is possibly an indication of how over subscribed the network is.
11 August 2010> got automatically upgraded from 4mbps to 8mbps
12 August 2010> pings started creeping up
pings got higher and higher at first just in the evenings, and then more and more throughout the day. packet loss got worse and so did ping until it was crap for gaming 23 out of 24 hours a day - and completely useless for gaming 17 hours a day. its possibly still getting worse and affecting more and more people. packet loss is also on the rise at its worst levels ever now.
24 October 2010> the problem has persisted almost 2.5 months now, ive complained to mweb multiple times who said its not them, its telkom. ive complained to telkom multiple times who are acting like nothing is wrong and refusing to give me any answers or deal with my problem further (engineers dont even contact me anymore). they seem to be avoiding the problem and acting like it doesnt exist. there is still no official statement from them or any sign that they are actually trying to fix it.
here's my last 48 hours graphed... the trend is blatantly clear:
http://i.imgur.com/oxUW0.gif
here's my speedtest results (4mbps line and uncapped mweb account):
http://www.speedtest.net/result/1003144744.png
i tested 3 accounts: mweb uncapped 4meg, telkom monthly capped, and web africa prepaid. whats interesting is not all the hops after the first one bad in these cases. i dont know what that means.
on an mweb account:
>tracert mweb.co.za
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:
1 7 ms 7 ms 9 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
2 179 ms 177 ms * 196-28-178-166.adsl.mweb.co.za [196.28.178.166]
3 121 ms 116 ms 105 ms 196.41.144.36
4 141 ms 137 ms 144 ms
www.mweb.co.za [196.2.63.110]
Trace complete.
--
on a telkom account:
>tracert telkom.co.za
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 6 ms 11 ms 11 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
2 187 ms 175 ms 175 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
3 28 ms 28 ms 33 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
4 30 ms 30 ms 30 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
5 179 ms 188 ms 185 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
--
on a web africa account:
>tracert webafrica.co.za
Tracing route to webafrica.co.za [196.220.58.66]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms wrbs-ip-esr-2.ipnet.wa.co.za [41.185.88.1]
2 8 ms 9 ms 18 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
3 10 ms 9 ms 9 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
4 9 ms 9 ms 9 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
5 169 ms 162 ms 155 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
6 138 ms 137 ms 145 ms wa-acc1.wadns.net [196.220.39.253]
7 158 ms 163 ms 167 ms 196.220.58.66
Trace complete.
--