Does Telkom Still Have A CSD department? Line issues

[KingLv]

Holding for 1hr now no response.

Zertop's "Is it my Line" Results
Date/Time: Thu Apr 23 17:47:39 CAT 2015

Basic Report:

Your packet loss was 23%.
Your average ping was 3030ms.
Your maximum ping was 3666ms.

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=708ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1647ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2581ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2541ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2658ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3458ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2859ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2969ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3398ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3540ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3666ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3221ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3150ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3280ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3284ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3329ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3131ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3304ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3230ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3342ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3443ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3471ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3492ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 23, Lost = 7 (23% loss),
Approximate round trip times in milli-seconds:
    Minimum = 708ms, Maximum = 3666ms, Average = 3030ms

 

[KingLv]

So got hold of them after a 1h 20mins.

Spoke to a guy buy the name of Shuping - Bloem Call Centre.

He claims I have been throttled. Due to usage. I asked are you sure because I checked the usage tool and it does not indicate that. Usually you a note at the bottom of your bar indicating you have been throttled.



The he claims his going to reset ports. So the guy tells me turn off the modem, I do and he says please hold.
The call dies totally.

So I give it 15mins thinking he will call back... but I was wrong.

So telkom reps can just cut your call... Thanks Telkom.

Tried one of my spare accounts but same problem so I am going to try calling again...

On hold now for 30mins and counting.



Telkom ISP

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 1623 ms 1953 ms 2555 ms wblv-ip-hsll-2-gi-3-0-0-vl127.telkom-ipnet.co.za
[105.226.0.245]
4 * * 3990 ms 105.226.0.246
5 * * * Request timed out.
6 * * * Request timed out.
7 1050 ms 902 ms 1138 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]

8 1160 ms 1088 ms 1165 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]

9 1193 ms 1235 ms 1278 ms 72.14.239.129
10 1406 ms 1363 ms 1420 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

 

[gmbpro]

Buddy Telkom's contention ratio plays a major part of alot peoples problems relating to their adsl service...
I'm currently trying to get sort my authentication issue, since the 13 4 2015 already, sjoe they suck

 

[AntiGanda]

So got hold of them after a 1h 20mins.

Spoke to a guy buy the name of Shuping - Bloem Call Centre.

He claims I have been throttled. Due to usage. I asked are you sure because I checked the usage tool and it does not indicate that. Usually you a note at the bottom of your bar indicating you have been throttled.

View attachment 210324

The he claims his going to reset ports. So the guy tells me turn off the modem, I do and he says please hold.
The call dies totally.

So I give it 15mins thinking he will call back... but I was wrong.

So telkom reps can just cut your call... Thanks Telkom.

Tried one of my spare accounts but same problem so I am going to try calling again...

On hold now for 30mins and counting.



Telkom ISP

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 1623 ms 1953 ms 2555 ms wblv-ip-hsll-2-gi-3-0-0-vl127.telkom-ipnet.co.za
[105.226.0.245]
4 * * 3990 ms 105.226.0.246
5 * * * Request timed out.
6 * * * Request timed out.
7 1050 ms 902 ms 1138 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]

8 1160 ms 1088 ms 1165 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]

9 1193 ms 1235 ms 1278 ms 72.14.239.129
10 1406 ms 1363 ms 1420 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Been there, had that.

It seems to be part of their repertoire.

The call centre has little or no real auditing of what they say and do.

 

[KingLv]

The sent me a sms to rate the second guy I spoke to... he actually logged a ticket for me.

Their QA should include that for every call the call centre has.

Had 2 call from telkom so far and it sounds like they dont know what the problem is.
The last call the agent blamed my router.

Todays trace routes are way better... *Note "SAME ADSL MODEM"
But for some reason I still see hops that timed out.

C:\Users\hp>ping google.co.za

Pinging google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=36ms TTL=55
Reply from 216.58.223.3: bytes=32 time=36ms TTL=55
Reply from 216.58.223.3: bytes=32 time=38ms TTL=55
Reply from 216.58.223.3: bytes=32 time=36ms TTL=55

Ping statistics for 216.58.223.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 38ms, Average = 36ms

C:\Users\hp>tracert google.co.za

Tracing route to google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 13 ms 13 ms 13 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za.0
.226.105.in-addr.arpa [105.226.0.29]
4 14 ms 13 ms 12 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 14 ms 13 ms 15 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

6 * * * Request timed out.
7 38 ms 37 ms 35 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]

8 36 ms 36 ms 36 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]

9 36 ms 37 ms 37 ms 72.14.237.239
10 37 ms 36 ms 48 ms ssl.gstatic.com [216.58.223.3]

Trace complete.