"Is it my Line" Report Tool


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

Your average ping was 10ms
Your maximum ping was 31ms

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 105.236.6.129 with 32 bytes of data:
Reply from 105.236.6.129: bytes=32 time=13ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=11ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=11ms TTL=254
Reply from 105.236.6.129: bytes=32 time=13ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Request timed out.
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=14ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=9ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=10ms TTL=254
Reply from 105.236.6.129: bytes=32 time=31ms TTL=254

Ping statistics for 105.236.6.129:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 31ms, Average = 10ms
 
08-May-14 10:52:11.77

Hey Man!

It looks like you have a timeout or two on your connection :/ How does the line perform on other ISP accounts?

Z
 
FYI:

80 was unexpected at this time.

Something to implement in the future, if the program cant run a log saying that instead of the screen just going AWOL? I had to do the "advanced" one to get that message. Going to try a different ISP now...

*edit*

Yeah different ISP credentials same result. It is not finding my IP, thats where it times out.
 
Last edited:
FYI:



Something to implement in the future, if the program cant run a log saying that instead of the screen just going AWOL? I had to do the "advanced" one to get that message. Going to try a different ISP now...

*edit*

Yeah different ISP credentials same result. It is not finding my IP, thats where it times out.

Okay cool!

Thanks for the feedback, I'll implement a error for this. It seems as though your firewall is blocking pings.

Could you try with your firewall disabled :)

Z
 
Hi Everyone,

As a response my my previous tool - I have created a new tool to help diagnose line faults. Basically - it pings the last possible IP on the telkom network, in order to help find an intermittent exchange fault. It also display's the results to the user in a friendly, understandable, way :)

I am very strict with regards to malware, and will never distribute something that potentially has any form of harmful file attached to it. You are free to test the downloads yourself, but I assure you, there is nothing malicious inside the file.

Enjoy!
Z

DOWNLOADS:
EXE (Easy) - http://zertop.com/files/LineTool/Windows/Current/linetool.exe
ZIP (Advanced-ish) - http://zertop.com/files/LineTool/Windows/Current/linetool.zip

Bitdefender Antimalware Filter blocks this. I know it's a false positive, but I thought you should know.

Edit: It's not the files themselves, Bitdefender seems to have something against Zertop.com. Was your site hacked recently maybe?

See here: http://trafficlight.bitdefender.com/info?url=http%3A//zertop.com/&language=en_US

Edit 2: Is this your host? http://trafficlight.bitdefender.com/info?url=http%3A%2F%2Fwww.hostinger.co.uk%2F%3F&language=en_US

That might explain it.
 
Last edited:
Bitdefender Antimalware Filter blocks this. I know it's a false positive, but I thought you should know.

Edit: It's not the files themselves, Bitdefender seems to have something against Zertop.com. Was your site hacked recently maybe?

See here: http://trafficlight.bitdefender.com/info?url=http%3A//zertop.com/&language=en_US

Edit 2: Is this your host? http://trafficlight.bitdefender.com/info?url=http%3A%2F%2Fwww.hostinger.co.uk%2F%3F&language=en_US

That might explain it.

Nope - but I'll move over my domain to my new VPS sooner than later ;)

That's a bit weird, but my site is fine as it is literally just a html page with an image haha - I just use it to host files.

Thanks for the heads-up though, ill try sort this out!

Z
 
Nope - but I'll move over my domain to my new VPS sooner than later ;)

That's a bit weird, but my site is fine as it is literally just a html page with an image haha - I just use it to host files.

Thanks for the heads-up though, ill try sort this out!

Z

The reason I asked if you were hosting with hostinger.co.uk is if you make a typo it redirects.

See here: http://zertop.com/files/LineTool/Win/Current/linetool.zip

I just changed /Windows to /Win

I'm thinking it's maybe the redirect that Bitdefender doesn't like.
 
Line seems to be dropping a lot... and SNR is way higher than usual.
Advise please?

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

Pinging 105.224.100.1 with 32 bytes of data:
Reply from 105.224.100.1: bytes=32 time=32ms TTL=254
Reply from 105.224.100.1: bytes=32 time=23ms TTL=254
Reply from 105.224.100.1: bytes=32 time=29ms TTL=254
Reply from 105.224.100.1: bytes=32 time=13ms TTL=254
Reply from 105.224.100.1: bytes=32 time=51ms TTL=254
Reply from 105.224.100.1: bytes=32 time=13ms TTL=254
Reply from 105.224.100.1: bytes=32 time=45ms TTL=254
Reply from 105.224.100.1: bytes=32 time=14ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=34ms TTL=254
Reply from 105.224.100.1: bytes=32 time=113ms TTL=254
Reply from 105.224.100.1: bytes=32 time=11ms TTL=254
Reply from 105.224.100.1: bytes=32 time=15ms TTL=254
Reply from 105.224.100.1: bytes=32 time=17ms TTL=254
Reply from 105.224.100.1: bytes=32 time=18ms TTL=254
Reply from 105.224.100.1: bytes=32 time=21ms TTL=254
Reply from 105.224.100.1: bytes=32 time=74ms TTL=254
Reply from 105.224.100.1: bytes=32 time=24ms TTL=254
Reply from 105.224.100.1: bytes=32 time=14ms TTL=254
Reply from 105.224.100.1: bytes=32 time=11ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=23ms TTL=254
Reply from 105.224.100.1: bytes=32 time=44ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=14ms TTL=254
Reply from 105.224.100.1: bytes=32 time=32ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=11ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254

