Grahamstown ADSL Problem - Please help with line testing

There has been a problem with the Grahamstown exchange for over a week but I see it's not too bad today - here's a mtr I just ran on my VPN to GTown:

GTown VPN.jpg
 
MickZA said:
There has been a problem with the Grahamstown exchange for over a week but I see it's not too bad today - here's a mtr I just ran on my VPN to GTown:
Click to expand...

Interesting, thanks. My upload speeds are far better than my download speeds. I can maintain 0.8Mb/s on a single upload thread versus only 0.2Mb/s on a download thread.
 
Hi There,
Without running the test but looking at the other results you are the only one with packet loss.
You have a cable fault as others have said so please report it and do not close the fault until you get 0% loss doing the test.

Regards

Tim
 
Tim the Techxpert said:
Hi There,
Without running the test but looking at the other results you are the only one with packet loss.
You have a cable fault as others have said so please report it and do not close the fault until you get 0% loss doing the test.

Regards

Tim
Click to expand...

askari too:

askari said:
Hi Gatecrasher

I'm in Grahamstown and having the same problem. I first noticed it a few days ago trying to play Guild Wars 2. It's playable but the moment I enter an area with a high player count then it lags to all hell and gone .

1) Afrihost 1gig free account on Telkom 4mb
2) http://www.speedtest.net/result/2800977621.png
3)
Ping statistics for 41.181.53.214:
Packets: Sent = 100, Received = 83, Lost = 17 (17% loss)
Approximate round trip times in milli-seconds:
Minimum = 128ms, Maximum = 159ms, Average = 131ms

All of the above has been happening on my Mweb 4mb premium uncapped account as well, before their Seacom troubles started today. Any sort of streaming has been completely useless.
Click to expand...
 
Tim the Techxpert said:
Hi There,
Without running the test but looking at the other results you are the only one with packet loss.
You have a cable fault as others have said so please report it and do not close the fault until you get 0% loss doing the test.

Regards

Tim
Click to expand...

... and I get packet loss on my VPN to GTown (from PE), all my other sites are 0%.
 
Last edited:
Been away for a few days so I didnt have the chance to log a fault with Telkom. Will do first thing on Monday morning. My results are still the same. Packet loss making my games unplayable and very slow single thread speeds, like Gatecrasher. Affects all my accounts.
 
Telkom advised me today that all should be well now.

Well, it is not.

After rebooting, I'm still getting exactly the same packet loss, slow speed test results and throttled single threads.

I guess it was just a quick stab at trying to close a ticket without doing any work.
 
My ticket has been escalated to D-Tech. I hope that's the Telkom equivalent of the SAS.
 
