so when is the Beta version ready?
Well.
So far I've made a 'Start' button. Doesn't do anything yet... but at least I can tap it.
So give me another hour
Z
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How do you normally pay for purchases in stores?
"Is it my Line" Report Tool
- Thread starter Zertop
- Start date
Well.
So far I've made a 'Start' button. Doesn't do anything yet... but at least I can tap it.
So give me another hour
Z
Icemanbrfc
Honorary Master
Lol all goodWell.
So far I've made a 'Start' button. Doesn't do anything yet... but at least I can tap it.
So give me another hour
Z
Android
For anybody interested
https://github.com/Zertop/LineToolAndroid/releases/tag/V0.1
Download the APK here: https://github.com/Zertop/LineToolAndroid/releases/download/V0.1/LineTool.Android.apk
Doing this purely to experiment haha. I hope it works!
Z
For anybody interested
https://github.com/Zertop/LineToolAndroid/releases/tag/V0.1
Download the APK here: https://github.com/Zertop/LineToolAndroid/releases/download/V0.1/LineTool.Android.apk
Doing this purely to experiment haha. I hope it works!
Z
Icemanbrfc
Honorary Master
Not working Zertop. I keep getting the same result
Apologies, was taking a bit of a break!
I know what the issue is. Let me see what I can do!
Z
Icemanbrfc
Honorary Master
Apologies, was taking a bit of a break!
I know what the issue is. Let me see what I can do!
Z
okay cool. I like that my ping is coming in at 6700ms 
thomascmyk
Well-Known Member
i know this might seem dumb, but how do I go about using this tool? 
wingnut771
Honorary Master
i know this might seem dumb, but how do I go about using this tool?
download java
thomascmyk
Well-Known Member
Thank you!
Can anyone comment on this:
Zertop's LineTool Results
Date/Time: Thu Jan 28 19:00:36 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 32ms.
Your maximum ping was 97ms.
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=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=97ms TTL=63
Reply from 155.239.255.250: bytes=32 time=43ms 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=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms 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 = 22ms, Maximum = 97ms, Average = 32msThank you!
Can anyone comment on this:
Zertop's LineTool Results
Date/Time: Thu Jan 28 19:00:36 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 32ms.
Your maximum ping was 97ms.
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=89ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=35ms TTL=63 Reply from 155.239.255.250: bytes=32 time=24ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=96ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=51ms TTL=63 Reply from 155.239.255.250: bytes=32 time=97ms TTL=63 Reply from 155.239.255.250: bytes=32 time=43ms 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=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms 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 = 22ms, Maximum = 97ms, Average = 32ms
Looks Good !
Mine:
Zertop's LineTool Results
Date/Time: Thu Jan 28 19:11:38 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 42ms.
Your maximum ping was 140ms.
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=43ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=140ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms 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 = 35ms, Maximum = 140ms, Average = 42ms
Code:
Adsl Line Status SHOWTIME.L0
Adsl Mode G992.5
Up Stream 947 kbps
Down Stream 10239 kbps
Attenuation Down Stream 27
Attenuation Up Stream 17
SNR Margin Down Stream 12.6
SNR Margin Up Stream 13.2
Vendor ID RETK
Firmware Version 4926dc02
CRC Errors 0
Up Stream BER 0e-7
Down Stream BER 0e-7
Up Output Power 12
Down Output Power 20
Down Stream ES 1044
Up Stream ES 0
Down Stream SES 164
Up Stream SES 0
Down Stream UAS 95423
Up Stream UAS 0
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert www.google.co.za
Tracing route to www.google.co.za [216.58.223.35]
over a maximum of 30 hops:
1 2 ms 3 ms 5 ms 192.168.0.1
2 * * * Request timed out.
3 41 ms 37 ms 39 ms 41.193.164.85
4 40 ms 44 ms 41 ms 41.193.164.86
5 40 ms 39 ms 40 ms 41.193.164.92
6 43 ms 45 ms 41 ms 41.193.119.85
7 41 ms 39 ms 39 ms 41.193.119.90
8 40 ms 40 ms 38 ms 72.14.220.136
9 40 ms 47 ms 45 ms 72.14.239.129
10 43 ms 39 ms 41 ms jnb01s08-in-f3.1e100.net [216.58.223.35]
Trace complete.
C:\WINDOWS\system32>tracert www.google.com
Tracing route to www.google.com [216.58.223.36]
over a maximum of 30 hops:
1 2 ms 3 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 41 ms 39 ms 46 ms 41.193.164.85
4 39 ms 42 ms 39 ms 41.193.164.86
5 40 ms 41 ms 40 ms 41.193.164.92
6 53 ms 41 ms 41 ms 41.193.119.85
7 43 ms 43 ms 40 ms 41.193.119.90
8 41 ms 40 ms 39 ms 72.14.220.136
9 40 ms 40 ms 46 ms 72.14.239.129
10 42 ms 41 ms 41 ms jnb01s08-in-f4.1e100.net [216.58.223.36]
Trace complete.
C:\WINDOWS\system32>tracert 155.239.255.250
Tracing route to 155.239.255.250 over a maximum of 30 hops
1 2 ms 3 ms 1 ms 192.168.0.1
2 71 ms 38 ms 37 ms 155.239.255.250
Trace complete.
C:\WINDOWS\system32>wingnut771
Honorary Master
Thank you!
Can anyone comment on this:
Zertop's LineTool Results
Date/Time: Thu Jan 28 19:00:36 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 32ms.
Your maximum ping was 97ms.
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=89ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=35ms TTL=63 Reply from 155.239.255.250: bytes=32 time=24ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=96ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=51ms TTL=63 Reply from 155.239.255.250: bytes=32 time=97ms TTL=63 Reply from 155.239.255.250: bytes=32 time=43ms 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=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms TTL=63 Reply from 155.239.255.250: bytes=32 time=23ms 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 = 22ms, Maximum = 97ms, Average = 32ms
No problem
To eliminate network activity fudging the results, disable wifi and test with an idle network, if still faulty, connect with an alternate backbone ISP and leave connected a few hours and test around same time original problem appears, if still an issue then it's line/exchange, probably exchange if it's only sometimes and line if all the time.
This is how it should look like:
Zertop's LineTool Results
Date/Time: Thu Jan 28 20:53:26 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 13ms.
Your maximum ping was 22ms.
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=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms 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 = 13ms, Maximum = 22ms, Average = 13msatomcrusher
Expert Member
Using Zertop's Line Tool (latest version - I updated today) I get the following result:
(it's the best result I have seen in a while )
Zertop's LineTool Results
Date/Time: Wed Feb 17 11:15:12 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 14ms.
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:
(it's the best result I have seen in a while
)Zertop's LineTool Results
Date/Time: Wed Feb 17 11:15:12 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 14ms.
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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms 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 = 12ms, Maximum = 14ms, Average = 12ms
KamikazeHamster
Well-Known Member
Zertop's LineTool Results
Date/Time: Wed Feb 17 15:30:50 CAT 2016
Basic Report:
Your packet loss was 20%.
Your average ping was 35ms.
Your maximum ping was 43ms.
You seem to have some packet loss. This indicates an issue on the line.
Detailed Report:
Date/Time: Wed Feb 17 15:30:50 CAT 2016
Basic Report:
Your packet loss was 20%.
Your average ping was 35ms.
Your maximum ping was 43ms.
You seem to have some packet loss. This indicates an issue on the line.
Detailed Report:
Code:
Pinging 169.0.12.1 with 32 bytes of data:
Request timed out.
Reply from 169.0.12.1: bytes=32 time=27ms TTL=254
Request timed out.
Reply from 169.0.12.1: bytes=32 time=43ms TTL=254
Reply from 169.0.12.1: bytes=32 time=30ms TTL=254
Request timed out.
Reply from 169.0.12.1: bytes=32 time=35ms TTL=254
Reply from 169.0.12.1: bytes=32 time=37ms TTL=254
Reply from 169.0.12.1: bytes=32 time=29ms TTL=254
Reply from 169.0.12.1: bytes=32 time=40ms TTL=254
Reply from 169.0.12.1: bytes=32 time=38ms TTL=254
Reply from 169.0.12.1: bytes=32 time=39ms TTL=254
Reply from 169.0.12.1: bytes=32 time=31ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.12.1: bytes=32 time=29ms TTL=254
Reply from 169.0.12.1: bytes=32 time=42ms TTL=254
Reply from 169.0.12.1: bytes=32 time=39ms TTL=254
Reply from 169.0.12.1: bytes=32 time=38ms TTL=254
Reply from 169.0.12.1: bytes=32 time=41ms TTL=254
Reply from 169.0.12.1: bytes=32 time=42ms TTL=254
Reply from 169.0.12.1: bytes=32 time=30ms TTL=254
Reply from 169.0.12.1: bytes=32 time=32ms TTL=254
Reply from 169.0.12.1: bytes=32 time=41ms TTL=254
Reply from 169.0.12.1: bytes=32 time=28ms TTL=254
Reply from 169.0.12.1: bytes=32 time=34ms TTL=254
Request timed out.
Reply from 169.0.12.1: bytes=32 time=30ms TTL=254
Reply from 169.0.12.1: bytes=32 time=29ms TTL=254
Reply from 169.0.12.1: bytes=32 time=36ms TTL=254
Ping statistics for 169.0.12.1:
Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 43ms, Average = 35ms
EnderZaMan
Well-Known Member
Zertop's LineTool Results
Date/Time: Thu Feb 18 11:11:56 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 40ms.
Your maximum ping was 68ms.
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:
Date/Time: Thu Feb 18 11:11:56 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 40ms.
Your maximum ping was 68ms.
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=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=53ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=68ms TTL=63
Reply from 155.239.255.250: bytes=32 time=30ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=29ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=30ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms 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 = 15ms, Maximum = 68ms, Average = 40msFrom this..
To This..
Zertop's LineTool Results
Date/Time: Thu Feb 18 23:49:28 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 391ms.
Your maximum ping was 1753ms.
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:
To This..
Zertop's LineTool Results
Date/Time: Thu Feb 18 23:49:28 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 391ms.
Your maximum ping was 1753ms.
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=501ms TTL=63
Reply from 155.239.255.250: bytes=32 time=224ms TTL=63
Reply from 155.239.255.250: bytes=32 time=285ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1111ms TTL=63
Reply from 155.239.255.250: bytes=32 time=647ms TTL=63
Reply from 155.239.255.250: bytes=32 time=214ms TTL=63
Reply from 155.239.255.250: bytes=32 time=308ms TTL=63
Reply from 155.239.255.250: bytes=32 time=56ms TTL=63
Reply from 155.239.255.250: bytes=32 time=717ms TTL=63
Reply from 155.239.255.250: bytes=32 time=199ms TTL=63
Reply from 155.239.255.250: bytes=32 time=299ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=373ms TTL=63
Reply from 155.239.255.250: bytes=32 time=506ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1753ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1044ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=141ms TTL=63
Reply from 155.239.255.250: bytes=32 time=271ms TTL=63
Reply from 155.239.255.250: bytes=32 time=298ms TTL=63
Reply from 155.239.255.250: bytes=32 time=212ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=682ms TTL=63
Reply from 155.239.255.250: bytes=32 time=91ms TTL=63
Reply from 155.239.255.250: bytes=32 time=193ms TTL=63
Reply from 155.239.255.250: bytes=32 time=229ms TTL=63
Reply from 155.239.255.250: bytes=32 time=290ms TTL=63
Reply from 155.239.255.250: bytes=32 time=351ms TTL=63
Reply from 155.239.255.250: bytes=32 time=437ms TTL=63
Reply from 155.239.255.250: bytes=32 time=170ms 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 = 24ms, Maximum = 1753ms, Average = 391ms
Code:
TOTO LINK ND300
23H47
Adsl Line Status SHOWTIME.L0
Adsl Mode G992.5
Up Stream 508 kbps
Down Stream 7167 kbps
Attenuation Down Stream 27
Attenuation Up Stream 17
SNR Margin Down Stream 19.0
SNR Margin Up Stream 24.4
Vendor ID RETK
Firmware Version 4926dc02
CRC Errors 151
Up Stream BER 0e-7
Down Stream BER 0e-7
Up Output Power 12
Down Output Power 20
Down Stream ES 55
Up Stream ES 0
Down Stream SES 0
Up Stream SES 0
Down Stream UAS 0
Up Stream UAS 0
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert 155.239.255.250
Tracing route to 155.239.255.250 over a maximum of 30 hops
1 2167 ms 1063 ms 2 ms 192.168.1.1
2 722 ms 115 ms 48 ms 155.239.255.250
Trace complete.
C:\WINDOWS\system32>tracert www.google.co.za
Tracing route to www.google.co.za [216.58.223.35]
over a maximum of 30 hops:
1 9 ms 6 ms 5 ms 192.168.1.1
2 * * * Request timed out.
3 195 ms 43 ms 472 ms 41.193.164.85
4 287 ms 186 ms 210 ms 41.193.164.86
5 29 ms 28 ms 28 ms 41.193.164.92
6 192.168.1.1 reports: Destination net unreachable.
Trace complete.
C:\WINDOWS\system32>tracert www.google.co.za
Tracing route to www.google.co.za [216.58.223.35]
over a maximum of 30 hops:
1 3 ms 4 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 26 ms 34 ms 26 ms 41.193.164.85
4 65 ms 30 ms 26 ms 41.193.164.86
5 30 ms 29 ms 26 ms 41.193.164.92
6 27 ms 30 ms 55 ms 41.193.119.85
7 26 ms 28 ms 26 ms 41.193.119.90
8 27 ms 30 ms 26 ms 72.14.220.136
9 31 ms 34 ms 28 ms 72.14.239.129
10 36 ms 29 ms 31 ms jnb01s08-in-f3.1e100.net [216.58.223.35]
Trace complete.
C:\WINDOWS\system32>tracert www.google.com
Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:
1 4 ms 1 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 26 ms 31 ms 26 ms 41.193.164.85
4 28 ms 26 ms 27 ms 41.193.164.86
5 42 ms 37 ms 33 ms 41.193.164.92
6 29 ms 27 ms 31 ms 41.193.119.85
7 38 ms 29 ms 36 ms 41.193.119.90
8 26 ms 30 ms 26 ms 72.14.220.136
9 29 ms 27 ms 27 ms 72.14.237.239
10 29 ms 28 ms 28 ms jnb01s07-in-f4.1e100.net [216.58.223.4]
Trace complete.
C:\WINDOWS\system32>tracert 155.239.255.250
Tracing route to 155.239.255.250 over a maximum of 30 hops
1 2 ms 3 ms 2 ms 192.168.1.1
2 26 ms 29 ms 24 ms 155.239.255.250
Trace complete.KamikazeHamster
Well-Known Member
So we're all just struggling, but it looks like nobody is listening that knows how to fix it 
So we're all just struggling, but it looks like nobody is listening that knows how to fix it
Telkom has to fix unfortunately
A few good results, a few bad results. Unfortunately - the only option you have is to log a Telkom fault (either through your ISP if they manage your line, or through Telkom directly) :/
If you ask for a port reset to be done, you might see improvements quite quickly. Otherwise, my personal favourite is to go to your local Telkom office and ask about any exchange issues. That way, you are speaking directly to the ones in charge of your area as opposed to speaking to somebody in a call centre. Although the call centre people are helpful (once you finally get hold of them), speaking directly to someone often yields better results
Also check for the following,
- If it happens in the evenings and mornings only:
Exchange Congestion
- If it is a constant problem no matter time of day
Line Erosion/Faulty port on exchange
- If it is a one time thing
Probably a temporary fault at the exchange.
Once again, apologies for the absence
Z
If you ask for a port reset to be done, you might see improvements quite quickly. Otherwise, my personal favourite is to go to your local Telkom office and ask about any exchange issues. That way, you are speaking directly to the ones in charge of your area as opposed to speaking to somebody in a call centre. Although the call centre people are helpful (once you finally get hold of them), speaking directly to someone often yields better results
Also check for the following,
- If it happens in the evenings and mornings only:
Exchange Congestion
- If it is a constant problem no matter time of day
Line Erosion/Faulty port on exchange
- If it is a one time thing
Probably a temporary fault at the exchange.
Once again, apologies for the absence
Z
Zertop's LineTool Results
Date/Time: Wed Feb 24 13:00:43 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 140ms.
Your maximum ping was 441ms.
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:
So is it my line?
Date/Time: Wed Feb 24 13:00:43 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 140ms.
Your maximum ping was 441ms.
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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms TTL=63
Reply from 155.239.255.250: bytes=32 time=57ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=434ms TTL=63
Reply from 155.239.255.250: bytes=32 time=173ms TTL=63
Reply from 155.239.255.250: bytes=32 time=441ms TTL=63
Reply from 155.239.255.250: bytes=32 time=151ms TTL=63
Reply from 155.239.255.250: bytes=32 time=73ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=86ms TTL=63
Reply from 155.239.255.250: bytes=32 time=434ms TTL=63
Reply from 155.239.255.250: bytes=32 time=202ms TTL=63
Reply from 155.239.255.250: bytes=32 time=441ms TTL=63
Reply from 155.239.255.250: bytes=32 time=160ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=57ms TTL=63
Reply from 155.239.255.250: bytes=32 time=74ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=365ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms TTL=63
Reply from 155.239.255.250: bytes=32 time=420ms TTL=63
Reply from 155.239.255.250: bytes=32 time=73ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=98ms 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 = 10ms, Maximum = 441ms, Average = 140msSo is it my line?