1 reviews | Active since Nov 2016
Worse than No Service
<p>The CEO certainly knows how to earn millions but does not know how to run a business. Telkom has less than no service where they have to lie to customers with fasle promises. So typical of the new SA</p>
The typical response from Telkom above.
What's happenned so far;
Telkom
Typically replies within a few hours
Chat Conversation Start
244K people like this
Telecommunication Company
NOV 16TH, 10:01AM
Hi. It's almost a week where Telekom network is up and down. Someone was to attend to this but has not been yet. Currently down to 8kb/s. Id is ********** 112086. Contacting you via Cell C with 4g. Please advise. Thanks Duane
NOV 16TH, 1:03PM
Hi,please inbox the circuit number that your line is running on,so we can speed up the process,as well as your physical address and the account holders identity number.Sorry for the inconvenience.^LA
Where do I find the number?
NOV 16TH, 3:24PM
Hi. The telkom number in question.^FK
********** 255
Plot 117, Charlie Street, Lusthof, Vastfontein 0120
********** 112086
NOV 16TH, 7:39PM
Hi Duane. Thank you for all the details. We will get our team to follow up on this query for you. Thank you.^ID
NOV 17TH, 10:05AM
Please supply reference. Service staff must phone ********** 920 for entrance to property. Took +-5min took open FB to message you. See test results I just ran. SUMMARY
Test Name: Google Websites HTTP Latency Test
Test ID: 9
Test result: Problem detected
CRITERIA
Average HTTP latency time (ms) benchmark under which a no problem verdict is rendered: 400
Average HTTP latency time (ms) benchmark between which a potential problem verdict is rendered: 400-500
Average HTTP latency time (ms) benchmark above which a problem verdict is rendered: 500
DETAILS
Thu Nov 17 2016 10:00:23 GMT+0200 (South Africa Standard Time) - Setting TCP timeout length (msec): 10000
Thu Nov 17 2016 10:00:23 GMT+0200 (South Africa Standard Time) - Creating a TCP socket, number / host / port: 26 / fslffetj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - TCP connection established with host / port / status code: fslffetj-ccd-testing-v4.metric.gstatic.com / 80 / 0
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - TCP connection established successfully with host / port: fslffetj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - Preparing to send data with size (bytes): 232
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - Successfully sent data with size (bytes): 232
Thu Nov 17 2016 10:00:26 GMT+0200 (South Africa Standard Time) - Successfully read data from TCP socket with size (bytes): 102
Thu Nov 17 2016 10:00:26 GMT+0200 (South Africa Standard Time) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Thu, 17 Nov 2016 08:00:25 GMT
Connection: close
Thu Nov 17 2016 10:00:26 GMT+0200 (South Africa Standard Time) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 0 / ********** 626073 / 2488
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Setting TCP timeout length (msec): 10000
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Creating a TCP socket, number / host / port: 28 / stskxrtj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - TCP connection established with host / port / status code: stskxrtj-ccd-testing-v4.metric.gstatic.com / 80 / 0
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - TCP connection established successfully with host / port: stskxrtj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Preparing to send data with size (bytes): 232
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Successfully sent data with size (bytes): 232
Thu Nov 17 2016 10:00:33 GMT+0200 (South Africa Standard Time) - Successfully read data from TCP socket with size (bytes): 102
Thu Nov 17 2016 10:00:33 GMT+0200 (South Africa Standard Time) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Thu, 17 Nov 2016 08:00:33 GMT
Connection: close
Thu Nov 17 2016 10:00:33 GMT+0200 (South Africa Standard Time) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 1 / ********** 633225 / 921
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Setting TCP timeout length (msec): 10000
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Creating a TCP socket, number / host / port: 30 / duagcfip-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - TCP connection established with host / port / status code: duagcfip-ccd-testing-v4.metric.gstatic.com / 80 / 0
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - TCP connection established successfully with host / port: duagcfip-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Preparing to send data with size (bytes): 232
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Successfully sent data with size (bytes): 232
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Successfully read data from TCP socket with size (bytes): 102
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Thu, 17 Nov 2016 08:00:36 GMT
Connection: close
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 2 / ********** 636167 / 153
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Total HTTP response time (ms): 3562
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Total number of HTTP requests: 3
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Average HTTP response time (ms): 1187.33
NOV 17TH, 1:38PM
Hi, thanks for your details will have our team follow-up & advise ^JD
your REF for this query is : AI ********** ^JD
Thanks
NOV 17TH, 3:14PM
Hi Duane, you welcome.^TM
NOV 17TH, 5:15PM
Good day Duane
Please be advised this is an update on your query, we would firstly like to apologise for the inconvenience caused, kindly note we have escalated your query to our technical team to assist and provide feedback accordingly.^BP
NOV 17TH, 6:51PM
Great thanks
NOV 20TH, 2:40PM
Still no contact from your technical team for AI ********** . Last time I had a network issue it took 2 years to fix. Do I have to go the same route again?
SUMMARY
Test Name: Resolver Present Test
Test ID: 3
Test result: Problem detected
CRITERIA
DNS resolver test performs a single DNS query and returns a failing result if a valid response is not returned.
DNS resolver test performs a single DNS query and returns a passing result if a valid response is returned.
DETAILS
Sun Nov 20 2016 14:51:24 GMT+0200 (South Africa Standard Time) - Attempting to resolve hostname: ccd-testing-v4.gstatic.com
Sun Nov 20 2016 14:51:24 GMT+0200 (South Africa Standard Time) - DNS server returned DNS query results.
Sun Nov 20 2016 14:51:24 GMT+0200 (South Africa Standard Time) - DNS server returned problem status code: -105
NOV 20TH, 8:12PM
hi,apologies for the delayed response.Our technical team are attending to a case related to the network and further correspondence will follow.^WC
NOV 21ST, 9:23AM
Telkom is responding to your comment: "It took Telkom 2 years to resolve a similar problem ..."
Hi Duene, we humbly do apologise for the delay. Please kindly note that your query has been sent to our mobile team feedback will be provided. ^LKE
Predict the fastest race time for this years Telkom 947 Cycle Challenge and you could win data prizes to keep you speeding along online! Ts&Cs apply. #CC2016
Facebook
NOV 23RD, 6:46AM
Please advice on the next action to take. Urgently
Hi Duane, Your query is in hand with our mobile team for investigation.^BD
When will I get some tangible feedback? I thought it was with a manager? Come guys
NOV 23RD, 9:29AM
Hi,your query is currently at our mobile team with reference AI ********** and they will be in contact,sorry for the inconvenience.^LA
DEC 1ST, 11:53AM
Its now the 1 Nov and you have done absolutely nothing. A month already. Maybe you should employ technicians and managers that know how to deliver services to your customers who actually pay your salaries
DEC 1ST, 4:46PM
Hi Duane ,please accept our apologies for the delay that have been caused,we will follow up with our support team and get back to you.^LK
WED 12:43PM
The typical response from Telkom above.
What's happenned so far;
Telkom
Typically replies within a few hours
Chat Conversation Start
244K people like this
Telecommunication Company
NOV 16TH, 10:01AM
Hi. It's almost a week where Telekom network is up and down. Someone was to attend to this but has not been yet. Currently down to 8kb/s. Id is ********** 112086. Contacting you via Cell C with 4g. Please advise. Thanks Duane
NOV 16TH, 1:03PM
Hi,please inbox the circuit number that your line is running on,so we can speed up the process,as well as your physical address and the account holders identity number.Sorry for the inconvenience.^LA
Where do I find the number?
NOV 16TH, 3:24PM
Hi. The telkom number in question.^FK
********** 255
Plot 117, Charlie Street, Lusthof, Vastfontein 0120
********** 112086
NOV 16TH, 7:39PM
Hi Duane. Thank you for all the details. We will get our team to follow up on this query for you. Thank you.^ID
NOV 17TH, 10:05AM
Please supply reference. Service staff must phone ********** 920 for entrance to property. Took +-5min took open FB to message you. See test results I just ran. SUMMARY
Test Name: Google Websites HTTP Latency Test
Test ID: 9
Test result: Problem detected
CRITERIA
Average HTTP latency time (ms) benchmark under which a no problem verdict is rendered: 400
Average HTTP latency time (ms) benchmark between which a potential problem verdict is rendered: 400-500
Average HTTP latency time (ms) benchmark above which a problem verdict is rendered: 500
DETAILS
Thu Nov 17 2016 10:00:23 GMT+0200 (South Africa Standard Time) - Setting TCP timeout length (msec): 10000
Thu Nov 17 2016 10:00:23 GMT+0200 (South Africa Standard Time) - Creating a TCP socket, number / host / port: 26 / fslffetj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - TCP connection established with host / port / status code: fslffetj-ccd-testing-v4.metric.gstatic.com / 80 / 0
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - TCP connection established successfully with host / port: fslffetj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - Preparing to send data with size (bytes): 232
Thu Nov 17 2016 10:00:25 GMT+0200 (South Africa Standard Time) - Successfully sent data with size (bytes): 232
Thu Nov 17 2016 10:00:26 GMT+0200 (South Africa Standard Time) - Successfully read data from TCP socket with size (bytes): 102
Thu Nov 17 2016 10:00:26 GMT+0200 (South Africa Standard Time) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Thu, 17 Nov 2016 08:00:25 GMT
Connection: close
Thu Nov 17 2016 10:00:26 GMT+0200 (South Africa Standard Time) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 0 / ********** 626073 / 2488
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Setting TCP timeout length (msec): 10000
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Creating a TCP socket, number / host / port: 28 / stskxrtj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - TCP connection established with host / port / status code: stskxrtj-ccd-testing-v4.metric.gstatic.com / 80 / 0
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - TCP connection established successfully with host / port: stskxrtj-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Preparing to send data with size (bytes): 232
Thu Nov 17 2016 10:00:32 GMT+0200 (South Africa Standard Time) - Successfully sent data with size (bytes): 232
Thu Nov 17 2016 10:00:33 GMT+0200 (South Africa Standard Time) - Successfully read data from TCP socket with size (bytes): 102
Thu Nov 17 2016 10:00:33 GMT+0200 (South Africa Standard Time) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Thu, 17 Nov 2016 08:00:33 GMT
Connection: close
Thu Nov 17 2016 10:00:33 GMT+0200 (South Africa Standard Time) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 1 / ********** 633225 / 921
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Setting TCP timeout length (msec): 10000
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Creating a TCP socket, number / host / port: 30 / duagcfip-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - TCP connection established with host / port / status code: duagcfip-ccd-testing-v4.metric.gstatic.com / 80 / 0
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - TCP connection established successfully with host / port: duagcfip-ccd-testing-v4.metric.gstatic.com / 80
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Preparing to send data with size (bytes): 232
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Successfully sent data with size (bytes): 232
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Successfully read data from TCP socket with size (bytes): 102
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Received raw data from TCP socket: HTTP/1.1 204 No Content
Content-Length: 0
Date: Thu, 17 Nov 2016 08:00:36 GMT
Connection: close
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - HTTP response # / time received (microtimestamp) / elapsed time(ms): 2 / ********** 636167 / 153
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Total HTTP response time (ms): 3562
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Total number of HTTP requests: 3
Thu Nov 17 2016 10:00:36 GMT+0200 (South Africa Standard Time) - Average HTTP response time (ms): 1187.33
NOV 17TH, 1:38PM
Hi, thanks for your details will have our team follow-up & advise ^JD
your REF for this query is : AI ********** ^JD
Thanks
NOV 17TH, 3:14PM
Hi Duane, you welcome.^TM
NOV 17TH, 5:15PM
Good day Duane
Please be advised this is an update on your query, we would firstly like to apologise for the inconvenience caused, kindly note we have escalated your query to our technical team to assist and provide feedback accordingly.^BP
NOV 17TH, 6:51PM
Great thanks
NOV 20TH, 2:40PM
Still no contact from your technical team for AI ********** . Last time I had a network issue it took 2 years to fix. Do I have to go the same route again?
SUMMARY
Test Name: Resolver Present Test
Test ID: 3
Test result: Problem detected
CRITERIA
DNS resolver test performs a single DNS query and returns a failing result if a valid response is not returned.
DNS resolver test performs a single DNS query and returns a passing result if a valid response is returned.
DETAILS
Sun Nov 20 2016 14:51:24 GMT+0200 (South Africa Standard Time) - Attempting to resolve hostname: ccd-testing-v4.gstatic.com
Sun Nov 20 2016 14:51:24 GMT+0200 (South Africa Standard Time) - DNS server returned DNS query results.
Sun Nov 20 2016 14:51:24 GMT+0200 (South Africa Standard Time) - DNS server returned problem status code: -105
NOV 20TH, 8:12PM
hi,apologies for the delayed response.Our technical team are attending to a case related to the network and further correspondence will follow.^WC
NOV 21ST, 9:23AM
Telkom is responding to your comment: "It took Telkom 2 years to resolve a similar problem ..."
Hi Duene, we humbly do apologise for the delay. Please kindly note that your query has been sent to our mobile team feedback will be provided. ^LKE
Predict the fastest race time for this years Telkom 947 Cycle Challenge and you could win data prizes to keep you speeding along online! Ts&Cs apply. #CC2016
Facebook
NOV 23RD, 6:46AM
Please advice on the next action to take. Urgently
Hi Duane, Your query is in hand with our mobile team for investigation.^BD
When will I get some tangible feedback? I thought it was with a manager? Come guys
NOV 23RD, 9:29AM
Hi,your query is currently at our mobile team with reference AI ********** and they will be in contact,sorry for the inconvenience.^LA
DEC 1ST, 11:53AM
Its now the 1 Nov and you have done absolutely nothing. A month already. Maybe you should employ technicians and managers that know how to deliver services to your customers who actually pay your salaries
DEC 1ST, 4:46PM
Hi Duane ,please accept our apologies for the delay that have been caused,we will follow up with our support team and get back to you.^LK
WED 12:43PM