"Is it my Line" Report Tool

Zertop · Mar 28, 2014

"Is it my Line" Report Tool [V2]

Hi All,
This tool pings the last possible hardware on the telkom network - to help deduce whether a fault lies with Telkom or with the user's ISP

I am very strict with regards to malware, and will never distribute something that potentially has any form of harmful file attached to it.

Download JAR: https://zertop.github.io/releases/latest/

Download Android App: https://github.com/Zertop/LineToolAndroid/releases

Changelog: https://github.com/Zertop/LineTool/releases

sybertiger · Mar 28, 2014

nice tool

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

Pinging 196.215.156.1 with 32 bytes of data:
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=10ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254

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

Fri 03/28/2014 20:51:36.65

Zertop · Mar 28, 2014

sybertiger said:
nice tool

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

Pinging 196.215.156.1 with 32 bytes of data:
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=10ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254
Reply from 196.215.156.1: bytes=32 time=9ms TTL=254

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

Fri 03/28/2014 20:51:36.65

Solid Stuff

Thanks

PhireSide · Mar 28, 2014

Your tool just called my line dodgy! JK, here is my result (WA 4meg capped account):

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

Pinging 196.210.145.129 with 32 bytes of data:
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
Reply from 196.210.145.129: bytes=32 time=28ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=30ms TTL=254
Reply from 196.210.145.129: bytes=32 time=35ms TTL=254
Reply from 196.210.145.129: bytes=32 time=32ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
Reply from 196.210.145.129: bytes=32 time=35ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=30ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
Reply from 196.210.145.129: bytes=32 time=31ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=30ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=37ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=34ms TTL=254
Reply from 196.210.145.129: bytes=32 time=41ms TTL=254
Reply from 196.210.145.129: bytes=32 time=33ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254
Reply from 196.210.145.129: bytes=32 time=29ms TTL=254

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

2014/03/28 21:13:22.05

EDIT: I am using a wireless USB stick (Draft N 300mpbs )connected to a router down the passage, if it makes any difference. Landlord said we aren't allowed to run cables

(-(-_(-_-)_-)-) · Mar 28, 2014

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

Pinging 105.224.132.1 with 32 bytes of data:
Reply from 105.224.132.1: bytes=32 time=759ms TTL=254
Reply from 105.224.132.1: bytes=32 time=824ms TTL=254
Reply from 105.224.132.1: bytes=32 time=864ms TTL=254
Reply from 105.224.132.1: bytes=32 time=847ms TTL=254
Reply from 105.224.132.1: bytes=32 time=819ms TTL=254
Reply from 105.224.132.1: bytes=32 time=769ms TTL=254
Reply from 105.224.132.1: bytes=32 time=825ms TTL=254
Reply from 105.224.132.1: bytes=32 time=947ms TTL=254
Reply from 105.224.132.1: bytes=32 time=893ms TTL=254
Reply from 105.224.132.1: bytes=32 time=792ms TTL=254
Reply from 105.224.132.1: bytes=32 time=855ms TTL=254
Reply from 105.224.132.1: bytes=32 time=866ms TTL=254
Reply from 105.224.132.1: bytes=32 time=802ms TTL=254
Reply from 105.224.132.1: bytes=32 time=720ms TTL=254
Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
Reply from 105.224.132.1: bytes=32 time=790ms TTL=254
Reply from 105.224.132.1: bytes=32 time=838ms TTL=254
Reply from 105.224.132.1: bytes=32 time=933ms TTL=254
Reply from 105.224.132.1: bytes=32 time=932ms TTL=254
Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
Reply from 105.224.132.1: bytes=32 time=612ms TTL=254
Reply from 105.224.132.1: bytes=32 time=575ms TTL=254
Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
Reply from 105.224.132.1: bytes=32 time=737ms TTL=254
Reply from 105.224.132.1: bytes=32 time=776ms TTL=254
Reply from 105.224.132.1: bytes=32 time=788ms TTL=254
Reply from 105.224.132.1: bytes=32 time=842ms TTL=254
Reply from 105.224.132.1: bytes=32 time=869ms TTL=254
Reply from 105.224.132.1: bytes=32 time=908ms TTL=254

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

2014/03/28 21:29:20.67

fault is being fixed though

MickeyD · Mar 28, 2014

running tool

cannot create the text file...

