"Is it my Line" Report Tool

B

Bufamotis

Senior Member
Joined
May 8, 2011
Messages
505
Here you go good sir..

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 15ms
Your maximum ping was 39ms

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 intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 196.210.142.129 with 32 bytes of data:
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=11ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=38ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=39ms TTL=254
Reply from 196.210.142.129: bytes=32 time=27ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=35ms TTL=254

Ping statistics for 196.210.142.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 39ms, Average = 15ms
 
2014-09-27 18:39:15,88
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Bufamotis said:
Here you go good sir..

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 15ms
Your maximum ping was 39ms

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 intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 196.210.142.129 with 32 bytes of data:
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=11ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=38ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=39ms TTL=254
Reply from 196.210.142.129: bytes=32 time=27ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=13ms TTL=254
Reply from 196.210.142.129: bytes=32 time=12ms TTL=254
Reply from 196.210.142.129: bytes=32 time=35ms TTL=254

Ping statistics for 196.210.142.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 39ms, Average = 15ms
 
2014-09-27 18:39:15,88
Click to expand...

That seems fine now!? Could have been a port reset that fixed it?

Did you notice a performance boost? It seems like you should have :)

Z
 
B

Bufamotis

Senior Member
Joined
May 8, 2011
Messages
505
Yip, on Web Africa it seems everything ran quite smooth. YouTube defaulted to 480p as opposed to usual 240
 
G

GreenArrow

Active Member
Joined
Apr 17, 2012
Messages
72
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 105.236.13.65 with 32 bytes of data:
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Request timed out.
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=15ms TTL=254
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=16ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254

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

Sun 28/09/2014 18:34:35.66


Your average ping was 13ms
Your maximum ping was 16ms

Looking at your average ping, your line seems to be running perfectly :)

Maybe add a thing that says packet loss is a bad sign?
 
J

Jimmy

Well-Known Member
Joined
Apr 12, 2011
Messages
472
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 32ms
Your maximum ping was 113ms

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 (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 105.233.9.1 with 32 bytes of data:
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=106ms TTL=254
Reply from 105.233.9.1: bytes=32 time=47ms TTL=254
Reply from 105.233.9.1: bytes=32 time=103ms TTL=254
Reply from 105.233.9.1: bytes=32 time=113ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=30ms TTL=254
Reply from 105.233.9.1: bytes=32 time=18ms TTL=254
Reply from 105.233.9.1: bytes=32 time=63ms TTL=254
Reply from 105.233.9.1: bytes=32 time=64ms TTL=254
Reply from 105.233.9.1: bytes=32 time=29ms TTL=254
Reply from 105.233.9.1: bytes=32 time=34ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=36ms TTL=254
Reply from 105.233.9.1: bytes=32 time=23ms TTL=254
Reply from 105.233.9.1: bytes=32 time=50ms TTL=254
Reply from 105.233.9.1: bytes=32 time=13ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=14ms TTL=254
Reply from 105.233.9.1: bytes=32 time=16ms TTL=254
Reply from 105.233.9.1: bytes=32 time=88ms TTL=254
Reply from 105.233.9.1: bytes=32 time=13ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254

Ping statistics for 105.233.9.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 113ms, Average = 32ms

2014/09/28 19:12:41.94
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
GreenArrow said:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 105.236.13.65 with 32 bytes of data:
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Request timed out.
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=15ms TTL=254
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=14ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=16ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=13ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254
Reply from 105.236.13.65: bytes=32 time=12ms TTL=254

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

Sun 28/09/2014 18:34:35.66


Your average ping was 13ms
Your maximum ping was 16ms

Looking at your average ping, your line seems to be running perfectly :)

Maybe add a thing that says packet loss is a bad sign?
Click to expand...

Will do! Thanks :)

Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
50-saint said:
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 32ms
Your maximum ping was 113ms

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 (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 105.233.9.1 with 32 bytes of data:
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=106ms TTL=254
Reply from 105.233.9.1: bytes=32 time=47ms TTL=254
Reply from 105.233.9.1: bytes=32 time=103ms TTL=254
Reply from 105.233.9.1: bytes=32 time=113ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=30ms TTL=254
Reply from 105.233.9.1: bytes=32 time=18ms TTL=254
Reply from 105.233.9.1: bytes=32 time=63ms TTL=254
Reply from 105.233.9.1: bytes=32 time=64ms TTL=254
Reply from 105.233.9.1: bytes=32 time=29ms TTL=254
Reply from 105.233.9.1: bytes=32 time=34ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=36ms TTL=254
Reply from 105.233.9.1: bytes=32 time=23ms TTL=254
Reply from 105.233.9.1: bytes=32 time=50ms TTL=254
Reply from 105.233.9.1: bytes=32 time=13ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=11ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=14ms TTL=254
Reply from 105.233.9.1: bytes=32 time=16ms TTL=254
Reply from 105.233.9.1: bytes=32 time=88ms TTL=254
Reply from 105.233.9.1: bytes=32 time=13ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254
Reply from 105.233.9.1: bytes=32 time=10ms TTL=254

Ping statistics for 105.233.9.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 113ms, Average = 32ms

2014/09/28 19:12:41.94
Click to expand...

Eeh a bit jumpy... what type of issues are you experiencing?

Z
 
R

r035198x

New Member
Joined
Mar 30, 2010
Messages
5
Well, my internet is non existent today


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 730ms
Your maximum ping was 1111ms

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 results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.224.40.1 with 32 bytes of data:
Reply from 105.224.40.1: bytes=32 time=654ms TTL=254
Reply from 105.224.40.1: bytes=32 time=563ms TTL=254
Reply from 105.224.40.1: bytes=32 time=543ms TTL=254
Reply from 105.224.40.1: bytes=32 time=531ms TTL=254
Reply from 105.224.40.1: bytes=32 time=543ms TTL=254
Reply from 105.224.40.1: bytes=32 time=594ms TTL=254
Reply from 105.224.40.1: bytes=32 time=624ms TTL=254
Reply from 105.224.40.1: bytes=32 time=658ms TTL=254
Reply from 105.224.40.1: bytes=32 time=680ms TTL=254
Reply from 105.224.40.1: bytes=32 time=701ms TTL=254
Reply from 105.224.40.1: bytes=32 time=723ms TTL=254
Reply from 105.224.40.1: bytes=32 time=562ms TTL=254
Reply from 105.224.40.1: bytes=32 time=558ms TTL=254
Reply from 105.224.40.1: bytes=32 time=686ms TTL=254
Reply from 105.224.40.1: bytes=32 time=708ms TTL=254
Reply from 105.224.40.1: bytes=32 time=730ms TTL=254
Reply from 105.224.40.1: bytes=32 time=752ms TTL=254
Reply from 105.224.40.1: bytes=32 time=774ms TTL=254
Reply from 105.224.40.1: bytes=32 time=694ms TTL=254
Reply from 105.224.40.1: bytes=32 time=716ms TTL=254
Reply from 105.224.40.1: bytes=32 time=738ms TTL=254
Reply from 105.224.40.1: bytes=32 time=760ms TTL=254
Reply from 105.224.40.1: bytes=32 time=782ms TTL=254
Reply from 105.224.40.1: bytes=32 time=1111ms TTL=254
Reply from 105.224.40.1: bytes=32 time=1022ms TTL=254
Reply from 105.224.40.1: bytes=32 time=818ms TTL=254
Reply from 105.224.40.1: bytes=32 time=942ms TTL=254
Reply from 105.224.40.1: bytes=32 time=964ms TTL=254
Reply from 105.224.40.1: bytes=32 time=884ms TTL=254
Reply from 105.224.40.1: bytes=32 time=906ms TTL=254

Ping statistics for 105.224.40.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 531ms, Maximum = 1111ms, Average = 730ms
 
Mon 09/29/2014 20:15:55.75
 
Splice

Splice

Senior Member
Joined
Feb 8, 2010
Messages
655
Get an "80 was unexpected at this time" message at the end. 0 results then
 
Iwojima

Iwojima

Expert Member
Joined
Jan 16, 2007
Messages
4,271
Fighting a strange intermittent loss of speed on various protocols on Openweb Business Uncapped/Unshaped

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 24ms
Your maximum ping was 63ms

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 intermittant issue on the line. If required, please post the results to a forum post.

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 196.210.155.129 with 32 bytes of data:
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=25ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=63ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254

Ping statistics for 196.210.155.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 63ms, Average = 24ms

2014/09/30 22:08:00.47
 
B

Basjohn

Expert Member
Joined
Dec 12, 2005
Messages
1,033
Good stuff getting this stickied, probably the most helpful part of the forums for a loooong time to come because I don't see ISPs changing excuses anytime soon and this helps everyone from laymen to experts.
 
M

Magnarmalok

Expert Member
Joined
Oct 4, 2008
Messages
1,109
Just got the following.

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 196.215.192.1 with 32 bytes of data:
Reply from 196.215.192.1: bytes=32 time=216ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=226ms TTL=254
Reply from 196.215.192.1: bytes=32 time=208ms TTL=254
Reply from 196.215.192.1: bytes=32 time=252ms TTL=254
Reply from 196.215.192.1: bytes=32 time=278ms TTL=254
Reply from 196.215.192.1: bytes=32 time=234ms TTL=254
Reply from 196.215.192.1: bytes=32 time=246ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=195ms TTL=254
Reply from 196.215.192.1: bytes=32 time=288ms TTL=254
Reply from 196.215.192.1: bytes=32 time=48ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=267ms TTL=254
Reply from 196.215.192.1: bytes=32 time=198ms TTL=254
Reply from 196.215.192.1: bytes=32 time=180ms TTL=254
Reply from 196.215.192.1: bytes=32 time=300ms TTL=254
Reply from 196.215.192.1: bytes=32 time=176ms TTL=254
Reply from 196.215.192.1: bytes=32 time=214ms TTL=254
Reply from 196.215.192.1: bytes=32 time=231ms TTL=254
Reply from 196.215.192.1: bytes=32 time=237ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=284ms TTL=254
Reply from 196.215.192.1: bytes=32 time=201ms TTL=254
Reply from 196.215.192.1: bytes=32 time=259ms TTL=254
Reply from 196.215.192.1: bytes=32 time=199ms TTL=254
Reply from 196.215.192.1: bytes=32 time=250ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=213ms TTL=254
Request timed out.

Ping statistics for 196.215.192.1:
Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 300ms, Average = 225ms

Thu 10/02/2014 0:19:12.20
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Magnarmalok said:
Just got the following.

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 196.215.192.1 with 32 bytes of data:
Reply from 196.215.192.1: bytes=32 time=216ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=226ms TTL=254
Reply from 196.215.192.1: bytes=32 time=208ms TTL=254
Reply from 196.215.192.1: bytes=32 time=252ms TTL=254
Reply from 196.215.192.1: bytes=32 time=278ms TTL=254
Reply from 196.215.192.1: bytes=32 time=234ms TTL=254
Reply from 196.215.192.1: bytes=32 time=246ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=195ms TTL=254
Reply from 196.215.192.1: bytes=32 time=288ms TTL=254
Reply from 196.215.192.1: bytes=32 time=48ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=267ms TTL=254
Reply from 196.215.192.1: bytes=32 time=198ms TTL=254
Reply from 196.215.192.1: bytes=32 time=180ms TTL=254
Reply from 196.215.192.1: bytes=32 time=300ms TTL=254
Reply from 196.215.192.1: bytes=32 time=176ms TTL=254
Reply from 196.215.192.1: bytes=32 time=214ms TTL=254
Reply from 196.215.192.1: bytes=32 time=231ms TTL=254
Reply from 196.215.192.1: bytes=32 time=237ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=284ms TTL=254
Reply from 196.215.192.1: bytes=32 time=201ms TTL=254
Reply from 196.215.192.1: bytes=32 time=259ms TTL=254
Reply from 196.215.192.1: bytes=32 time=199ms TTL=254
Reply from 196.215.192.1: bytes=32 time=250ms TTL=254
Request timed out.
Reply from 196.215.192.1: bytes=32 time=213ms TTL=254
Request timed out.

Ping statistics for 196.215.192.1:
Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 300ms, Average = 225ms

Thu 10/02/2014 0:19:12.20
Click to expand...

Looks horrible :(

Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Basjohn said:
Good stuff getting this stickied, probably the most helpful part of the forums for a loooong time to come because I don't see ISPs changing excuses anytime soon and this helps everyone from laymen to experts.
Click to expand...

Thanks :D

Appreciate it,
Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Iwojima said:
Fighting a strange intermittent loss of speed on various protocols on Openweb Business Uncapped/Unshaped

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 24ms
Your maximum ping was 63ms

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 intermittant issue on the line. If required, please post the results to a forum post.

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 196.210.155.129 with 32 bytes of data:
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=25ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=23ms TTL=254
Reply from 196.210.155.129: bytes=32 time=63ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254
Reply from 196.210.155.129: bytes=32 time=24ms TTL=254

Ping statistics for 196.210.155.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 63ms, Average = 24ms

2014/09/30 22:08:00.47
Click to expand...

Looks fine? Just one jump? Are you connected via Wifi?

Z
 
SlowInternet

SlowInternet

Executive Member
Joined
Oct 11, 2006
Messages
8,322
This tool is not working for me.

Finding IP address - Done
Pinging IP address - Done

Press any key to continue..
Click to expand...

When I press any key it closes.....doesn't show any results
 
You must log in or register to reply here.
Top