"Is it my Line" Report Tool

BigBear · Mar 12, 2016

Zertop said:
Not great :/

Still as bad?

Z

Better now since TelkomZA Fixed something

11-03-2016
04:58 PM
Re: Telkom Line Fault report reference 585CTK150216
TelkomZA

Zertop's LineTool Results
Date/Time: Sat Mar 12 15:12:59 CAT 2016
Basic Report:

Your packet loss was 0%.
Your average ping was 61ms.
Your maximum ping was 595ms.

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=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=43ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms 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=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms 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=92ms 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=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=595ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms 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=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms 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 = 36ms, Maximum = 595ms, Average = 61ms

So far So Good been Stable on 10 mbps

Zertop · Mar 12, 2016

EchoZA said:
My current situation is a borked exchange... 3 weeks ago 10Mb line became 6Mb (max) with bad noise etc. Tech was here today and together we redid every joint going back to the exchange. Still the same, as a last resort connected direct at the cable coming out the DSLAM and the same results...

That's properly bleak :/

You sure it's not your router (I had a router show the same symptoms once-upon-a-time)

Z

Zertop · Mar 12, 2016

BigBear said:

Better now since TelkomZA Fixed something

Zertop's LineTool Results
Date/Time: Sat Mar 12 15:12:59 CAT 2016
Basic Report:

Your packet loss was 0%.
Your average ping was 61ms.
Your maximum ping was 595ms.

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=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=43ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms 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=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms 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=92ms 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=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=595ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms 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=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms 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 = 36ms, Maximum = 595ms, Average = 61ms

So far So Good been Stable on 10 mbps

Awesome! Ping is still a bit high, but I'm glad you're getting good speeds

Z

Geoff.D · Mar 12, 2016

Hi Zertop,

An excellent piece of work! Congratulations.

I see on average quite a variation on the results submitted by various persons.

Mine show an average ping time of 9 ms and a maximum of 10 ms.

I notice that the IPaddress reported has changed from a few weeks ago for me to 155.239.255.250 today. Seems Telkom is definitely up to something in my area.

If one does a tracert to any websites say google.co.za, the second and 3rd hops very often times out ( not always) Any reason why this happens? never had similar issues before the upgrade to WIN 10.

Best

Zertop · Mar 12, 2016

daniellgr said:
Hi Zertop,

An excellent piece of work! Congratulations.

I see on average quite a variation on the results submitted by various persons.

Mine show an average ping time of 9 ms and a maximum of 10 ms.

I notice that the IPaddress reported has changed from a few weeks ago for me to 155.239.255.250 today. Seems Telkom is definitely up to something in my area.

If one does a tracert to any websites say google.co.za, the second and 3rd hops very often times out ( not always) Any reason why this happens? never had similar issues before the upgrade to WIN 10.

Best

Hi There!

The different ping times are exactly what we are looking for

A ping over, say, 40ms indicates a problem somewhere. 10ms is an excellent result.

At some point last year Telkom released a new update for their DSLAM boxes/Exchanges which disabled the ability to ping them directly. This means that your second hop on your tracert, i.e. the exchange, would timeout - as Telkom blocks the ping request. To combat this, a user on the forum recommended that I change the tool to ping the BRAS network (155.239.255.250), which shows the same result. If you are only now seeing the tool pinging 155.239.255.250, it means your exchange was recently upgraded

Probably why you're seeing those good results

Z

Geoff.D · Mar 13, 2016

Zertop said:
Hi There!

The different ping times are exactly what we are looking for A ping over, say, 40ms indicates a problem somewhere. 10ms is an excellent result.

At some point last year Telkom released a new update for their DSLAM boxes/Exchanges which disabled the ability to ping them directly. This means that your second hop on your tracert, i.e. the exchange, would timeout - as Telkom blocks the ping request. To combat this, a user on the forum recommended that I change the tool to ping the BRAS network (155.239.255.250), which shows the same result. If you are only now seeing the tool pinging 155.239.255.250, it means your exchange was recently upgraded Probably why you're seeing those good results

