"Is it my Line" Report Tool

V

ViciousClone

Expert Member
Joined
Apr 26, 2012
Messages
4,203
Hows the stats looking?
got a new modem and new filter but seems the telephone still has a crackling noise??

Zertop's LineTool Results
Date/Time: Thu Oct 29 22:52:43 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 16ms.
Your maximum ping was 21ms.

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=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63

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

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
djbrendan said:
Hows the stats looking?
got a new modem and new filter but seems the telephone still has a crackling noise??

Zertop's LineTool Results
Date/Time: Thu Oct 29 22:52:43 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 16ms.
Your maximum ping was 21ms.

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=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 21ms, Average = 16ms[/QUOTE]

Looking good!

Z
Click to expand...
 
A

AntiGanda

Banned
Joined
Aug 17, 2014
Messages
4,515
I get this error on Vox today. They refuse to acknowledge any problems btw.
What could cause this error?

I used the .jar and it just stopped at the first test.

zertop_error.jpg
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
AntiGanda said:
I get this error on Vox today. They refuse to acknowledge any problems btw.
What could cause this error?

I used the .jar and it just stopped at the first test.

View attachment 311445
Click to expand...

Heyo!

It's not typically seen that the second hop has anything to do with the ISP, however your results show it as belonging to vox o_O

Very strange!

Let me take a look :)

Z
 
V

ViciousClone

Expert Member
Joined
Apr 26, 2012
Messages
4,203
Zertop said:
Heyo!

It's not typically seen that the second hop has anything to do with the ISP, however your results show it as belonging to vox o_O

Very strange!

Let me take a look :)

Z
Click to expand...
How is it showing Vox on the 2nd hop amd not telkom ??! Haha this is new
 
Luke7777

Luke7777

Executive Member
Joined
Apr 22, 2004
Messages
8,730
Also get this on 221 and 220. Works on 219


Tracing route to zertop.com [154.127.61.124]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 8 ms 8 ms 8 ms 169-0-53-1.ip.afrihost.co.za [169.0.53.1]
3 11 ms 11 ms 10 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
4 11 ms 11 ms 11 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
5 11 ms 11 ms 11 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
6 11 ms 11 ms 11 ms 41.169.57.218
7 74 ms 11 ms 11 ms is.jinx.net.za [196.223.14.10]
8 11 ms 11 ms 12 ms csw5-pkl-te1-7.ip.isnet.net [196.26.0.188]
9 12 ms 11 ms 11 ms 197.96.204.52
10 23 ms 23 ms 25 ms za-node1.host1plus.com [154.70.152.50]
11 12 ms 11 ms 11 ms zertop.com [154.127.61.124]

Trace complete.
 

Attachments

  • zer01.jpg
    zer01.jpg
    20.8 KB · Views: 384
P

petrus344

Member
Joined
Mar 1, 2013
Messages
23
Zertop's LineTool Results
Date/Time: Sun Nov 15 21:47:43 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 7ms.
Your maximum ping was 8ms.

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:

Pinging 155.239.255.250 with 32 bytes of data:
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=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=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=8ms 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=8ms 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=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

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 = 8ms, Average = 7ms
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
petrus344 said:
Zertop's LineTool Results
Date/Time: Sun Nov 15 21:47:43 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 7ms.
Your maximum ping was 8ms.

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:

Pinging 155.239.255.250 with 32 bytes of data:
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=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=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=8ms 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=8ms 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=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

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 = 8ms, Average = 7ms
Click to expand...

Looking good to me :)

Z
 
A

atomcrusher

Expert Member
Joined
Jun 27, 2006
Messages
4,208
Using Zertop's tool
_________________
Zertop's LineTool Results
Date/Time: Wed Nov 25 08:21:30 CAT 2015

Basic Report:

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

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=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=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63

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 = 23ms, Average = 13ms

I don't really understand the above :eek: but I guess it's not bad for my 4Mbps Telkom ISP line?
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
atomcrusher said:
Using Zertop's tool
_________________
Zertop's LineTool Results
Date/Time: Wed Nov 25 08:21:30 CAT 2015

Basic Report:

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

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:
Code: 
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=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=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63

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 = 23ms, Average = 13ms

I don't really understand the above :eek: but I guess it's not bad for my 4Mbps Telkom ISP line?
Click to expand...

Looks good to me!

Z
 
M

Mental-Tree

Senior Member
Joined
Jun 30, 2009
Messages
777
AntiGanda said:
I get this error on Vox today. They refuse to acknowledge any problems btw.
What could cause this error?

I used the .jar and it just stopped at the first test.

View attachment 311445
Click to expand...

I either get above myself OR i get bellow results

Zertop's LineTool Results
Date/Time: Sat Nov 28 10:03:59 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 4ms.
Your maximum ping was 90ms.

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:

Pinging 10.0.0.2 with 32 bytes of data:
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=3ms TTL=64
Reply from 10.0.0.2: bytes=32 time=3ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=90ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64

Ping statistics for 10.0.0.2:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 90ms, Average = 4ms
Click to expand...

It's just pinging my router :wtf:
 
B

BigBear

Expert Member
Joined
Apr 24, 2008
Messages
2,197
Telkom 10 Mbps ADSL Line

Code: 
Adsl Line Status	SHOWTIME.L0
Adsl Mode	G992.5
Up Stream	639 kbps
Down Stream	8190 kbps
Attenuation Down Stream	25
Attenuation Up Stream	13
SNR Margin Down Stream	10.0
SNR Margin Up Stream	10.2

VOX Fatpipe

JHB

YOUR LATEST RESULTS
332539508.png
Code: 
Last Result:
Download Speed: 5950 kbps (743.8 KB/sec transfer rate)
Upload Speed: 434 kbps (54.3 KB/sec transfer rate)
Latency: 11 ms
Jitter: 6 ms
11/28/2015, 10:17:13 AM

CPT

YOUR LATEST RESULTS
332539944.png
Code: 
Last Result:
Download Speed: 4638 kbps (579.8 KB/sec transfer rate)
Upload Speed: 434 kbps (54.3 KB/sec transfer rate)
Latency: 27 ms
Jitter: 10 ms
11/28/2015, 10:18:27 AM

zertop Line Tool Version 222

Zertop's LineTool Results
Date/Time: Sat Nov 28 10:20:56 CAT 2015

Basic Report:

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

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=10ms TTL=62
Reply from 155.239.255.250: bytes=32 time=14ms TTL=62
Reply from 155.239.255.250: bytes=32 time=10ms TTL=62
Reply from 155.239.255.250: bytes=32 time=38ms TTL=62
Reply from 155.239.255.250: bytes=32 time=12ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=11ms TTL=62
Reply from 155.239.255.250: bytes=32 time=27ms TTL=62
Reply from 155.239.255.250: bytes=32 time=10ms TTL=62
Reply from 155.239.255.250: bytes=32 time=10ms TTL=62
Reply from 155.239.255.250: bytes=32 time=10ms TTL=62
Reply from 155.239.255.250: bytes=32 time=28ms TTL=62
Reply from 155.239.255.250: bytes=32 time=33ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=25ms TTL=62
Reply from 155.239.255.250: bytes=32 time=10ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=9ms TTL=62
Reply from 155.239.255.250: bytes=32 time=11ms TTL=62
Reply from 155.239.255.250: bytes=32 time=35ms TTL=62
Reply from 155.239.255.250: bytes=32 time=27ms TTL=62
Reply from 155.239.255.250: bytes=32 time=31ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=34ms TTL=62
Reply from 155.239.255.250: bytes=32 time=36ms TTL=62
Reply from 155.239.255.250: bytes=32 time=10ms 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 = 9ms, Maximum = 38ms, Average = 18ms
 
You must log in or register to reply here.
Top