-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Have you ever ordered a product online and received a fake knock-off?
"Is it my Line" Report Tool
- Thread starter Zertop
- Start date
EchoZA
Expert Member
Pretty flawless actually! Abnormally high, but stable. Are you experiencing issues?
Z
Just that it's supposed to be a 10Mb line
but have 6 down and 1 up.Just that it's supposed to be a 10Mb line
Hmm okay. It might be that there is some form of limiting happening somewhere (which would explain the high, but stable, pings. What does Telkom say when you ask?
Z
EchoZA
Expert Member
Hmm okay. It might be that there is some form of limiting happening somewhere (which would explain the high, but stable, pings. What does Telkom say when you ask?
Z
The usual Telkom, but got home today and all of a sudden back to a 10Mb line (might have been the suggestion I made about putting 220v through their line
) will post new results soon.
EchoZA
Expert Member
Zertop's LineTool Results
Date/Time: Fri Apr 29 18:39:42 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 8ms.
Your maximum ping was 19ms.
Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP
Detailed Report:
Date/Time: Fri Apr 29 18:39:42 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 8ms.
Your maximum ping was 19ms.
Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 19ms, Average = 8msEchoZA
Expert Member
First off thanks for all the good info on the forums.
My ISP is mweb and I have been with them for the past 6 years and I have been happy or just extremely lucky running on a 4meg uncapped. Telkom exchange is less that 1km.
I need some help - telkom keeps on telling me there is nothing wrong everything is perfect... and I keep on telling them there is something seriously wrong somewhere.
I have been getting insane lag with online gaming (funny enough Sunday night I thought everything was perfect after logging yet another line fault Sunday morning and seeing telkom working on the exchange that afternoon just to find out Monday evening its better just to switch off the pc and have a beer) and before using the linetool I did a couple of speedtest from saix/mweb/mbb with some results being what expect but then just to get another one "what the fudge" and I tried explaining this the telkom call center but ja i am still waiting for the tech -
Its basically gotten to point were i am seriously considering stopping the dsl/telephone service and move to LTE (100/100gig) or WIFI- just not sure about WIFI quality in Bloemfontein.
[/URL][/IMG]
[/URL][/IMG]
[/URL][/IMG]
Zertop's LineTool Results
Date/Time: Wed May 04 19:11:38 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 29ms.
Your maximum ping was 635ms.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.
Detailed Report:
Thanks for the knowledge shared
My ISP is mweb and I have been with them for the past 6 years and I have been happy or just extremely lucky running on a 4meg uncapped. Telkom exchange is less that 1km.
I need some help - telkom keeps on telling me there is nothing wrong everything is perfect... and I keep on telling them there is something seriously wrong somewhere.
I have been getting insane lag with online gaming (funny enough Sunday night I thought everything was perfect after logging yet another line fault Sunday morning and seeing telkom working on the exchange that afternoon just to find out Monday evening its better just to switch off the pc and have a beer) and before using the linetool I did a couple of speedtest from saix/mweb/mbb with some results being what expect but then just to get another one "what the fudge" and I tried explaining this the telkom call center but ja i am still waiting for the tech -
Its basically gotten to point were i am seriously considering stopping the dsl/telephone service and move to LTE (100/100gig) or WIFI- just not sure about WIFI quality in Bloemfontein.
Zertop's LineTool Results
Date/Time: Wed May 04 19:11:38 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 29ms.
Your maximum ping was 635ms.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=635ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 635ms, Average = 29msThanks for the knowledge shared
First off thanks for all the good info on the forums.
My ISP is mweb and I have been with them for the past 6 years and I have been happy or just extremely lucky running on a 4meg uncapped. Telkom exchange is less that 1km.
I need some help - telkom keeps on telling me there is nothing wrong everything is perfect... and I keep on telling them there is something seriously wrong somewhere.
I have been getting insane lag with online gaming (funny enough Sunday night I thought everything was perfect after logging yet another line fault Sunday morning and seeing telkom working on the exchange that afternoon just to find out Monday evening its better just to switch off the pc and have a beer) and before using the linetool I did a couple of speedtest from saix/mweb/mbb with some results being what expect but then just to get another one "what the fudge" and I tried explaining this the telkom call center but ja i am still waiting for the tech -
Its basically gotten to point were i am seriously considering stopping the dsl/telephone service and move to LTE (100/100gig) or WIFI- just not sure about WIFI quality in Bloemfontein.
[/URL][/IMG]
[/URL][/IMG]
[/URL][/IMG]
Zertop's LineTool Results
Date/Time: Wed May 04 19:11:38 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 29ms.
Your maximum ping was 635ms.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.
Detailed Report:
Code:Pinging 155.239.255.250 with 32 bytes of data: Reply from 155.239.255.250: bytes=32 time=635ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=12ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=13ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=13ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=11ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=12ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=8ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Ping statistics for 155.239.255.250: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 635ms, Average = 29ms
Thanks for the knowledge shared
Hi There!
From your line stats, it might look as if everything is fine. However from your test results, there is definitely an underlying issue which seems to be present.
Do you notice these symptoms coming through mostly at specific times during the day (such as evenings etc). That might indicate exchange congestion.
Thanks,
Z
Geoff.D
Honorary Master
Try and determine if there is a time of day issue involved. What about the line diagnostics available on your router ( SNR etc)? What do they look like.
I doubt the problem is with the physical ADSL line but deeper into the network, maybe some exchange congestion or another network issue.
Right now we are all experiencing sub optimal performance.
There are definitely network issues at the moment affecting most of us.
I doubt the problem is with the physical ADSL line but deeper into the network, maybe some exchange congestion or another network issue.
Right now we are all experiencing sub optimal performance.
There are definitely network issues at the moment affecting most of us.
Hi There!
From your line stats, it might look as if everything is fine. However from your test results, there is definitely an underlying issue which seems to be present.
Do you notice these symptoms coming through mostly at specific times during the day (such as evenings etc). That might indicate exchange congestion.
Thanks,
Z
early mornings its fine and as the day goes on it goes downhill, i just did a speed test again and all good and did it again and then it timed out...
Download Speed: 3417 kbps (427.1 KB/sec transfer rate)
Upload Speed: 395 kbps (49.4 KB/sec transfer rate)
Latency: 36 ms
Jitter: 1 ms
5/4/2016, 9:06:50 PM
And after the speed test time out the line test showed the following results
B]Zertop's LineTool Results
Date/Time: Wed May 04 21:12:14 CAT 2016[/B]
Basic Report:
Your packet loss was 0%.
Your average ping was 37ms.
Your maximum ping was 425ms.
Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=274ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=425ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=129ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 425ms, Average = 37msLooks better now, but still not perfect.
From those results, I feel exchange congestion might be the culprit. Have you asked Telkom to check the exchange for congestion? Otherwise, sometimes a port reset/move might fix these issues.
If possible, trying asking around your neighbourhood if anybody is experiencing anything similar.
Z
At peak hours, 8-10pm, our 10Mbps line goes to 50-500Kbps. I'm suspecting exchange congestion...
Zertop's LineTool Results
Date/Time: Thu May 05 22:06:21 CAT 2016
Basic Report:
Your packet loss was 10%.
Your average ping was 292ms.
Your maximum ping was 502ms.
You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Zertop's LineTool Results
Date/Time: Thu May 05 22:06:21 CAT 2016
Basic Report:
Your packet loss was 10%.
Your average ping was 292ms.
Your maximum ping was 502ms.
You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=349ms TTL=63
Reply from 155.239.255.250: bytes=32 time=384ms TTL=63
Reply from 155.239.255.250: bytes=32 time=367ms TTL=63
Reply from 155.239.255.250: bytes=32 time=502ms TTL=63
Reply from 155.239.255.250: bytes=32 time=310ms TTL=63
Reply from 155.239.255.250: bytes=32 time=389ms TTL=63
Reply from 155.239.255.250: bytes=32 time=301ms TTL=63
Reply from 155.239.255.250: bytes=32 time=186ms TTL=63
Reply from 155.239.255.250: bytes=32 time=184ms TTL=63
Reply from 155.239.255.250: bytes=32 time=348ms TTL=63
Reply from 155.239.255.250: bytes=32 time=413ms TTL=63
Reply from 155.239.255.250: bytes=32 time=357ms TTL=63
Reply from 155.239.255.250: bytes=32 time=371ms TTL=63
Reply from 155.239.255.250: bytes=32 time=362ms TTL=63
Reply from 155.239.255.250: bytes=32 time=239ms TTL=63
Reply from 155.239.255.250: bytes=32 time=397ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=389ms TTL=63
Reply from 155.239.255.250: bytes=32 time=355ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=144ms TTL=63
Reply from 155.239.255.250: bytes=32 time=161ms TTL=63
Reply from 155.239.255.250: bytes=32 time=211ms TTL=63
Reply from 155.239.255.250: bytes=32 time=228ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=307ms TTL=63
Reply from 155.239.255.250: bytes=32 time=295ms TTL=63
Reply from 155.239.255.250: bytes=32 time=280ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 502ms, Average = 292msApologies, only saw this now. Yes, definitely looks like exchange congestion... especially if it only pops up during peak hours :/
Z
EchoZA
Expert Member
Zertop's LineTool Results
Date/Time: Sat May 21 14:22:18 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 87ms.
Your maximum ping was 402ms.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Date/Time: Sat May 21 14:22:18 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 87ms.
Your maximum ping was 402ms.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=250ms TTL=63
Reply from 155.239.255.250: bytes=32 time=382ms TTL=63
Reply from 155.239.255.250: bytes=32 time=384ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=241ms TTL=63
Reply from 155.239.255.250: bytes=32 time=389ms TTL=63
Reply from 155.239.255.250: bytes=32 time=402ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 402ms, Average = 87msEchoZA
Expert Member
A bit of variation there... are you seeing slow speeds?
Z
I'm 110% sure it's an overloaded exchange.
Definitely looks like it!
Have you tried asking your local telkom store if they know about it?
Z
Hi Devo!
That's odd! With 100% packet loss, I'm inclined to believe that the app failed at some point. If you do a speedtest on speedtest.net, what do your results show?
Z