Z

Thanks!

Turns out we have been swinging back and forth between some equipment in our local exchange, hence why a few weeks ago I got the DSLAM ping results and not the BRAS results.

Checked back though my logs and it would seem the main change occurred as long ago as Feb/March 2015.

Says something for my ADSL service ---- very stable in spite of the local line faults caused by cable damage. I sort of don't bother when I know there is a local cable fault.

BigBear · Mar 15, 2016

Before Router Reboot

Zertop's LineTool Results
Date/Time: Tue Mar 15 06:53:18 CAT 2016
Basic Report:

Your packet loss was 3%.
Your average ping was 199ms.
Your maximum ping was 405ms.

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=143ms TTL=63
Reply from 155.239.255.250: bytes=32 time=84ms TTL=63
Reply from 155.239.255.250: bytes=32 time=214ms TTL=63
Reply from 155.239.255.250: bytes=32 time=184ms TTL=63
Reply from 155.239.255.250: bytes=32 time=255ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=224ms TTL=63
Reply from 155.239.255.250: bytes=32 time=405ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=153ms TTL=63
Reply from 155.239.255.250: bytes=32 time=190ms TTL=63
Reply from 155.239.255.250: bytes=32 time=198ms TTL=63
Reply from 155.239.255.250: bytes=32 time=108ms TTL=63
Reply from 155.239.255.250: bytes=32 time=391ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=340ms TTL=63
Reply from 155.239.255.250: bytes=32 time=114ms TTL=63
Reply from 155.239.255.250: bytes=32 time=130ms TTL=63
Reply from 155.239.255.250: bytes=32 time=270ms TTL=63
Reply from 155.239.255.250: bytes=32 time=251ms TTL=63
Reply from 155.239.255.250: bytes=32 time=157ms TTL=63
Reply from 155.239.255.250: bytes=32 time=295ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=147ms TTL=63
Reply from 155.239.255.250: bytes=32 time=206ms TTL=63
Reply from 155.239.255.250: bytes=32 time=395ms TTL=63
Reply from 155.239.255.250: bytes=32 time=263ms TTL=63
Reply from 155.239.255.250: bytes=32 time=136ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 405ms, Average = 199ms

After Router Reboot

Zertop's LineTool Results
Date/Time: Tue Mar 15 07:03:01 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 40ms.
Your maximum ping was 49ms.

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=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms 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=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms 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=40ms 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=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms 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=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms 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 = 37ms, Maximum = 49ms, Average = 40ms

karnallie · Mar 16, 2016

Zertop said:
Try contacting your local Telkom shop. They usually have a way of assisting faster than the national hotline

A HelloPeter complaint seemed to have the desired effect... So my line is finally working great at 4mbps

Zertop · Mar 16, 2016

LuMiNOuS said:
A HelloPeter complaint seemed to have the desired effect... So my line is finally working great at 4mbps

Glad to hear it

Zertop · Mar 16, 2016

BigBear said:

Before Router Reboot

Zertop's LineTool Results
Date/Time: Tue Mar 15 06:53:18 CAT 2016
Basic Report:

Your packet loss was 3%.
Your average ping was 199ms.
Your maximum ping was 405ms.

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=143ms TTL=63
Reply from 155.239.255.250: bytes=32 time=84ms TTL=63
Reply from 155.239.255.250: bytes=32 time=214ms TTL=63
Reply from 155.239.255.250: bytes=32 time=184ms TTL=63
Reply from 155.239.255.250: bytes=32 time=255ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=224ms TTL=63
Reply from 155.239.255.250: bytes=32 time=405ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=153ms TTL=63
Reply from 155.239.255.250: bytes=32 time=190ms TTL=63
Reply from 155.239.255.250: bytes=32 time=198ms TTL=63
Reply from 155.239.255.250: bytes=32 time=108ms TTL=63
Reply from 155.239.255.250: bytes=32 time=391ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63
Reply from 155.239.255.250: bytes=32 time=340ms TTL=63
Reply from 155.239.255.250: bytes=32 time=114ms TTL=63
Reply from 155.239.255.250: bytes=32 time=130ms TTL=63
Reply from 155.239.255.250: bytes=32 time=270ms TTL=63
Reply from 155.239.255.250: bytes=32 time=251ms TTL=63
Reply from 155.239.255.250: bytes=32 time=157ms TTL=63
Reply from 155.239.255.250: bytes=32 time=295ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=147ms TTL=63
Reply from 155.239.255.250: bytes=32 time=206ms TTL=63
Reply from 155.239.255.250: bytes=32 time=395ms TTL=63
Reply from 155.239.255.250: bytes=32 time=263ms TTL=63
Reply from 155.239.255.250: bytes=32 time=136ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 40ms, Maximum = 405ms, Average = 199ms

After Router Reboot

Zertop's LineTool Results
Date/Time: Tue Mar 15 07:03:01 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 40ms.
Your maximum ping was 49ms.

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=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms 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=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms 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=40ms 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=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms 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=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms 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 = 37ms, Maximum = 49ms, Average = 40ms

Looking relatively OK, but not amazing. Are you receiving bad speeds?

Z

Zertop · Mar 16, 2016

daniellgr said:
Thanks!

Turns out we have been swinging back and forth between some equipment in our local exchange, hence why a few weeks ago I got the DSLAM ping results and not the BRAS results.

Checked back though my logs and it would seem the main change occurred as long ago as Feb/March 2015.

Says something for my ADSL service ---- very stable in spite of the local line faults caused by cable damage. I sort of don't bother when I know there is a local cable fault.

Aah okay,

But glad all is working well

Z

assagai · Mar 28, 2016

Thanks for the tool - here's my sad story.

Zertop's LineTool Results
Date/Time: Mon Mar 28 19:10:37 SAST 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 1116ms.
Your maximum ping was 1438ms.

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 data bytes
Request timeout for icmp_seq 0
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=1023.849 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=1131.217 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=1130.465 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=1178.764 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=1204.313 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=1203.538 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=1245.368 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=1270.308 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=1320.579 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=1376.729 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=1157.299 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=923.943 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=1049.701 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=1114.111 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=1093.683 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=990.301 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=1143.682 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=1242.325 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=1219.443 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=1276.141 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=1309.950 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=1333.568 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=1402.556 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=1438.902 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=1246.411 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=1074.305 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=711.045 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=624.692 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=444.062 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=622.187 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 444.062/1116.781/1438.902/236.774 ms

Zertop · Apr 1, 2016

Wow,

That is pretty hideous :/

Is it still that bad?

Z

assagai said:

Thanks for the tool - here's my sad story.

Zertop's LineTool Results
Date/Time: Mon Mar 28 19:10:37 SAST 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 1116ms.
Your maximum ping was 1438ms.

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 data bytes
Request timeout for icmp_seq 0
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=1023.849 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=1131.217 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=1130.465 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=1178.764 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=1204.313 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=1203.538 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=1245.368 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=1270.308 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=1320.579 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=1376.729 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=1157.299 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=923.943 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=1049.701 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=1114.111 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=1093.683 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=990.301 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=1143.682 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=1242.325 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=1219.443 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=1276.141 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=1309.950 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=1333.568 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=1402.556 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=1438.902 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=1246.411 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=1074.305 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=711.045 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=624.692 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=444.062 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=622.187 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 444.062/1116.781/1438.902/236.774 ms

jarad12 · Apr 12, 2016

Guys please assist with this. The line gets extremely slow an starts dropping in the evenings. Telkom claims its not them and I have tested afrihost and webafrica and it makes no difference. The fact that its seems only to occur in the evenings indicates some kind of local congestion issue. This only started within the past 3 weeks, with zero issues for years previously. In Centurion.

