"Is it my Line" Report Tool

Cessationist · May 4, 2017

Hey guys!, I am running Afrihost's 4mbps uncapped business package, this is the results i'm getting:

Zertop's LineTool Results
Date/Time: Thu May 04 16:30:45 CAT 2017

Basic Report:

Your packet loss was 13%.
Your average ping was 370ms.
Your maximum ping was 1430ms.

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 169.0.27.1 with 32 bytes of data:
Reply from 169.0.27.1: bytes=32 time=174ms TTL=254
Reply from 169.0.27.1: bytes=32 time=303ms TTL=254
Reply from 169.0.27.1: bytes=32 time=379ms TTL=254
Reply from 169.0.27.1: bytes=32 time=266ms TTL=254
Reply from 169.0.27.1: bytes=32 time=242ms TTL=254
Reply from 169.0.27.1: bytes=32 time=87ms TTL=254
Reply from 169.0.27.1: bytes=32 time=312ms TTL=254
Request timed out.
Reply from 169.0.27.1: bytes=32 time=421ms TTL=254
Reply from 169.0.27.1: bytes=32 time=409ms TTL=254
Reply from 169.0.27.1: bytes=32 time=241ms TTL=254
Reply from 169.0.27.1: bytes=32 time=195ms TTL=254
Reply from 169.0.27.1: bytes=32 time=114ms TTL=254
Reply from 169.0.27.1: bytes=32 time=53ms TTL=254
Reply from 169.0.27.1: bytes=32 time=184ms TTL=254
Reply from 169.0.27.1: bytes=32 time=723ms TTL=254
Reply from 169.0.27.1: bytes=32 time=93ms TTL=254
Reply from 169.0.27.1: bytes=32 time=224ms TTL=254
Reply from 169.0.27.1: bytes=32 time=605ms TTL=254
Reply from 169.0.27.1: bytes=32 time=454ms TTL=254
Reply from 169.0.27.1: bytes=32 time=785ms TTL=254
Request timed out.
Reply from 169.0.27.1: bytes=32 time=1272ms TTL=254
Reply from 169.0.27.1: bytes=32 time=274ms TTL=254
Reply from 169.0.27.1: bytes=32 time=65ms TTL=254
Reply from 169.0.27.1: bytes=32 time=177ms TTL=254
Reply from 169.0.27.1: bytes=32 time=139ms TTL=254
Request timed out.
Request timed out.
Reply from 169.0.27.1: bytes=32 time=1430ms TTL=254

