"Is it my Line" Report Tool

Geoff.D · Mar 28, 2017

Zertop said:
Did you manage to sort it by updating java?

No. I left the issue with the company involved. They had to decide about updating the sw that uses an old version of JAVA. I showed them however, that the PC would work fine with the latest version of Java on it but it still required their IT guys to allow the update.

"You can take a Horse to water an all that ...."

Zertop · Mar 28, 2017

Geoff.D said:
No. I left the issue with the company involved. They had to decide about updating the sw that uses an old version of JAVA. I showed them however, that the PC would work fine with the latest version of Java on it but it still required their IT guys to allow the update.

"You can take a Horse to water an all that ...."

Ahaaa,

Sounds like one of those typical situations where explaining seems fruitless. I definitely think this is just a version error though

happynoodleboy · Mar 28, 2017

Zertop said:
Let me know how that goes! I've compiled using JDK7, so anything > Java 7 should work fine

Will let you know later when I am home.

Thanks a million!

happynoodleboy · Mar 28, 2017

Hi Zertop.

Was definitely my Java on work PC.
Works perfect at home:

Zertop's LineTool Results
Date/Time: Tue Mar 28 16:55:09 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 60ms.
Your maximum ping was 223ms.

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=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=158ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms 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=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=223ms TTL=63
Reply from 155.239.255.250: bytes=32 time=114ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms 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=111ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=189ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=80ms TTL=63
Reply from 155.239.255.250: bytes=32 time=65ms TTL=63
Reply from 155.239.255.250: bytes=32 time=144ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=56ms 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 = 223ms, Average = 60ms

Ramantoo · Apr 5, 2017

App works correctly - my line not so much

Zertop's LineTool Results
Date/Time: Wed Apr 05 23:05:58 CAT 2017

Basic Report:

Your packet loss was 6%.
Your average ping was 10ms.
Your maximum ping was 34ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

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
Request timed out.
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=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=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 34ms, Average = 10ms

SYNERGY · Apr 7, 2017

I get pings of 3 seconds with Web Africa. Telkom still insists that my line is fine

Zertop's LineTool Results
Date/Time: Fri Apr 07 11:25:10 GMT+02:00 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 145ms.
Your maximum ping was 763ms.

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=62 time=56.4 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=62 time=763 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=62 time=51.4 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=62 time=71.5 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=62 time=89.0 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=62 time=68.3 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=62 time=48.7 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=62 time=111 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=62 time=44.4 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=62 time=270 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=62 time=220 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=62 time=47.0 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=62 time=48.5 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=62 time=49.5 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=62 time=88.9 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=62 time=184 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=62 time=145 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=62 time=43.2 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=62 time=48.1 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=62 time=70.6 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=62 time=47.0 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=62 time=49.1 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=62 time=45.6 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=62 time=680 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=62 time=59.9 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=62 time=54.2 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=62 time=99.1 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=62 time=49.3 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=62 time=47.4 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=62 time=697 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29127ms
rtt min/avg/max/mdev = 43.273/145.064/763.687/197.551 ms

electrofreeze · Apr 7, 2017

is there a problem with your tool on linux with openjdk8 as it does not seam to work properly on debian

Zertop · Apr 7, 2017

electrofreeze said:
is there a problem with your tool on linux with openjdk8 as it does not seam to work properly on debian

Not that I'm aware of, will test!

Edit: Is this command line or desktop?

Zertop · Apr 7, 2017

SYNERGY said:

I get pings of 3 seconds with Web Africa. Telkom still insists that my line is fine

Zertop's LineTool Results
Date/Time: Fri Apr 07 11:25:10 GMT+02:00 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 145ms.
Your maximum ping was 763ms.

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=62 time=56.4 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=62 time=763 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=62 time=51.4 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=62 time=71.5 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=62 time=89.0 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=62 time=68.3 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=62 time=48.7 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=62 time=111 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=62 time=44.4 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=62 time=270 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=62 time=220 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=62 time=47.0 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=62 time=48.5 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=62 time=49.5 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=62 time=88.9 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=62 time=184 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=62 time=145 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=62 time=43.2 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=62 time=48.1 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=62 time=70.6 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=62 time=47.0 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=62 time=49.1 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=62 time=45.6 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=62 time=680 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=62 time=59.9 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=62 time=54.2 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=62 time=99.1 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=62 time=49.3 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=62 time=47.4 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=62 time=697 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29127ms
rtt min/avg/max/mdev = 43.273/145.064/763.687/197.551 ms