Zertop's LineTool Results
Date/Time: Tue Apr 12 16:30:19 CAT 2016

Basic Report:

Your packet loss was 50%.
Your average ping was 3256ms.
Your maximum ping was 3919ms.

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

Detailed Report:

Pinging 196.210.146.1 with 32 bytes of data:
Reply from 196.210.146.1: bytes=32 time=2832ms TTL=254
Reply from 196.210.146.1: bytes=32 time=2798ms TTL=254
Reply from 196.210.146.1: bytes=32 time=2928ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3003ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3093ms TTL=254
Reply from 196.210.146.1: bytes=32 time=2943ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3350ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3340ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3308ms TTL=254
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3661ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3297ms TTL=254
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3854ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3919ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3878ms TTL=254
Request timed out.
Reply from 196.210.146.1: bytes=32 time=2639ms TTL=254
Request timed out.
Request timed out.

Ping statistics for 196.210.146.1:
Packets: Sent = 30, Received = 15, Lost = 15 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 2639ms, Maximum = 3919ms, Average = 3256ms

Tested this previously this afternoon and the results are absolutely perfect during the day every day.

wingnut771 · Apr 12, 2016

jarad12 said:
Guys please assist with this. The line gets extremely slow an starts dropping in the evenings. Telkom claims its not them and I have tested afrihost and webafrica and it makes no difference. The fact that its seems only to occur in the evenings indicates some kind of local congestion issue. This only started within the past 3 weeks, with zero issues for years previously. In Centurion.

Zertop's LineTool Results
Date/Time: Tue Apr 12 16:30:19 CAT 2016

Basic Report:

Your packet loss was 50%.
Your average ping was 3256ms.
Your maximum ping was 3919ms.

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

Detailed Report:

Pinging 196.210.146.1 with 32 bytes of data:
Reply from 196.210.146.1: bytes=32 time=2832ms TTL=254
Reply from 196.210.146.1: bytes=32 time=2798ms TTL=254
Reply from 196.210.146.1: bytes=32 time=2928ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3003ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3093ms TTL=254
Reply from 196.210.146.1: bytes=32 time=2943ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3350ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3340ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3308ms TTL=254
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3661ms TTL=254
Reply from 196.210.146.1: bytes=32 time=3297ms TTL=254
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3854ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3919ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.210.146.1: bytes=32 time=3878ms TTL=254
Request timed out.
Reply from 196.210.146.1: bytes=32 time=2639ms TTL=254
Request timed out.
Request timed out.

Ping statistics for 196.210.146.1:
Packets: Sent = 30, Received = 15, Lost = 15 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 2639ms, Maximum = 3919ms, Average = 3256ms

Tested this previously this afternoon and the results are absolutely perfect during the day every day.

Check nothing is uploading during that time like icloud - maybe disable wifi

assagai · Apr 14, 2016

Zertop said:
Wow,

That is pretty hideous :/

Is it still that bad?

Z

It's intermittent. I report it to telkom, it works again for a couple days, and then gradually slides back to this.

Zertop · Apr 14, 2016

assagai said:
It's intermittent. I report it to telkom, it works again for a couple days, and then gradually slides back to this.

Sounds like a bit of an exchange issue. If possible, check if any of your neighbours are having similar issues

tortured · Apr 17, 2016

So this has been happening the past week or so. Returns to normal late at night.

This is a capped account. Any ideas?

Zertop's LineTool Results
Date/Time: Sun Apr 17 21:59:42 CAT 2016

Basic Report:

Your packet loss was 26%.
Your average ping was 1128ms.
Your maximum ping was 3926ms.

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

Detailed Report:

Code:

