rr
r.brinton.wragg r.brinton.wragg

1 reviews | Active since Apr 2017

11 May 2017, 17:40

ADSL line fault "restored" about five times, and is still faulty.

<p>I have had to reopen faults on my line multiple times because it gets closed without ever actually being fixed. <br /> <br /> I am having problems relating to high latency (ping) on my line, and packet loss, choke etc. in online games. I have called in the fault and reported it using the Telkom Live chat feature, and I get a reference number, told that it is in hand with a technician, and then told that the problem is restored. All of this with no actual change to my fault. <br /> I have had someone call me a few times, and each time ask what my actual problem is, as if I have not described it countless times already. Once, a technician from a company that you subcontract to actually came to my premises and was helpful. He checked my line from the house, told me that the issue is not my side, and that someone from Telkom had cut through lines in the area previously and that needed to be repaired. He told me he would do his best to get someone to actually fix the issue. Nothing came of that.<br /> <br /> I have had confirmation from someone calling me to ask the nature of my issue (again) that there is noise on my line when he was monitoring it, and that someone would need to address it, but again, nothing came of it.<br /> <br /> This has been going on for many weeks now, and I am becoming increasingly frustrated at the apparent lack on concern from Telkom’s side. It seems that you think that just closing the fault and saying everything is restored, that my issues will just go away and I will stop bothering you with them.<br /> <br /> I am a paying customer, and I want this service fixed. <br /> <br /> Here are some traceroutes that I ran today after once again being told that my problem has been resolved.<br /> </p> <p>C:\Users\Ryan>tracert google.com</p> <p>Tracing route to google.com [216.58.223.46]<br /> over a maximum of 30 hops:</p> <p>1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]<br /> 2 * * * Request timed out.<br /> 3 159 ms 197 ms 196 ms 197-84-96-185.cpt.mweb.co.za [197.84.96.185]<br /> 4 74 ms 77 ms 71 ms 540.po-channel50.cpt-ipc-2.optinet.net [197.84.96.186]<br /> 5 124 ms 126 ms 129 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]<br /> 6 109 ms 116 ms 166 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]<br /> 7 54 ms 43 ms 44 ms 101.te0-0-2-2.vic-pr-3.optinet.net [197.80.7.7]<br /> 8 118 ms 129 ms 95 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]<br /> 9 85 ms 88 ms 90 ms 72.14.239.129<br /> 10 103 ms 118 ms 106 ms jnb01s08-in-f14.1e100.net [216.58.223.46]</p> <p>Trace complete.</p> <p>C:\Users\Ryan>tracert google.com</p> <p>Tracing route to google.com [216.58.223.46]<br /> over a maximum of 30 hops:</p> <p>1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]<br /> 2 * * * Request timed out.<br /> 3 195 ms 85 ms 90 ms 197-84-96-185.cpt.mweb.co.za [197.84.96.185]<br /> 4 94 ms 96 ms 87 ms 540.po-channel50.cpt-ipc-2.optinet.net [197.84.96.186]<br /> 5 127 ms 121 ms 118 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]<br /> 6 111 ms 90 ms 127 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]<br /> 7 59 ms 43 ms 89 ms 101.te0-0-2-2.vic-pr-3.optinet.net [197.80.7.7]<br /> 8 96 ms 125 ms 101 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]<br /> 9 107 ms 104 ms 133 ms 72.14.239.129<br /> 10 142 ms 112 ms 123 ms jnb01s08-in-f14.1e100.net [216.58.223.46]</p> <p>Trace complete.</p> <p>C:\Users\Ryan>tracert google.com</p> <p>Tracing route to google.com [216.58.223.46]<br /> over a maximum of 30 hops:</p> <p>1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]<br /> 2 * * * Request timed out.<br /> 3 100 ms 107 ms 115 ms 197-84-96-185.cpt.mweb.co.za [197.84.96.185]<br /> 4 94 ms 85 ms 90 ms 540.po-channel50.cpt-ipc-2.optinet.net [197.84.96.186]<br /> 5 132 ms 139 ms 137 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]<br /> 6 150 ms 136 ms 155 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]<br /> 7 49 ms 61 ms 70 ms 101.te0-0-2-2.vic-pr-3.optinet.net [197.80.7.7]<br /> 8 92 ms 114 ms 95 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]<br /> 9 119 ms 151 ms 107 ms 72.14.239.129<br /> 10 133 ms 124 ms 178 ms jnb01s08-in-f14.1e100.net [216.58.223.46]</p> <p>Trace complete.</p> <p> </p> <p>Clearly, NOTHING has been resolved.<br /> <br /> I eagerly await your reply so that I can listen to how you plan on resolving this issue.</p> <p> </p>

0
Replies (1)
Telkom
Telkom's reply12 May 2017, 10:01
Official

Good day Ryan,

Please be assured that this matter has been escalated to our Technical Team, feedback will be provided.

Your reference number is AI***.

We apologize for any inconvenience caused.

Regards,

Busi

Telkom Social Media Team