Ping statistics for 105.224.100.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 113ms, Average = 25ms
 
Line seems to be dropping a lot... and SNR is way higher than usual.
Advise please?

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

Pinging 105.224.100.1 with 32 bytes of data:
Reply from 105.224.100.1: bytes=32 time=32ms TTL=254
Reply from 105.224.100.1: bytes=32 time=23ms TTL=254
Reply from 105.224.100.1: bytes=32 time=29ms TTL=254
Reply from 105.224.100.1: bytes=32 time=13ms TTL=254
Reply from 105.224.100.1: bytes=32 time=51ms TTL=254
Reply from 105.224.100.1: bytes=32 time=13ms TTL=254
Reply from 105.224.100.1: bytes=32 time=45ms TTL=254
Reply from 105.224.100.1: bytes=32 time=14ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=34ms TTL=254
Reply from 105.224.100.1: bytes=32 time=113ms TTL=254
Reply from 105.224.100.1: bytes=32 time=11ms TTL=254
Reply from 105.224.100.1: bytes=32 time=15ms TTL=254
Reply from 105.224.100.1: bytes=32 time=17ms TTL=254
Reply from 105.224.100.1: bytes=32 time=18ms TTL=254
Reply from 105.224.100.1: bytes=32 time=21ms TTL=254
Reply from 105.224.100.1: bytes=32 time=74ms TTL=254
Reply from 105.224.100.1: bytes=32 time=24ms TTL=254
Reply from 105.224.100.1: bytes=32 time=14ms TTL=254
Reply from 105.224.100.1: bytes=32 time=11ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=23ms TTL=254
Reply from 105.224.100.1: bytes=32 time=44ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=14ms TTL=254
Reply from 105.224.100.1: bytes=32 time=32ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254
Reply from 105.224.100.1: bytes=32 time=11ms TTL=254
Reply from 105.224.100.1: bytes=32 time=12ms TTL=254

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

Looks like there might be a line issue :/

Please would you check all your POTS (ADSL Phone) filters are still working :) (You shouldn't hear any crackling on the line)

Z :)
 
Hi,
I'm unsure what the problem might be but my results are as follow(I'm still very new to the dsl market ._.)

PingResults file:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Bad parameter *.

2014/05/25 14:45:33.56

intelreport file:
Your average ping was =ms
Your maximum ping was =ms


I'm unsure if it's a problem with the tool or my line(Pretty sure its the line :P ), I've tried doing tracerts through the cmd prompt window but it times out on every hop till the 11-13th one. I myself don't know what this means tho.

Can you maybe point me in the right direction, as to if I should contact my ISP or Telkom to try find out why this is so?
Line is a 4MB Uncapped, line managed by Telkom.
(Been getting pretty high latency these past weeks so it's beginning to frustrate me not knowing @_@)
From the replies on this forum this tool looks like a great one to use for line fault testing and I hope I'll be able to get it working soon :)
 
Hi,
I'm unsure what the problem might be but my results are as follow(I'm still very new to the dsl market ._.)

PingResults file:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Bad parameter *.

2014/05/25 14:45:33.56

intelreport file:
Your average ping was =ms
Your maximum ping was =ms


I'm unsure if it's a problem with the tool or my line(Pretty sure its the line :P ), I've tried doing tracerts through the cmd prompt window but it times out on every hop till the 11-13th one. I myself don't know what this means tho.

Can you maybe point me in the right direction, as to if I should contact my ISP or Telkom to try find out why this is so?
Line is a 4MB Uncapped, line managed by Telkom.
(Been getting pretty high latency these past weeks so it's beginning to frustrate me not knowing @_@)
From the replies on this forum this tool looks like a great one to use for line fault testing and I hope I'll be able to get it working soon :)

Hi TiCKoMasta,

I will be fixing this in the next release to display a better error message that what currently happens :) Basically, what has happened is that something is blocking the request to get the IP we need to do the tests. Do you have any firewalls installed?

Z :)
 