Pinging 169.0.44.1 with 32 bytes of data:
Reply from 169.0.44.1: bytes=32 time=1128ms TTL=254
Reply from 169.0.44.1: bytes=32 time=207ms TTL=254
Reply from 169.0.44.1: bytes=32 time=84ms TTL=254
Reply from 169.0.44.1: bytes=32 time=59ms TTL=254
Reply from 169.0.44.1: bytes=32 time=81ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1213ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1260ms TTL=254
Reply from 169.0.44.1: bytes=32 time=506ms TTL=254
Reply from 169.0.44.1: bytes=32 time=2397ms TTL=254
Reply from 169.0.44.1: bytes=32 time=381ms TTL=254
Reply from 169.0.44.1: bytes=32 time=91ms TTL=254
Reply from 169.0.44.1: bytes=32 time=3488ms TTL=254
Reply from 169.0.44.1: bytes=32 time=467ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.44.1: bytes=32 time=249ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1790ms TTL=254
Reply from 169.0.44.1: bytes=32 time=201ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1293ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1338ms TTL=254
Reply from 169.0.44.1: bytes=32 time=2887ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 169.0.44.1: bytes=32 time=1473ms TTL=254
Reply from 169.0.44.1: bytes=32 time=307ms TTL=254
Reply from 169.0.44.1: bytes=32 time=3926ms TTL=254

Ping statistics for 169.0.44.1:
    Packets: Sent = 30, Received = 22, Lost = 8 (26% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 3926ms, Average = 1128ms

Zertop · Apr 18, 2016

tortured said:

So this has been happening the past week or so. Returns to normal late at night.

This is a capped account. Any ideas?

Zertop's LineTool Results
Date/Time: Sun Apr 17 21:59:42 CAT 2016

Basic Report:

Your packet loss was 26%.
Your average ping was 1128ms.
Your maximum ping was 3926ms.

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

Detailed Report:

Code:

Pinging 169.0.44.1 with 32 bytes of data:
Reply from 169.0.44.1: bytes=32 time=1128ms TTL=254
Reply from 169.0.44.1: bytes=32 time=207ms TTL=254
Reply from 169.0.44.1: bytes=32 time=84ms TTL=254
Reply from 169.0.44.1: bytes=32 time=59ms TTL=254
Reply from 169.0.44.1: bytes=32 time=81ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1213ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1260ms TTL=254
Reply from 169.0.44.1: bytes=32 time=506ms TTL=254
Reply from 169.0.44.1: bytes=32 time=2397ms TTL=254
Reply from 169.0.44.1: bytes=32 time=381ms TTL=254
Reply from 169.0.44.1: bytes=32 time=91ms TTL=254
Reply from 169.0.44.1: bytes=32 time=3488ms TTL=254
Reply from 169.0.44.1: bytes=32 time=467ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.44.1: bytes=32 time=249ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1790ms TTL=254
Reply from 169.0.44.1: bytes=32 time=201ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1293ms TTL=254
Reply from 169.0.44.1: bytes=32 time=1338ms TTL=254
Reply from 169.0.44.1: bytes=32 time=2887ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 169.0.44.1: bytes=32 time=1473ms TTL=254
Reply from 169.0.44.1: bytes=32 time=307ms TTL=254
Reply from 169.0.44.1: bytes=32 time=3926ms TTL=254

Ping statistics for 169.0.44.1:
    Packets: Sent = 30, Received = 22, Lost = 8 (26% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 3926ms, Average = 1128ms

Looks to be line issue...

Have you tested with other ISP accounts?

EchoZA · Apr 18, 2016

Zertop's LineTool Results
Date/Time: Mon Apr 18 17:46:58 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 32ms.
Your maximum ping was 34ms.

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=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=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms 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=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms 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=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=32ms 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=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms 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=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=32ms 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

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 = 34ms, Average = 32ms

Any comments?

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Expert Member

Expert Member

Expert Member

Honorary Master

Expert Member

Honorary Master

Expert Member

Well-Known Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

New Member

Honorary Master

Expert Member

Expert Member

Senior Member

Expert Member

Expert Member