Zertop · Mar 28, 2014

MickeyD said:
running tool

cannot create the text file...

Did you extract the file?

If so - please PM me with the full output on screen

Z

Zertop · Mar 28, 2014

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

Pinging 105.224.132.1 with 32 bytes of data:
Reply from 105.224.132.1: bytes=32 time=759ms TTL=254
Reply from 105.224.132.1: bytes=32 time=824ms TTL=254
Reply from 105.224.132.1: bytes=32 time=864ms TTL=254
Reply from 105.224.132.1: bytes=32 time=847ms TTL=254
Reply from 105.224.132.1: bytes=32 time=819ms TTL=254
Reply from 105.224.132.1: bytes=32 time=769ms TTL=254
Reply from 105.224.132.1: bytes=32 time=825ms TTL=254
Reply from 105.224.132.1: bytes=32 time=947ms TTL=254
Reply from 105.224.132.1: bytes=32 time=893ms TTL=254
Reply from 105.224.132.1: bytes=32 time=792ms TTL=254
Reply from 105.224.132.1: bytes=32 time=855ms TTL=254
Reply from 105.224.132.1: bytes=32 time=866ms TTL=254
Reply from 105.224.132.1: bytes=32 time=802ms TTL=254
Reply from 105.224.132.1: bytes=32 time=720ms TTL=254
Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
Reply from 105.224.132.1: bytes=32 time=790ms TTL=254
Reply from 105.224.132.1: bytes=32 time=838ms TTL=254
Reply from 105.224.132.1: bytes=32 time=933ms TTL=254
Reply from 105.224.132.1: bytes=32 time=932ms TTL=254
Reply from 105.224.132.1: bytes=32 time=718ms TTL=254
Reply from 105.224.132.1: bytes=32 time=612ms TTL=254
Reply from 105.224.132.1: bytes=32 time=575ms TTL=254
Reply from 105.224.132.1: bytes=32 time=688ms TTL=254
Reply from 105.224.132.1: bytes=32 time=737ms TTL=254
Reply from 105.224.132.1: bytes=32 time=776ms TTL=254
Reply from 105.224.132.1: bytes=32 time=788ms TTL=254
Reply from 105.224.132.1: bytes=32 time=842ms TTL=254
Reply from 105.224.132.1: bytes=32 time=869ms TTL=254
Reply from 105.224.132.1: bytes=32 time=908ms TTL=254

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

2014/03/28 21:29:20.67

fault is being fixed though

I was about to say :wtf:

Haha - hope it gets fixed soon

Z

Zertop · Mar 28, 2014

wabbit16 said:
Your tool just called my line dodgy! JK, here is my result (WA 4meg capped account):

EDIT: I am using a wireless USB stick (Draft N 300mpbs )connected to a router down the passage, if it makes any difference. Landlord said we aren't allowed to run cables

Haha - Yea thats probably it

Long-Distance wifi does influence ping

Z

MickeyD · Mar 28, 2014

Zertop said:
Did you extract the file?

If so - please PM me with the full output on screen

Z

EXE file gives the issue.
Saved the ZIP file - works.
******************

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

Pinging 105.224.168.1 with 32 bytes of data:

Reply from 105.224.168.1: bytes=32 time=28ms TTL=254
Reply from 105.224.168.1: bytes=32 time=27ms TTL=254
Reply from 105.224.168.1: bytes=32 time=90ms TTL=254
Reply from 105.224.168.1: bytes=32 time=39ms TTL=254
Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
Reply from 105.224.168.1: bytes=32 time=30ms TTL=254
Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
Reply from 105.224.168.1: bytes=32 time=31ms TTL=254
Reply from 105.224.168.1: bytes=32 time=29ms TTL=254
Reply from 105.224.168.1: bytes=32 time=29ms TTL=254
Reply from 105.224.168.1: bytes=32 time=35ms TTL=254
Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
Reply from 105.224.168.1: bytes=32 time=43ms TTL=254
Reply from 105.224.168.1: bytes=32 time=140ms TTL=254
Reply from 105.224.168.1: bytes=32 time=129ms TTL=254
Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
Reply from 105.224.168.1: bytes=32 time=43ms TTL=254
Reply from 105.224.168.1: bytes=32 time=47ms TTL=254
Reply from 105.224.168.1: bytes=32 time=85ms TTL=254
Reply from 105.224.168.1: bytes=32 time=63ms TTL=254
Reply from 105.224.168.1: bytes=32 time=47ms TTL=254
Reply from 105.224.168.1: bytes=32 time=60ms TTL=254
Reply from 105.224.168.1: bytes=32 time=91ms TTL=254
Reply from 105.224.168.1: bytes=32 time=81ms TTL=254
Reply from 105.224.168.1: bytes=32 time=56ms TTL=254
Reply from 105.224.168.1: bytes=32 time=26ms TTL=254
Reply from 105.224.168.1: bytes=32 time=27ms TTL=254
Reply from 105.224.168.1: bytes=32 time=27ms TTL=254
Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Ping statistics for 105.224.168.1:

Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 26ms, Maximum = 140ms, Average = 48ms