using Zertop's report tool .. I have a Telkom ISP 4Mbps line. Local exchange only supports up to 4Mbps connection.
Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 12 ms 11 ms 12 ms ti-224-92-01.telkomadsl.co.za [105.224.92.1]
3 14 ms 14 ms 12 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246]
4 14 ms 14 ms 13 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 13 ms 13 ms 12 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 14 ms 13 ms 14 ms 196.43.11.218
7 13 ms 20 ms 13 ms 196.43.25.206
8 * 15 ms 13 ms gigabitethernet1-1-1.cpt-pr-1.mweb.co.za [197.84.4.22]
9 17 ms 18 ms 19 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 14 ms 14 ms 13 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 15 ms 14 ms 14 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 15 ms 14 ms 13 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 16 ms 14 ms 14 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 15 ms 14 ms 15 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 14 ms 14 ms 15 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Billion.400G [10.0.0.2]
2 12 ms 11 ms 10 ms ti-224-92-01.telkomadsl.co.za [105.224.92.1]
3 15 ms 13 ms 13 ms ti-226-0-06.telkomadsl.co.za [105.226.0.6]
4 14 ms 13 ms 13 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 153 ms 136 ms 120 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 37 ms * 37 ms nngy-ip-hsll-1-gig-4-0-0.telkom-ipnet.co.za [196.43.51.254]
7 125 ms 125 ms * if-3-0-1.core1.COV-Cochin.as6453.net [116.0.85.1]
8 163 ms 163 ms 163 ms if-4-0-0.core1.MLV-Mumbai.as6453.net [209.58.105.37]
9 414 ms 417 ms 465 ms if-1-2-1-0.tcore1.MLV-Mumbai.as6453.net [209.58.105.226]
10 266 ms * * if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17]
11 273 ms 273 ms 273 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6]
12 265 ms 271 ms 265 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17]
13 237 ms 237 ms 237 ms ge-11-2-1.mpr1.cdg11.fr.above.net [64.125.14.57]
14 238 ms 242 ms 243 ms ae2.mpr2.cdg12.fr.above.net [64.125.26.74]
15 230 ms 230 ms 231 ms ae3.mpr2.lhr2.uk.above.net [64.125.32.98]
16 233 ms 233 ms * ae5.mpr1.lhr15.uk.above.net [64.125.21.10]
17 227 ms 227 ms 226 ms 94.31.40.154.IPYX-080002-001-ZYO.above.net [94.31.40.154]
18 233 ms 233 ms 235 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
19 237 ms 238 ms 237 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 10.0 megabytes in 56 seconds. (179.84 KB/s)

Local Speedtest
Downloaded 8000.0 kilobytes in 24 seconds. (320.79 KB/s)




Test End Timestamp
2014-05-25 15:07:40.75
 
Hi Z,

Windows Firewall Status is set to Off, just Microsoft Security Essentials running.
Might it be a setting on the router which is blocking the requests? I've not made any advance setting changes on the router regarding firewalls or anything.

I'll do some google'ing to see what might be giving the request timeouts on all those hops. Might end up being something small, thank you for the feedback. :)
 
Hi Z,

Windows Firewall Status is set to Off, just Microsoft Security Essentials running.
Might it be a setting on the router which is blocking the requests? I've not made any advance setting changes on the router regarding firewalls or anything.

I'll do some google'ing to see what might be giving the request timeouts on all those hops. Might end up being something small, thank you for the feedback. :)

You installed avast? :P

No probs - anytime :) That definitely sounds like a firewall issue to me. What software have you recently installed?

Z
 
Haven't installed Avast on any PC I've owned before, have seen it in action >.<

No software which I think might be causing the block.
When you asked about the software installed I thought about MSSQL 2008, which I've had installed before I got DSL, don't know if that has any networking services running which might cause a block like this. Got NetBrute installed but that is also I think just a executable tool which don't have services running while the application is not open. The rest of the applications are just the normal Steam, Origin, Skype kind of apps.

I can maybe run Wireshark and see what is happening while I try do a tracert... but then I need to run through all those wireshark logs @_@

When I do a Diagnostic run for "Test Internet surfing" on the router, I do see the following 3 not passing:
ATM OAM Segment Ping - Skip
ATM OAM end to end Ping - Skip
Test DNS Root - Fail

Going to start up the Wireshark quickly and see what I can figure out, thank for the help so far much appreciate! :)
 
Haven't installed Avast on any PC I've owned before, have seen it in action >.<

No software which I think might be causing the block.
When you asked about the software installed I thought about MSSQL 2008, which I've had installed before I got DSL, don't know if that has any networking services running which might cause a block like this. Got NetBrute installed but that is also I think just a executable tool which don't have services running while the application is not open. The rest of the applications are just the normal Steam, Origin, Skype kind of apps.

I can maybe run Wireshark and see what is happening while I try do a tracert... but then I need to run through all those wireshark logs @_@

When I do a Diagnostic run for "Test Internet surfing" on the router, I do see the following 3 not passing:
ATM OAM Segment Ping - Skip
ATM OAM end to end Ping - Skip
Test DNS Root - Fail

Going to start up the Wireshark quickly and see what I can figure out, thank for the help so far much appreciate! :)

Okay wait.

Try using 8.8.8.8 as your DNS and do a tracert for me :)

Z
 
Okay wait.

Try using 8.8.8.8 as your DNS and do a tracert for me :)

Z

After setting the DNS manualy.

Tracing route to www.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 364 ms 271 ms 289 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Tracing route to www.google.com [74.125.233.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 550 ms 540 ms 522 ms jnb01s02-in-f17.1e100.net [74.125.233.81]

Trace complete.

Basicly doing this to any destination I tracert to. x_x
Maybe the Wireshark logs will reveal something, crossing fingers :P
 
Top
Sign up to the MyBroadband newsletter
X