Undoubtedly line issues...

SYNERGY · Apr 7, 2017

Zertop said:
Undoubtedly line issues...

Thanks. Tested with 3 isp's.

electrofreeze · Apr 7, 2017

Zertop said:
Not that I'm aware of, will test!

Edit: Is this command line or desktop?

desktop

Zertop · Apr 10, 2017

electrofreeze said:
desktop

Seems to work my side? I'll reconfirm a bit later

Edit: Yeah, just checked - working perfectly. Does the app open to the splash screen?

electrofreeze · Apr 14, 2017

yes it opens but the test is very quick and the output is all 0

Zertop · Apr 16, 2017

electrofreeze said:
yes it opens but the test is very quick and the output is all 0

Are you running on ADSL or Fibre?

Idiosyncratic · Apr 16, 2017

Zertop's LineTool Results
Date/Time: Sun Apr 16 20:20:02 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 24ms.
Your maximum ping was 50ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=24ms 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=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms 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=23ms 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=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms 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=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms 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=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

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 = 50ms, Average = 24ms

Speeds haven't been great lately vs what they used to be with Vox (+ Telkom DSL) - could it be the line?

Zertop · Apr 17, 2017

Idiosyncratic said:

Zertop's LineTool Results
Date/Time: Sun Apr 16 20:20:02 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 24ms.
Your maximum ping was 50ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=24ms 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=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms 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=23ms 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=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms 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=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms 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=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

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 = 50ms, Average = 24ms

Speeds haven't been great lately vs what they used to be with Vox (+ Telkom DSL) - could it be the line?

To be honest, line looks alright to me :/

Is there a specific time when speeds are dropping?

Idiosyncratic · Apr 17, 2017

Zertop said:
To be honest, line looks alright to me :/

Is there a specific time when speeds are dropping?

Nope, just used to be ~9.5 Mbps (on a 10 Mbps line), but now it usually tests ~5 Mbps.

craigcul · Apr 20, 2017

AH uncapped 2 meg line wireless to modem internet is ok at the moment great program.

Zertop's LineTool Results
Date/Time: Thu Apr 20 19:05:53 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 18ms.
Your maximum ping was 24ms.

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=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms 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 = 16ms, Maximum = 24ms, Average = 18ms

wingnut771 · Apr 21, 2017

With a YT vid playing same time:

Zertop's LineTool Results
Date/Time: Fri Apr 21 22:13:33 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 13ms.
Your maximum ping was 20ms.

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=15ms 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=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=20ms 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=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms 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=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms 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=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=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 = 20ms, Average = 13ms

MoonOwl · Apr 24, 2017

On Afrihost's 10 Mbps Premium Uncapped bundle.

Zertop's LineTool Results
Date/Time: Mon Apr 24 23:48:50 SAST 2017

Basic Report:

Your packet loss was 3%.
Your average ping was 17ms.
Your maximum ping was 163ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.

Detailed Report:

Code:

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=64 time=14.7 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=64 time=12.7 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=64 time=11.4 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=64 time=9.87 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=64 time=12.1 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=64 time=9.81 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=64 time=9.62 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=64 time=10.9 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=64 time=37.7 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=64 time=9.74 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=64 time=10.2 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=64 time=9.84 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=64 time=9.90 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=64 time=10.6 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=64 time=9.61 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=64 time=163 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=64 time=9.57 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=64 time=9.37 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=64 time=9.39 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=64 time=11.0 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=64 time=36.5 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=64 time=9.53 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=64 time=11.7 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=64 time=9.67 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=64 time=9.72 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=64 time=10.0 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=64 time=10.1 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=64 time=10.1 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=64 time=9.62 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 29 received, 3% packet loss, time 29050ms
rtt min/avg/max/mdev = 9.378/17.556/163.519/28.424 ms

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Honorary Master

Expert Member

Expert Member

Expert Member

Member

Executive Member

Expert Member

Expert Member

Expert Member

Executive Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Well-Known Member

Honorary Master

Active Member