2014/03/28 21:57:12.37

Zertop · Mar 28, 2014

MickeyD said:
EXE file gives the issue.
Saved the ZIP file - works.
2014/03/28 21:57:12.37

Okay cool - I'll look into it!

Z

Zertop · Mar 28, 2014

UPDATE:
-Fixed error when text file is deleted before it is opened. (Thanks MickyD).
-Results are now attached to the clipboard.
-Fixed intelligence report on Good result.

Z

DrJohnZoidberg · Mar 28, 2014

Nice work Zertop.

One idea to get the correct external IP is to start from the top (of the traceroute) and accept the first IP which is not a private address and is not the clients IP.

Zertop · Mar 28, 2014

DrJohnZoidberg said:
Nice work Zertop.

One idea to get the correct external IP is to start from the top (of the traceroute) and accept the first IP which is not a private address and is not the clients IP.

Thanks Man!

Good Idea - I will try implement that

wingnut771 · Mar 28, 2014

VOX:

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

Pinging 197.245.30.1 with 32 bytes of data:
Reply from 197.245.30.1: bytes=32 time=22ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254
Reply from 197.245.30.1: bytes=32 time=20ms TTL=254
Reply from 197.245.30.1: bytes=32 time=21ms TTL=254

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

2014/03/28 23:09:39.54

Connection:

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

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

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

2014/03/28 23:14:25.03

Fulton17 · Mar 29, 2014

WA 10 meg line

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

Pinging 196.210.130.1 with 32 bytes of data:
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=10ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=17ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=18ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=9ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254
Reply from 196.210.130.1: bytes=32 time=8ms TTL=254

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

2014/03/29 7:51:37.28

Empie · Mar 29, 2014

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=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=13ms TTL=254
Reply from 196.215.192.1: bytes=32 time=16ms TTL=254
Reply from 196.215.192.1: bytes=32 time=16ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=16ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=22ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=16ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=15ms TTL=254
Reply from 196.215.192.1: bytes=32 time=16ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254
Reply from 196.215.192.1: bytes=32 time=14ms TTL=254

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

Sat 03/29/2014 12:20:44.31

Yet I'm getting a 1Mbps speed on a 2Mbps line for the last week. So it's save to say that WA needs to sort something out on their end? Unless they throttled me :/

Basjohn · Mar 31, 2014

Brilliant tool to help see where the blame REALLY sits, considering how Telkom will blame the ISP and the ISP will blame Telkom in and endless cycle.

I'd really suggest a sticky for this one, the other tool is insightful, but this one is very very useful in diagnosis locally.

[EDIT] My only suggestion would be to print the line about the fault being with the ISP in the results.txt, it would make things easier when fussing it out with tech support bottom tier drones.

atomcrusher · Mar 31, 2014

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

Pinging 105.224.92.1 with 32 bytes of data:
Reply from 105.224.92.1: bytes=32 time=16ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=16ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=17ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=16ms TTL=254
Reply from 105.224.92.1: bytes=32 time=17ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=14ms TTL=254
Reply from 105.224.92.1: bytes=32 time=15ms TTL=254

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

2014-03-31 15:28:47.50

LCBXX · Mar 31, 2014

Cool stuff, thanks!

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Expert Member

Expert Member

Expert Member

Honorary Master

Active Member

RIP

Expert Member

Expert Member

Expert Member

RIP

Expert Member

Expert Member

Honorary Master

Expert Member

Honorary Master

Expert Member

Active Member

Expert Member

Expert Member

Honorary Master