Now it has been referred back from DTech (who I'm told did what they needed to do) to a technician who probably isn't going to arrive for some time, since every ADSL user in Grahamstown will have reported line faults by now. When the technician arrives he will confirm that there is no problem with my line and that everyone in Grahamstown has this same issue.

The error is 24/7, consistent, reliable, repeatable. And it has been like this for 17 days. What is it going to take to get Telkom to fix it?
 
Every single time I report a fault on my line, Telkom closes it saying there is nothing wrong with it. We have even tried to rectify this through our Telkom account manager, but even he seems to think that the problem doesn't exist.

Each time a tech has come out, they always try do a port recreate then physically change the port on the exchange. I try explain to them that this wont fix everybody in Grahamstown internet, but that doesn't click to them. Even when I show them that I have done it through Uniweb, they STILL do it themselves.

No idea how to get this issue escalated further
 
Surim said:
Every single time I report a fault on my line, Telkom closes it saying there is nothing wrong with it. We have even tried to rectify this through our Telkom account manager, but even he seems to think that the problem doesn't exist.

Each time a tech has come out, they always try do a port recreate then physically change the port on the exchange. I try explain to them that this wont fix everybody in Grahamstown internet, but that doesn't click to them. Even when I show them that I have done it through Uniweb, they STILL do it themselves.

No idea how to get this issue escalated further
Click to expand...

The only "promising" reply I have received from anyone came from Telkom's Facebook rep:

We have requested feedback from the tech investigating your fault, as well as other techs assigned to faults in the Grahamstown area. When I look at the results, everything seems fine... no congestion issue for your DSLAM. We have also asked our network infrastructure team to look into this, as it is a possibilty that the power failure could've affected something further up the network. As soon as we receive feedback, we will let you know what the problem is, and what is being done to resolve it.We can only apologise for this inconvenience, and I truly am sorry that your area has experienced this for the past 17 days. ^TL
Click to expand...
 
Thanks Gatecrasher, that is more than we have gotten over many faults and many lines.
 
Thanks to rpm for changing the thread title. Hopefully, a few more Grahamstown ADSL users will see this now and respond. Needless to say, there is still no fix on this after 19 days. If anything, the packet loss and slow speeds have gotten worse.
 
Yep I went down the social media avenue like Gatecrasher and got a similar response as well as a another fault log. The TL guy called me last night and explained its something to do with load balancing, or load balancing being interrupted by that power cut we had a few weeks ago. I'm growing angry now. I cant even watch the Evo 2013 championship stream in 240p. So basically... I cant play games and I cant watch videos of other people playing games. What is the use of paying for another month of ADSL then.

Get it together, Telkom.
 
Last edited:
Telkom "worked" on my fault today. Now everything is worse.



Code: 
>tracert google.com

Tracing route to google.com [74.125.233.39]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.10.1]
  2    37 ms    10 ms    22 ms  105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.
8.129]
  3   246 ms   234 ms    40 ms  41.181.221.254
  4    33 ms    20 ms    20 ms  41.181.198.188
  5   249 ms     *       20 ms  unc-cpt-1.mtnns.net [196.44.18.8]
  6   300 ms   299 ms   296 ms  196.44.31.106
  7   301 ms     *       71 ms  ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30
]
  8   148 ms    40 ms    47 ms  41.181.139.99
  9   170 ms    73 ms   139 ms  72.14.194.74
 10   316 ms   314 ms   219 ms  64.233.174.21
 11   366 ms   331 ms   338 ms  jnb01s01-in-f7.1e100.net [74.125.233.39]

Code: 
>ping 105.236.8.129 -l 4096 -n 100

Pinging 105.236.8.129 with 4096 bytes of data:
Reply from 105.236.8.129: bytes=4096 time=377ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=158ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=234ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=330ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=203ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=120ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=136ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=875ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1176ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1085ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=222ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=616ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=725ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=862ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1197ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1394ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1161ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=176ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=422ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=344ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=329ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=124ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=253ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=332ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=123ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=379ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=119ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=122ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=410ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=899ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1207ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1044ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1412ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=157ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=470ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=716ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=211ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=558ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=392ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=255ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=121ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=166ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=364ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=376ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=279ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=164ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=119ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=124ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=429ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=369ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=161ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=127ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=674ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=824ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=870ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=521ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=682ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=685ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=865ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=1224ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=457ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=780ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=789ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=468ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=280ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=379ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=222ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=119ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=121ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=123ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=120ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=380ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=125ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=127ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=319ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=182ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=360ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=193ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=265ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=409ms TTL=254

Code: 
Ping statistics for 105.236.8.129:
    Packets: Sent = 100, Received = 80, Lost = 20 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 119ms, Maximum = 1412ms, Average = 458ms

Hopefully, this is still a work in progress.
 
My brother-in-law in Ght is having endless crap lately with his ADSL line.
 
askari said:
Wow, that's incredibly bad Gatecrasher. I'm still sitting on 4% packet loss though it jumps around. Did a technician show up or did they fiddle remotely? Should I be expecting a call too?
Click to expand...

Phoned me while I was out. Asked me if my internet was working ok. I said no, that I was still getting huge packet loss and slow speeds. He said the network guys in Pretoria/Jhb are busy working on it. And he will get back to me. Of course, he never did.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X