-
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
You might really have intense packet loss then, hence it showing 100%. It's possible that the rain last night came into contact with the copper running to your house, hence causing these speeds.
Best advice I can give is to request a port reset from telkom (will not fix anything if it is indeed the rain), otherwise report a fault.
Z
Thanks! I believe that can be the case. Been raining for 2 days here.
Telkom already did a port reset. Nothing changed. Logged a fault last night and this morning it was closed as resolved but with no results.
Telkom already did a port reset. Nothing changed. Logged a fault last night and this morning it was closed as resolved but with no results.
Visit your local telkom store as opposed to using the hotline. They can often offer better assistance
Zertop's LineTool Results
Date/Time: Sat Jun 18 22:30:02 SAST 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 45ms.
Your maximum ping was 167ms.
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: Sat Jun 18 22:30:02 SAST 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 45ms.
Your maximum ping was 167ms.
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:
PING 155.239.255.250 (155.239.255.250) 56(84) bytes of data.
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=57.1 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=36.9 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=35.2 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=102 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=77.6 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=32.0 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=167 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=28.4 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=30.0 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=32.7 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=38.2 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=38.6 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=37.6 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=27.4 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=61.1 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=39.1 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=38.5 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=35.1 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=38.3 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=38.4 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=33.5 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=37.4 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=35.8 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=37.8 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=36.8 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=32.2 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=38.1 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=34.8 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=52.1 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=63 time=37.8 ms
--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29161ms
rtt min/avg/max/mdev = 27.432/45.649/167.129/27.167 msPing looks quite high. Is your line showing slowdowns?
It's probably the rain unfortunately. Try chatting to your neighbours to see if they're having similar issues
If so, it would be best to report a fault to Telkom. First get them to do a port reset, just in case, though.
LaraC
Honorary Master
- Joined
- Mar 11, 2014
- Messages
- 42,673
- Reaction score
- 1,847
Hi Zertop,
Are you going to add speed test functionality again in newer versions?
Zertop's LineTool Results
Date/Time: Sun Jun 19 17:48:21 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 6ms.
Your maximum ping was 7ms.
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:
Are you going to add speed test functionality again in newer versions?
Zertop's LineTool Results
Date/Time: Sun Jun 19 17:48:21 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 6ms.
Your maximum ping was 7ms.
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=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms 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=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms 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=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms 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=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms 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=6ms 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 = 7ms, Average = 6msIt's probably the rain unfortunately. Try chatting to your neighbours to see if they're having similar issues
If so, it would be best to report a fault to Telkom. First get them to do a port reset, just in case, though.
I will try the neighbours but i dont get my hopes tooooo high.
I have logged 3x cases as the first two the closed saying its resolved....sigh
The have done a port reset and made zero difference. I am also thinking about the rain, guess nothing can be done about that??? Why now, its rained plenty before with no issue
Cables sometimes wear thin over time, unfortunately :/ Have you tried a different ISP account to test if that makes any difference?
atomcrusher
Expert Member
I have a Telkom ISP "up to 4 Mbps" ADSL connection (the max my local exchange allows 
. Here's my latest result using Zertop's Line Tool
Zertop's LineTool Results
Date/Time: Sun Jul 10 08:55:47 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 27ms.
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:
. Here's my latest result using Zertop's Line ToolZertop's LineTool Results
Date/Time: Sun Jul 10 08:55:47 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 27ms.
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=12ms 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=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=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=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=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=12ms 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=27ms 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=12ms 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 = 27ms, Average = 12msI have a Telkom ISP "up to 4 Mbps" ADSL connection (the max my local exchange allows
Zertop's LineTool Results
Date/Time: Sun Jul 10 08:55:47 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
Your maximum ping was 27ms.
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=12ms 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=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=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=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=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=12ms 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=27ms 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=12ms 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 = 27ms, Average = 12ms
That looks great! Are you experiencing any issues?
Z
Im currently subscribed to Vox Telecom on their 4mbps uncapped package. Ping was fine until I hit the soft cap (50 GB i think) and then my speed gets halved. I'm fine with having half the speed but my ping shouldn't be affected right?
Zertop's LineTool Results
Date/Time: Fri Aug 12 14:40:36 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 168ms.
Your maximum ping was 401ms.
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: Fri Aug 12 14:40:36 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 168ms.
Your maximum ping was 401ms.
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 197.245.3.1 with 32 bytes of data:
Reply from 197.245.3.1: bytes=32 time=254ms TTL=254
Reply from 197.245.3.1: bytes=32 time=166ms TTL=254
Reply from 197.245.3.1: bytes=32 time=172ms TTL=254
Reply from 197.245.3.1: bytes=32 time=181ms TTL=254
Reply from 197.245.3.1: bytes=32 time=181ms TTL=254
Reply from 197.245.3.1: bytes=32 time=219ms TTL=254
Reply from 197.245.3.1: bytes=32 time=210ms TTL=254
Reply from 197.245.3.1: bytes=32 time=146ms TTL=254
Reply from 197.245.3.1: bytes=32 time=155ms TTL=254
Reply from 197.245.3.1: bytes=32 time=254ms TTL=254
Reply from 197.245.3.1: bytes=32 time=204ms TTL=254
Reply from 197.245.3.1: bytes=32 time=401ms TTL=254
Reply from 197.245.3.1: bytes=32 time=312ms TTL=254
Reply from 197.245.3.1: bytes=32 time=179ms TTL=254
Reply from 197.245.3.1: bytes=32 time=128ms TTL=254
Reply from 197.245.3.1: bytes=32 time=142ms TTL=254
Reply from 197.245.3.1: bytes=32 time=195ms TTL=254
Reply from 197.245.3.1: bytes=32 time=173ms TTL=254
Reply from 197.245.3.1: bytes=32 time=80ms TTL=254
Reply from 197.245.3.1: bytes=32 time=104ms TTL=254
Reply from 197.245.3.1: bytes=32 time=57ms TTL=254
Reply from 197.245.3.1: bytes=32 time=115ms TTL=254
Reply from 197.245.3.1: bytes=32 time=104ms TTL=254
Reply from 197.245.3.1: bytes=32 time=107ms TTL=254
Reply from 197.245.3.1: bytes=32 time=108ms TTL=254
Reply from 197.245.3.1: bytes=32 time=100ms TTL=254
Reply from 197.245.3.1: bytes=32 time=185ms TTL=254
Reply from 197.245.3.1: bytes=32 time=153ms TTL=254
Reply from 197.245.3.1: bytes=32 time=126ms TTL=254
Reply from 197.245.3.1: bytes=32 time=154ms TTL=254
Ping statistics for 197.245.3.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 401ms, Average = 168mswingnut771
Honorary Master
No, it shouldn't affect your ping.
Afrihost DSL Capped / Telkom 10 Mbps ADSL
DSL Stats:
Main Router
Zertop's LineTool Results
Date/Time: Fri Aug 12 19:25:17 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 37ms.
Your maximum ping was 91ms.
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:
Johannesburg
YOUR LATEST RESULTS
Last Result:
Download Speed: 8673 kbps (1084.1 KB/sec transfer rate)
Upload Speed: 786 kbps (98.3 KB/sec transfer rate)
Latency: 35 ms
Jitter: 23 ms
8/12/2016, 7:22:45 PM
Cape Town
Last Result:
Download Speed: 8216 kbps (1027 KB/sec transfer rate)
Upload Speed: 579 kbps (72.4 KB/sec transfer rate)
Latency: 52 ms
Jitter: 35 ms
8/12/2016, 7:24:02 PM
2nd Wi-Fi Router / Repeater
Zertop's LineTool Results
Date/Time: Fri Aug 12 19:15:02 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 69ms.
Your maximum ping was 123ms.
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:
Johannesburg
YOUR LATEST RESULTS
Last Result:
Download Speed: 2334 kbps (291.8 KB/sec transfer rate)
Upload Speed: 842 kbps (105.3 KB/sec transfer rate)
Latency: 36 ms
Jitter: 7 ms
8/12/2016, 7:18:12 PM
Cape Town
YOUR LATEST RESULTS
Last Result:
Download Speed: 2237 kbps (279.6 KB/sec transfer rate)
Upload Speed: 778 kbps (97.3 KB/sec transfer rate)
Latency: 53 ms
Jitter: 67 ms
8/12/2016, 7:20:22 PM
DSL Stats:
Code:
xdsl info expand=enabled
Physical Layer Statistics:
Modem state: up
Up time (Days hh:mm:ss): 0 days, 16:45:19
xDSL Standard: ITU-T G.992.5 Annex A (ADSL2+ over POTS)
xDSL Annex: Annex A
Channel Mode: Interleaved
Number of reset: 2
Chipset Vendor info (G.994.1): Local Remote
Country code: B500 B500
ID: BDCM BDCM
Specific: 0000 A41B
System Vendor info (showtime): Local Remote
Country code: 0F00 0000
ID: TMMB ----
Specific: 3C61 0000
Bearers generic info DS US
Payload rate [kbps]: 10239 1022
Attenuation [dB]: 25.5 14.9
Margins [dB]: 9.1 8.7
Output power [dBm]: 18.8 12.1
Number of bearers: 1
Bearer 0 DS US
INP [DMT symbols]: 8.38 3.39
Delay [ms]: 12.31 11.76
Depth []: 511 0.00
R: 16 0
G.997.1 Statistics (Current):
Failures:
Line failures Near end
Loss of signal (LOS): 2
Loss of frame (LOF): 18
Loss of power (LPR): 0
Performance monitoring:
Line PM: Near end
Error second (ES): 113
Channel PM: Near end Far end
Bearer 0:
Code Violation (CV): 315 767
FEC: 797791 18414
ATM data path PM: Near end Far end
Bearer 0:
HEC violation count (HEC): 7569 N/A
G.997.1 Statistics (last 15 minutes):
Failures:
Line failures Near end
Loss of signal (LOS): 0
Loss of frame (LOF): 0
Loss of power (LPR): 0
Performance monitoring:
Line PM: Near end
Error second (ES): 0
Channel PM: Near end Far end
Bearer 0:
Code Violation (CV): 315 767
FEC: 797791 18414
ATM data path PM: Near end Far end
Bearer 0:
HEC violation count (HEC): 7569 N/A
G.997.1 Statistics (last 24 hours):
Failures:
Line failures Near end
Loss of signal (LOS): 2
Loss of frame (LOF): 18
Loss of power (LPR): 0
Performance monitoring:
Line PM: Near end
Error second (ES): 113
Channel PM: Near end Far end
Bearer 0:
Code Violation (CV): 315 767
FEC: 797791 18414
ATM data path PM: Near end Far end
Bearer 0:
HEC violation count (HEC): 7569 N/A
{Administrator}=>Zertop's LineTool Results
Date/Time: Fri Aug 12 19:25:17 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 37ms.
Your maximum ping was 91ms.
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=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms 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=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=91ms TTL=63
Reply from 155.239.255.250: bytes=32 time=62ms 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=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=61ms 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=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms 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 = 31ms, Maximum = 91ms, Average = 37msJohannesburg
YOUR LATEST RESULTS
Last Result:
Download Speed: 8673 kbps (1084.1 KB/sec transfer rate)
Upload Speed: 786 kbps (98.3 KB/sec transfer rate)
Latency: 35 ms
Jitter: 23 ms
8/12/2016, 7:22:45 PM
Cape Town
Last Result:
Download Speed: 8216 kbps (1027 KB/sec transfer rate)
Upload Speed: 579 kbps (72.4 KB/sec transfer rate)
Latency: 52 ms
Jitter: 35 ms
8/12/2016, 7:24:02 PM
2nd Wi-Fi Router / Repeater
Zertop's LineTool Results
Date/Time: Fri Aug 12 19:15:02 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 69ms.
Your maximum ping was 123ms.
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=76ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=65ms TTL=63
Reply from 155.239.255.250: bytes=32 time=63ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms 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=85ms TTL=63
Reply from 155.239.255.250: bytes=32 time=80ms TTL=63
Reply from 155.239.255.250: bytes=32 time=97ms TTL=63
Reply from 155.239.255.250: bytes=32 time=91ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=67ms TTL=63
Reply from 155.239.255.250: bytes=32 time=75ms TTL=63
Reply from 155.239.255.250: bytes=32 time=66ms TTL=63
Reply from 155.239.255.250: bytes=32 time=55ms TTL=63
Reply from 155.239.255.250: bytes=32 time=61ms TTL=63
Reply from 155.239.255.250: bytes=32 time=90ms TTL=63
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=57ms TTL=63
Reply from 155.239.255.250: bytes=32 time=79ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=123ms TTL=63
Reply from 155.239.255.250: bytes=32 time=115ms TTL=63
Reply from 155.239.255.250: bytes=32 time=105ms 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 = 32ms, Maximum = 123ms, Average = 69msJohannesburg
YOUR LATEST RESULTS
Last Result:
Download Speed: 2334 kbps (291.8 KB/sec transfer rate)
Upload Speed: 842 kbps (105.3 KB/sec transfer rate)
Latency: 36 ms
Jitter: 7 ms
8/12/2016, 7:18:12 PM
Cape Town
YOUR LATEST RESULTS
Last Result:
Download Speed: 2237 kbps (279.6 KB/sec transfer rate)
Upload Speed: 778 kbps (97.3 KB/sec transfer rate)
Latency: 53 ms
Jitter: 67 ms
8/12/2016, 7:20:22 PM
F
Former member 61586
Guest
Line broken AGAIN.
Zertop's LineTool Results
Date/Time: Wed Aug 31 23:28:10 SAST 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 92ms.
Your maximum ping was 1355ms.
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: Wed Aug 31 23:28:10 SAST 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 92ms.
Your maximum ping was 1355ms.
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:
PING 155.239.255.250 (155.239.255.250) 56(84) bytes of data.
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=41.8 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=35.2 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=34.6 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=32.7 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=34.2 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=35.5 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=23.7 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=33.6 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=33.5 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=34.4 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=35.1 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=1355 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=355 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=70.0 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=49.7 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=45.3 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=57.1 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=34.4 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=52.9 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=49.5 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=34.3 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=34.3 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=30.6 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=35.8 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=34.7 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=32.4 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=36.0 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=34.9 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=35.3 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=63 time=23.0 ms
--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29754ms
rtt min/avg/max/mdev = 23.083/92.565/1355.165/241.476 ms, pipe 2ichocolate
Senior Member
- Joined
- Oct 17, 2011
- Messages
- 703
- Reaction score
- 18
10 meg on 9 meg profile test
This seems like a false positive to me because i tested an iso download from the is ftp site and i get 40 to 60 kb/s :
Zertop's LineTool Results
Date/Time: Thu Sep 22 22:20:44 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 5ms.
Your maximum ping was 7ms.
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:
I dont know what to do anymore.
Something is slowing my speed down. I download the same file just moments ago and really could not believe it, it was downloading at 950 odd kb/s
Note before i did the java test about it was a bad speed test like 4.9 and then max the needle was , was at 7.6.
Ping test was good though showing amazingly no jitter and only ping - quality B was given.
I rebooted the modem to run this test but before i did i downloaded a iso out of interest:
Then all of a sudden it went back to the mystery speed i have been having since they changed me to a 10 meg line from 4:
Its been reported but i might be talking to the wrong technician.
Anoying part is that you report a fault and you are told there is a line noise and then then tell you they will contact you later to tell you what speed you are connected at and tghey ask you to check how fast a website loads.
i mean flip.
The call gets closed and no dam resolution.
I have escalated this so hope something happens because it is ridiculous.
These are my details of my tp-link device page:
I have tested different RJ11 cables and also unplugged the phone and im running nothing else electrical near by.
Not sure what to do and who to talk to .
You either have the right person that will go out of their way to help you or you just struggle.
I also run the Zertop test - 3 of them which all include 2x the tracert results:
Zertop Results:
This seems like a false positive to me because i tested an iso download from the is ftp site and i get 40 to 60 kb/s :
Zertop's LineTool Results
Date/Time: Thu Sep 22 22:20:44 CAT 2016
Basic Report:
Your packet loss was 0%.
Your average ping was 5ms.
Your maximum ping was 7ms.
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=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms 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=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms 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 = 4ms, Maximum = 7ms, Average = 5msI dont know what to do anymore.
Something is slowing my speed down. I download the same file just moments ago and really could not believe it, it was downloading at 950 odd kb/s
Note before i did the java test about it was a bad speed test like 4.9 and then max the needle was , was at 7.6.
Ping test was good though showing amazingly no jitter and only ping - quality B was given.
I rebooted the modem to run this test but before i did i downloaded a iso out of interest:
Then all of a sudden it went back to the mystery speed i have been having since they changed me to a 10 meg line from 4:
Its been reported but i might be talking to the wrong technician.
Anoying part is that you report a fault and you are told there is a line noise and then then tell you they will contact you later to tell you what speed you are connected at and tghey ask you to check how fast a website loads.
i mean flip.
The call gets closed and no dam resolution.
I have escalated this so hope something happens because it is ridiculous.
These are my details of my tp-link device page:
I have tested different RJ11 cables and also unplugged the phone and im running nothing else electrical near by.
Not sure what to do and who to talk to .
You either have the right person that will go out of their way to help you or you just struggle.
I also run the Zertop test - 3 of them which all include 2x the tracert results:
Zertop Results:
Code:
TEST01
Tracert skipped (post too long)
International Speedtest
Downloaded 100.0 megabytes in 4:58 seconds. (343.37 KB/s)
Local Speedtest
Downloaded 8000.0 kilobytes in 14 seconds. (564.17 KB/s)
Test End Timestamp
Fri 09/23/2016 0:08:16.63
TEST02
Local Tracert
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms dsldevice.lan [192.168.10.1]
2 * * * Request timed out.
3 47 ms 231 ms 7 ms cdsl1-rba-vl2253-ipc.ip.isnet.net [196.38.73.182]
4 7 ms 7 ms 7 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
5 7 ms 7 ms 6 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 10 ms 8 ms 7 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 7 ms 17 ms 7 ms 168.209.1.170
8 7 ms 7 ms 7 ms mweb-1.jinx.net.za [196.223.14.25]
9 29 ms 29 ms 30 ms te0-0-0-3.vic-p-2.optinet.net [197.80.7.34]
10 28 ms 27 ms 27 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
11 25 ms 26 ms 25 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 27 ms 27 ms 26 ms 196.28.178.66
13 29 ms 27 ms 29 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 26 ms 26 ms 26 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 26 ms 27 ms 27 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 26 ms 26 ms 26 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms dsldevice.lan [192.168.10.1]
2 * * * Request timed out.
3 7 ms 8 ms 7 ms cdsl1-rba-vl2253-ipc.ip.isnet.net [196.38.73.182]
4 7 ms 7 ms 7 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
5 7 ms 7 ms 7 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 8 ms 7 ms 7 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 7 ms 7 ms 7 ms 168.209.1.170
8 7 ms 7 ms 7 ms mweb-1.jinx.net.za [196.223.14.25]
9 30 ms 28 ms 31 ms te0-0-0-3.vic-p-2.optinet.net [197.80.7.34]
10 30 ms 31 ms 31 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
11 26 ms 26 ms 26 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 28 ms 32 ms 26 ms 196.28.178.66
13 27 ms 27 ms 27 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 26 ms 27 ms 30 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 27 ms 26 ms 29 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 26 ms 26 ms 26 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
International Tracert
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms dsldevice.lan [192.168.10.1]
2 * * * Request timed out.
3 76 ms 104 ms 103 ms curp1-rba-gi1.isdsl.net [196.38.72.230]
4 7 ms 9 ms 7 ms 196.38.72.229
5 8 ms 7 ms 7 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 11 ms 7 ms 11 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 194 ms 194 ms 184 ms core2b-dock-ten-0-4-0-0sub8.ip.isnet.net [168.209.246.66]
8 184 ms 183 ms 184 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
9 180 ms 179 ms 179 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 183 ms 183 ms 184 ms [url]www.thinkbroadband.com[/url] [80.249.99.130]
Trace complete.
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms dsldevice.lan [192.168.10.1]
2 * * * Request timed out.
3 8 ms 7 ms 8 ms curp1-rba-gi1.isdsl.net [196.38.72.230]
4 7 ms 7 ms 7 ms 196.38.72.229
5 6 ms 7 ms 7 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 10 ms 7 ms 7 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 186 ms 188 ms 187 ms core2b-dock-ten-0-4-0-0sub8.ip.isnet.net [168.209.246.66]
8 183 ms 183 ms 183 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
9 181 ms 178 ms 193 ms po4-31.core-rs2.thdo.ncuk.net [80.249.97.85]
10 183 ms 183 ms 184 ms [url]www.thinkbroadband.com[/url] [80.249.99.130]
Trace complete.
International Speedtest
Downloaded 10.0 megabytes in 30 seconds. (331.28 KB/s)
Local Speedtest
Downloaded 4000.0 kilobytes in 5 seconds. (770.71 KB/s)
Test End Timestamp
Fri 09/23/2016 0:11:21.12
Last edited: