"Is it my Line" Report Tool

Drifter

Drifter

Honorary Master
Joined
Dec 19, 2012
Messages
22,825
Hang on, I got the 3 .txt reports in the main folder, even though it showed a crash. averagereport.txt intereport.txt and Ping Results.txt

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

Pinging 41.132.72.1 with 32 bytes of data:
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=11ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=11ms TTL=254
Reply from 41.132.72.1: bytes=32 time=11ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254

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

2014/08/13 16:29:00.24
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Gerhardva said:
Hang on, I got the 3 .txt reports in the main folder, even though it showed a crash. averagereport.txt intereport.txt and Ping Results.txt

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

Pinging 41.132.72.1 with 32 bytes of data:
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=11ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254
Reply from 41.132.72.1: bytes=32 time=11ms TTL=254
Reply from 41.132.72.1: bytes=32 time=11ms TTL=254
Reply from 41.132.72.1: bytes=32 time=12ms TTL=254

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

2014/08/13 16:29:00.24
Click to expand...

Those look 100% to me!

Z
 
Necuno

Necuno

Court Jester
Joined
Sep 27, 2005
Messages
58,567
I got a strange error using this tool while being connected to a vpn... will report back.
 
J

jpgrobler

Well-Known Member
Joined
Aug 14, 2006
Messages
165
This is my results
What should I do?
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 224ms
Your maximum ping was 358ms

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

Pinging 197.245.1.1 with 32 bytes of data:
Reply from 197.245.1.1: bytes=32 time=189ms TTL=254
Reply from 197.245.1.1: bytes=32 time=219ms TTL=254
Reply from 197.245.1.1: bytes=32 time=329ms TTL=254
Reply from 197.245.1.1: bytes=32 time=234ms TTL=254
Reply from 197.245.1.1: bytes=32 time=158ms TTL=254
Reply from 197.245.1.1: bytes=32 time=285ms TTL=254
Reply from 197.245.1.1: bytes=32 time=328ms TTL=254
Reply from 197.245.1.1: bytes=32 time=242ms TTL=254
Reply from 197.245.1.1: bytes=32 time=258ms TTL=254
Reply from 197.245.1.1: bytes=32 time=301ms TTL=254
Reply from 197.245.1.1: bytes=32 time=343ms TTL=254
Reply from 197.245.1.1: bytes=32 time=320ms TTL=254
Reply from 197.245.1.1: bytes=32 time=217ms TTL=254
Reply from 197.245.1.1: bytes=32 time=296ms TTL=254
Reply from 197.245.1.1: bytes=32 time=191ms TTL=254
Reply from 197.245.1.1: bytes=32 time=162ms TTL=254
Reply from 197.245.1.1: bytes=32 time=175ms TTL=254
Reply from 197.245.1.1: bytes=32 time=142ms TTL=254
Reply from 197.245.1.1: bytes=32 time=206ms TTL=254
Reply from 197.245.1.1: bytes=32 time=227ms TTL=254
Reply from 197.245.1.1: bytes=32 time=160ms TTL=254
Request timed out.
Reply from 197.245.1.1: bytes=32 time=183ms TTL=254
Reply from 197.245.1.1: bytes=32 time=263ms TTL=254
Reply from 197.245.1.1: bytes=32 time=30ms TTL=254
Reply from 197.245.1.1: bytes=32 time=358ms TTL=254
Reply from 197.245.1.1: bytes=32 time=268ms TTL=254
Reply from 197.245.1.1: bytes=32 time=25ms TTL=254
Reply from 197.245.1.1: bytes=32 time=276ms TTL=254
Reply from 197.245.1.1: bytes=32 time=126ms TTL=254

Ping statistics for 197.245.1.1:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 358ms, Average = 224ms

14/08/2014 17:35:12.24
 
E

ellis

Active Member
Joined
Apr 7, 2014
Messages
37
Hi, not sure if it was mentioned before, but my avast just picked up a threat (I chose the .exe file), and moved it to the chest.
Yes I did read the first post regarding malware, I just though OP might want to know
 
Drifter

Drifter

Honorary Master
Joined
Dec 19, 2012
Messages
22,825
The tool is crashing for me now, not generating report. just says IP must be specified.
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Im so sorry guys, been extremely busy!

I'll get it sorted ASAP!

Z :)
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
ellis said:
Hi, not sure if it was mentioned before, but my avast just picked up a threat (I chose the .exe file), and moved it to the chest.
Yes I did read the first post regarding malware, I just though OP might want to know
Click to expand...

Thanks! Ill check it out :)
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
jpgrobler said:
This is my results
What should I do?
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 224ms
Your maximum ping was 358ms

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

Pinging 197.245.1.1 with 32 bytes of data:
Reply from 197.245.1.1: bytes=32 time=189ms TTL=254
Reply from 197.245.1.1: bytes=32 time=219ms TTL=254
Reply from 197.245.1.1: bytes=32 time=329ms TTL=254
Reply from 197.245.1.1: bytes=32 time=234ms TTL=254
Reply from 197.245.1.1: bytes=32 time=158ms TTL=254
Reply from 197.245.1.1: bytes=32 time=285ms TTL=254
Reply from 197.245.1.1: bytes=32 time=328ms TTL=254
Reply from 197.245.1.1: bytes=32 time=242ms TTL=254
Reply from 197.245.1.1: bytes=32 time=258ms TTL=254
Reply from 197.245.1.1: bytes=32 time=301ms TTL=254
Reply from 197.245.1.1: bytes=32 time=343ms TTL=254
Reply from 197.245.1.1: bytes=32 time=320ms TTL=254
Reply from 197.245.1.1: bytes=32 time=217ms TTL=254
Reply from 197.245.1.1: bytes=32 time=296ms TTL=254
Reply from 197.245.1.1: bytes=32 time=191ms TTL=254
Reply from 197.245.1.1: bytes=32 time=162ms TTL=254
Reply from 197.245.1.1: bytes=32 time=175ms TTL=254
Reply from 197.245.1.1: bytes=32 time=142ms TTL=254
Reply from 197.245.1.1: bytes=32 time=206ms TTL=254
Reply from 197.245.1.1: bytes=32 time=227ms TTL=254
Reply from 197.245.1.1: bytes=32 time=160ms TTL=254
Request timed out.
Reply from 197.245.1.1: bytes=32 time=183ms TTL=254
Reply from 197.245.1.1: bytes=32 time=263ms TTL=254
Reply from 197.245.1.1: bytes=32 time=30ms TTL=254
Reply from 197.245.1.1: bytes=32 time=358ms TTL=254
Reply from 197.245.1.1: bytes=32 time=268ms TTL=254
Reply from 197.245.1.1: bytes=32 time=25ms TTL=254
Reply from 197.245.1.1: bytes=32 time=276ms TTL=254
Reply from 197.245.1.1: bytes=32 time=126ms TTL=254

Ping statistics for 197.245.1.1:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 358ms, Average = 224ms

14/08/2014 17:35:12.24
Click to expand...

Definitely a line issue :(

Z
 
B

Basjohn

Expert Member
Joined
Dec 12, 2005
Messages
1,033
Why has this not been stickied yet??? Has the request been made to RPM or another mod?
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Hi!

If anyone is having issues - please would you PM me :)

Thanks,
Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Update!

26-09-2014
- Fixed general bugs. Auto update improved (this update must be done manually).
 
B

Bufamotis

Senior Member
Joined
May 8, 2011
Messages
505
Mkay, So apparently there's an issue with my line. I complained to Afrihost about my ****ty line speeds and then came accross Z's tool.

O great guru's, please decipher the meaning behind whatever there is to see here:


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

Your average ping was 450ms
Your maximum ping was 650ms

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.236.3.193 with 32 bytes of data:
Reply from 105.236.3.193: bytes=32 time=458ms TTL=254
Reply from 105.236.3.193: bytes=32 time=410ms TTL=254
Reply from 105.236.3.193: bytes=32 time=624ms TTL=254
Reply from 105.236.3.193: bytes=32 time=452ms TTL=254
Reply from 105.236.3.193: bytes=32 time=222ms TTL=254
Reply from 105.236.3.193: bytes=32 time=504ms TTL=254
Reply from 105.236.3.193: bytes=32 time=563ms TTL=254
Reply from 105.236.3.193: bytes=32 time=611ms TTL=254
Reply from 105.236.3.193: bytes=32 time=650ms TTL=254
Reply from 105.236.3.193: bytes=32 time=636ms TTL=254
Reply from 105.236.3.193: bytes=32 time=528ms TTL=254
Reply from 105.236.3.193: bytes=32 time=413ms TTL=254
Reply from 105.236.3.193: bytes=32 time=359ms TTL=254
Reply from 105.236.3.193: bytes=32 time=434ms TTL=254
Reply from 105.236.3.193: bytes=32 time=377ms TTL=254
Reply from 105.236.3.193: bytes=32 time=388ms TTL=254
Reply from 105.236.3.193: bytes=32 time=411ms TTL=254
Reply from 105.236.3.193: bytes=32 time=379ms TTL=254
Reply from 105.236.3.193: bytes=32 time=341ms TTL=254
Reply from 105.236.3.193: bytes=32 time=335ms TTL=254
Reply from 105.236.3.193: bytes=32 time=367ms TTL=254
Reply from 105.236.3.193: bytes=32 time=391ms TTL=254
Reply from 105.236.3.193: bytes=32 time=383ms TTL=254
Reply from 105.236.3.193: bytes=32 time=467ms TTL=254
Reply from 105.236.3.193: bytes=32 time=434ms TTL=254
Reply from 105.236.3.193: bytes=32 time=452ms TTL=254
Reply from 105.236.3.193: bytes=32 time=279ms TTL=254
Reply from 105.236.3.193: bytes=32 time=477ms TTL=254
Reply from 105.236.3.193: bytes=32 time=608ms TTL=254
Reply from 105.236.3.193: bytes=32 time=558ms TTL=254

Ping statistics for 105.236.3.193:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 222ms, Maximum = 650ms, Average = 450ms
 
2014-09-27 17:35:34,90
 
Last edited:
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Bufamotis said:
Mkay, So apparently there's an issue with my line. I complained to Afrihost about my ****ty line speeds and then came accross Z's tool.

O great guru's, please decipher the meaning behind whatever there is to see here:

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

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

Pinging 105.236.3.193 with 32 bytes of data:
Reply from 105.236.3.193: bytes=32 time=458ms TTL=254
Reply from 105.236.3.193: bytes=32 time=410ms TTL=254
Reply from 105.236.3.193: bytes=32 time=624ms TTL=254
Reply from 105.236.3.193: bytes=32 time=452ms TTL=254
Reply from 105.236.3.193: bytes=32 time=222ms TTL=254
Reply from 105.236.3.193: bytes=32 time=504ms TTL=254
Reply from 105.236.3.193: bytes=32 time=563ms TTL=254
Reply from 105.236.3.193: bytes=32 time=611ms TTL=254
Reply from 105.236.3.193: bytes=32 time=650ms TTL=254
Reply from 105.236.3.193: bytes=32 time=636ms TTL=254
Reply from 105.236.3.193: bytes=32 time=528ms TTL=254
Reply from 105.236.3.193: bytes=32 time=413ms TTL=254
Reply from 105.236.3.193: bytes=32 time=359ms TTL=254
Reply from 105.236.3.193: bytes=32 time=434ms TTL=254
Reply from 105.236.3.193: bytes=32 time=377ms TTL=254
Reply from 105.236.3.193: bytes=32 time=388ms TTL=254
Reply from 105.236.3.193: bytes=32 time=411ms TTL=254
Reply from 105.236.3.193: bytes=32 time=379ms TTL=254
Reply from 105.236.3.193: bytes=32 time=341ms TTL=254
Reply from 105.236.3.193: bytes=32 time=335ms TTL=254
Reply from 105.236.3.193: bytes=32 time=367ms TTL=254
Reply from 105.236.3.193: bytes=32 time=391ms TTL=254
Reply from 105.236.3.193: bytes=32 time=383ms TTL=254
Reply from 105.236.3.193: bytes=32 time=467ms TTL=254
Reply from 105.236.3.193: bytes=32 time=434ms TTL=254
Reply from 105.236.3.193: bytes=32 time=452ms TTL=254
Reply from 105.236.3.193: bytes=32 time=279ms TTL=254
Reply from 105.236.3.193: bytes=32 time=477ms TTL=254
Reply from 105.236.3.193: bytes=32 time=608ms TTL=254
Reply from 105.236.3.193: bytes=32 time=558ms TTL=254

Ping statistics for 105.236.3.193:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 222ms, Maximum = 650ms, Average = 450ms

2014-09-27 17:35:34,90
Click to expand...

Ooh that doesn't look fantastic - at all :/

Just to be sure - could you take out a few free GB's with Webafrica, and use that account to run the test again?

Z :)
 
You must log in or register to reply here.
Top