I'm also from the Strand area and have been experiencing the same issues relating to high latency, due to congestion at the Strand exchange. The problem is noticeable around mid-day, but especially after about 6pm up to midnight. My problems started last weekend (14th/15th of July 2012):
The first fault I logged was on Saturday the 14th. On Sunday the 15th, I called again and they marked my previous reference numbers as "urgent". On Monday, I got a call from a Telkom technician and after explaining my problem to him at great length, he said he'll see what he can do.
I did notice my connection going down for a short period during that day. I suspect they changed the ports on my connection, however, this didn't really help much (if at all). Just before 7pm I phoned in another fault report with a new reference number. I got an SMS very early the next day saying the problem was resolved. About 30min later, a quality assurance lady from Telkom phoned, but I didn't do the survey and reported to her the problem still persisted.
I then logged an escalation query on Telkom's website, but I've not heard anything from them. And, later last night I phoned 10210 again, and now I've basically hit the proverbial "service-consultant-brick-wall" ... the point where they just cannot assist me anymore.
Even though I asked to speak to a supervisor, the operator just flat-out refused. He offered to "downgrade my connection to see if it runs more stable". He also vaguely acknowledged that congestion might occur from time to time. That's basically it. It's not an ISP problem (as a simple traceroute will reveal - notice hop 2) ...
Tracing route to 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms
www.routerlogin.com [192.168.0.1]
2 907 ms 969 ms 1019 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
3 1066 ms 1049 ms 1020 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 1028 ms 1054 ms 1020 ms 196-28-178-169.adsl.mweb.co.za [196.28.178.169]
5 924 ms 889 ms 836 ms 41-133-134-1.dsl.mweb.co.za [41.133.134.1]
Trace complete.
... and it's not a physical problem with the line. My line attenuation and noise margins are within the acceptable range (also confirmed by Telkom).
The problem is either congestion, or some other fault at the exchange that disallows the equipment to run at proper capacity. I've had exactly the same issues about two years ago, before the exchange was upgraded. Let's hope the issue can be resolved. Issues with online gaming and Skype notwithstanding, just plain ol' browsing becomes a pain in the butt, because you have to continuously hit refresh so that the page can load all it's elements properly.
As for downloads or watching streaming video ... well, as you can see from my speedtest result, that's a no-go as well. Holding thumbs for a speedy solution.
Bookmarks