Ping statistics for 169.0.27.1:
    Packets: Sent = 30, Received = 26, Lost = 4 (13% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 1430ms, Average = 370ms

So i take it this means i should go after Telkom and not Afrihost?

Diesal · May 17, 2017

So guys what on earth causes this?

Zertop's LineTool Results
Date/Time: Wed May 17 23:28:35 CAT 2017

Basic Report:

Your packet loss was 46%.
Your average ping was 3297ms.
Your maximum ping was 3991ms.

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

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3991ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2933ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2831ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3766ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2928ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3213ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2921ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2684ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2913ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3735ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3664ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3776ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2938ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3688ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3427ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3353ms TTL=63
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 16, Lost = 14 (46% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2684ms, Maximum = 3991ms, Average = 3297ms

moedawood · May 21, 2017

Zertop's LineTool Results
Date/Time: Sun May 21 23:43:49 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 26ms.
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=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms 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=18ms 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 = 17ms, Maximum = 50ms, Average = 26ms

moedawood · May 21, 2017

When I test through my router which has the network tools feature so I'd assume results are better because it's a wired connection, I get this:

Code:

PING 155.239.255.250 (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=64 time=49.9 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=64 time=15.2 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=64 time=14.5 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=64 time=14.3 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=64 time=14.2 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=64 time=14.5 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=64 time=17.1 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=64 time=14.6 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=64 time=15.6 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=64 time=14.9 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=64 time=14.6 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=64 time=14.6 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=64 time=14.4 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=64 time=13.9 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=64 time=14.8 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=64 time=14.6 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=64 time=14.1 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=64 time=15.1 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=64 time=15.1 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=64 time=14.7 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=64 time=15.3 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=64 time=15.4 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=64 time=14.9 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=64 time=14.9 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=64 time=14.4 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=64 time=14.3 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=64 time=15.1 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=64 time=14.6 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=64 time=14.4 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=64 time=15.5 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max = 13.9/15.9/49.9 ms

getafix33 · May 23, 2017

How do you run this utility on windows 10??

moedawood · May 23, 2017

getafix33 said:
How do you run this utility on windows 10??

First page of the forum is the link to this utility. Download it and open it on your desktop. Then click start test

getafix33 · May 23, 2017

moedawood said:
First page of the forum is the link to this utility. Download it and open it on your desktop. Then click start test

Thanks. I have extracted it and see a few directories with .CLASS files.

Sorry, my bad. WINRAR is set to open .jar files

ronnie_94 · Jun 12, 2017

Do isp's accept these results? I had 200 ping and when running the tool it said no issues, if there is a problem it is probably your isp.

pittboell · Jun 27, 2017

My adsl line latency that runs fine the whole day, spikes every night a 11pm and continues until 7am the next morning (see test results below) to unusable levels.

Logging a fault does not help as the daytime test shows the line is fine. Any suggestions to get Telkom to attend to the fault?

Zertop's LineTool Results
Date/Time: Tue Jun 27 00:35:47 CAT 2017

Basic Report:

Your packet loss was 3%.
Your average ping was 305ms.
Your maximum ping was 570ms.

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=113ms TTL=64
Reply from 155.239.255.250: bytes=32 time=131ms TTL=64
Reply from 155.239.255.250: bytes=32 time=123ms TTL=64
Reply from 155.239.255.250: bytes=32 time=211ms TTL=64
Reply from 155.239.255.250: bytes=32 time=264ms TTL=64
Reply from 155.239.255.250: bytes=32 time=352ms TTL=64
Reply from 155.239.255.250: bytes=32 time=171ms TTL=64
Reply from 155.239.255.250: bytes=32 time=201ms TTL=64
Reply from 155.239.255.250: bytes=32 time=417ms TTL=64
Reply from 155.239.255.250: bytes=32 time=408ms TTL=64
Reply from 155.239.255.250: bytes=32 time=227ms TTL=64
Reply from 155.239.255.250: bytes=32 time=445ms TTL=64
Reply from 155.239.255.250: bytes=32 time=401ms TTL=64
Reply from 155.239.255.250: bytes=32 time=425ms TTL=64
Reply from 155.239.255.250: bytes=32 time=437ms TTL=64
Reply from 155.239.255.250: bytes=32 time=375ms TTL=64
Reply from 155.239.255.250: bytes=32 time=357ms TTL=64
Reply from 155.239.255.250: bytes=32 time=342ms TTL=64
Reply from 155.239.255.250: bytes=32 time=570ms TTL=64
Reply from 155.239.255.250: bytes=32 time=19ms TTL=64
Reply from 155.239.255.250: bytes=32 time=242ms TTL=64
Reply from 155.239.255.250: bytes=32 time=333ms TTL=64
Reply from 155.239.255.250: bytes=32 time=400ms TTL=64
Reply from 155.239.255.250: bytes=32 time=301ms TTL=64
Reply from 155.239.255.250: bytes=32 time=397ms TTL=64
Reply from 155.239.255.250: bytes=32 time=288ms TTL=64
Reply from 155.239.255.250: bytes=32 time=269ms TTL=64
Request timed out.
Reply from 155.239.255.250: bytes=32 time=333ms TTL=64
Reply from 155.239.255.250: bytes=32 time=301ms TTL=64

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

Geoff.D · Jun 27, 2017

pittboell said:

My adsl line latency that runs fine the whole day, spikes every night a 11pm and continues until 7am the next morning (see test results below) to unusable levels.

Logging a fault does not help as the daytime test shows the line is fine. Any suggestions to get Telkom to attend to the fault?

Zertop's LineTool Results
Date/Time: Tue Jun 27 00:35:47 CAT 2017

Basic Report:

Your packet loss was 3%.
Your average ping was 305ms.
Your maximum ping was 570ms.

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=113ms TTL=64
Reply from 155.239.255.250: bytes=32 time=131ms TTL=64
Reply from 155.239.255.250: bytes=32 time=123ms TTL=64
Reply from 155.239.255.250: bytes=32 time=211ms TTL=64
Reply from 155.239.255.250: bytes=32 time=264ms TTL=64
Reply from 155.239.255.250: bytes=32 time=352ms TTL=64
Reply from 155.239.255.250: bytes=32 time=171ms TTL=64
Reply from 155.239.255.250: bytes=32 time=201ms TTL=64
Reply from 155.239.255.250: bytes=32 time=417ms TTL=64
Reply from 155.239.255.250: bytes=32 time=408ms TTL=64
Reply from 155.239.255.250: bytes=32 time=227ms TTL=64
Reply from 155.239.255.250: bytes=32 time=445ms TTL=64
Reply from 155.239.255.250: bytes=32 time=401ms TTL=64
Reply from 155.239.255.250: bytes=32 time=425ms TTL=64
Reply from 155.239.255.250: bytes=32 time=437ms TTL=64
Reply from 155.239.255.250: bytes=32 time=375ms TTL=64
Reply from 155.239.255.250: bytes=32 time=357ms TTL=64
Reply from 155.239.255.250: bytes=32 time=342ms TTL=64
Reply from 155.239.255.250: bytes=32 time=570ms TTL=64
Reply from 155.239.255.250: bytes=32 time=19ms TTL=64
Reply from 155.239.255.250: bytes=32 time=242ms TTL=64
Reply from 155.239.255.250: bytes=32 time=333ms TTL=64
Reply from 155.239.255.250: bytes=32 time=400ms TTL=64
Reply from 155.239.255.250: bytes=32 time=301ms TTL=64
Reply from 155.239.255.250: bytes=32 time=397ms TTL=64
Reply from 155.239.255.250: bytes=32 time=288ms TTL=64
Reply from 155.239.255.250: bytes=32 time=269ms TTL=64
Request timed out.
Reply from 155.239.255.250: bytes=32 time=333ms TTL=64
Reply from 155.239.255.250: bytes=32 time=301ms TTL=64

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

Try and access the line stats ( SNR etc, at the same time this occurs form the diagnostic pages on the router direct. See iof you cab correlate the lines test results with anything reported by the router.

Next which exchange area are you in?
Have you tried to see if there are any reported maintenance issues for your exchange area or scheduled infrastructure work underway?

pittboell · Jul 4, 2017

Get the same results from the router.
No maintenance on the exchange.

Tonight the results are very strange. Can anyone make sense of this?

Zertop's LineTool Results
Date/Time: Tue Jul 04 02:20:34 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 551ms.
Your maximum ping was 957ms.

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=413ms TTL=63
Reply from 80.231.158.30: TTL expired in transit.
Reply from 155.239.255.250: bytes=32 time=213ms TTL=63
Reply from 4.53.121.70: TTL expired in transit.
Reply from 155.239.255.250: bytes=32 time=488ms TTL=63
Reply from 169.1.5.204: TTL expired in transit.
Reply from 169.1.5.204: TTL expired in transit.
Reply from 169.1.5.174: TTL expired in transit.
Reply from 172.18.1.162: TTL expired in transit.
Reply from 41.162.84.192: TTL expired in transit.
Reply from 155.239.255.250: bytes=32 time=551ms TTL=63
Reply from 4.53.121.70: TTL expired in transit.
Reply from 155.239.255.250: bytes=32 time=541ms TTL=63
Reply from 155.239.255.250: bytes=32 time=393ms TTL=63
Reply from 155.239.255.250: bytes=32 time=957ms TTL=63
Reply from 155.239.255.250: bytes=32 time=725ms TTL=63
Reply from 155.239.255.250: bytes=32 time=615ms TTL=63
Reply from 155.239.255.250: bytes=32 time=633ms TTL=63
Reply from 155.239.255.250: bytes=32 time=775ms TTL=63
Reply from 155.239.255.250: bytes=32 time=627ms TTL=63
Reply from 155.239.255.250: bytes=32 time=117ms TTL=63
Reply from 155.239.255.250: bytes=32 time=431ms TTL=63
Reply from 155.239.255.250: bytes=32 time=458ms TTL=63
Reply from 155.239.255.250: bytes=32 time=496ms TTL=63
Reply from 155.239.255.250: bytes=32 time=513ms TTL=63
Reply from 155.239.255.250: bytes=32 time=731ms TTL=63
Reply from 155.239.255.250: bytes=32 time=737ms TTL=63
Reply from 155.239.255.250: bytes=32 time=644ms TTL=63
Reply from 155.239.255.250: bytes=32 time=498ms TTL=63
Reply from 155.239.255.250: bytes=32 time=571ms 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 = 117ms, Maximum = 957ms, Average = 551ms

razzor13bt · Aug 22, 2017

i have a 4mb uncapped line with Crystalweb.
Zertop's LineTool Results
Date/Time: Tue Aug 22 19:07:52 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 86ms.
Your maximum ping was 284ms.

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=115ms TTL=62
Reply from 155.239.255.250: bytes=32 time=26ms TTL=62
Reply from 155.239.255.250: bytes=32 time=74ms TTL=62
Reply from 155.239.255.250: bytes=32 time=107ms TTL=62
Reply from 155.239.255.250: bytes=32 time=44ms TTL=62
Reply from 155.239.255.250: bytes=32 time=103ms TTL=62
Reply from 155.239.255.250: bytes=32 time=71ms TTL=62
Reply from 155.239.255.250: bytes=32 time=161ms TTL=62
Reply from 155.239.255.250: bytes=32 time=111ms TTL=62
Reply from 155.239.255.250: bytes=32 time=143ms TTL=62
Reply from 155.239.255.250: bytes=32 time=284ms TTL=62
Reply from 155.239.255.250: bytes=32 time=157ms TTL=62
Reply from 155.239.255.250: bytes=32 time=46ms TTL=62
Reply from 155.239.255.250: bytes=32 time=52ms TTL=62
Reply from 155.239.255.250: bytes=32 time=106ms TTL=62
Reply from 155.239.255.250: bytes=32 time=89ms TTL=62
Reply from 155.239.255.250: bytes=32 time=26ms TTL=62
Reply from 155.239.255.250: bytes=32 time=31ms TTL=62
Reply from 155.239.255.250: bytes=32 time=61ms TTL=62
Reply from 155.239.255.250: bytes=32 time=66ms TTL=62
Reply from 155.239.255.250: bytes=32 time=42ms TTL=62
Reply from 155.239.255.250: bytes=32 time=51ms TTL=62
Reply from 155.239.255.250: bytes=32 time=119ms TTL=62
Reply from 155.239.255.250: bytes=32 time=84ms TTL=62
Reply from 155.239.255.250: bytes=32 time=54ms TTL=62
Reply from 155.239.255.250: bytes=32 time=70ms TTL=62
Reply from 155.239.255.250: bytes=32 time=129ms TTL=62
Reply from 155.239.255.250: bytes=32 time=86ms TTL=62
Reply from 155.239.255.250: bytes=32 time=25ms TTL=62
Reply from 155.239.255.250: bytes=32 time=59ms TTL=62

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 284ms, Average = 86ms

razzor13bt · Aug 22, 2017

Dlink router statistics:

Mode: ADSL_2plus
Type: ATM
Status: Up

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (0.1dB): 246 260
Attenuation (0.1dB): 205 116
Output Power (0.1dBm): 198 126
Attainable Rate (Kbps): 22852 1111
Rate (Kbps): 4091 508
D (interleaver depth): 448 8
Delay (msec): 7.78 7.4

HEC Errors: 0 0
OCD Errors: 0 0
LCD Errors: 0 0

Total ES: 0 0

as the crow flies i am 1.6kms from the nearest exchange
2.4kms by road.

Bearded_O_G · Aug 26, 2017

Zertop's LineTool Results
Date/Time: Sat Aug 26 07:43:26 GMT+02:00 2017

Basic Report:

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

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=32.5 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=38.3 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=37.5 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=37.4 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=36.5 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=36.9 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=35.9 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=40.5 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=38.0 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=37.4 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=37.4 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=37.5 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=36.7 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=37.7 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=37.9 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=37.1 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=38.4 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=37.8 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=38.9 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=36.8 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=37.0 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=37.6 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=38.0 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=38.1 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=37.5 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=37.5 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=37.4 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=36.0 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=38.2 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=63 time=38.8 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29165ms
rtt min/avg/max/mdev = 32.568/37.496/40.576/1.285 ms

IndrenG · Oct 22, 2017

Zertop's LineTool Results
Date/Time: Sun Oct 22 10:40:56 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 936ms.
Your maximum ping was 1468ms.

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=707ms TTL=63
Reply from 155.239.255.250: bytes=32 time=733ms TTL=63
Reply from 155.239.255.250: bytes=32 time=742ms TTL=63
Reply from 155.239.255.250: bytes=32 time=745ms TTL=63
Reply from 155.239.255.250: bytes=32 time=788ms TTL=63
Reply from 155.239.255.250: bytes=32 time=795ms TTL=63
Reply from 155.239.255.250: bytes=32 time=780ms TTL=63
Reply from 155.239.255.250: bytes=32 time=815ms TTL=63
Reply from 155.239.255.250: bytes=32 time=815ms TTL=63
Reply from 155.239.255.250: bytes=32 time=866ms TTL=63
Reply from 155.239.255.250: bytes=32 time=867ms TTL=63
Reply from 155.239.255.250: bytes=32 time=875ms TTL=63
Reply from 155.239.255.250: bytes=32 time=893ms TTL=63
Reply from 155.239.255.250: bytes=32 time=904ms TTL=63
Reply from 155.239.255.250: bytes=32 time=920ms TTL=63
Reply from 155.239.255.250: bytes=32 time=927ms TTL=63
Reply from 155.239.255.250: bytes=32 time=938ms TTL=63
Reply from 155.239.255.250: bytes=32 time=934ms TTL=63
Reply from 155.239.255.250: bytes=32 time=967ms TTL=63
Reply from 155.239.255.250: bytes=32 time=980ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1004ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1022ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1029ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1058ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1099ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1075ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1468ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1085ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1109ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1141ms 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 = 707ms, Maximum = 1468ms, Average = 936ms

KOPITE · Apr 3, 2018

sorry gents, but when i open it via winzip i dont see a file to run it.

Am i missing something

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Cessationist

New Member

Diesal

Expert Member

moedawood

Senior Member

moedawood

Senior Member

getafix33

Expert Member

moedawood

Senior Member

getafix33

Expert Member

ronnie_94

Expert Member

pittboell

New Member

Geoff.D

Honorary Master

pittboell

New Member

razzor13bt

New Member

razzor13bt

New Member

Bearded_O_G

Senior Member

IndrenG

Active Member

KOPITE

Executive Member