"Is it my Line" Report Tool

Zertop · Mar 20, 2015

New Update!

14. 20-03-2014
- Reintroduced Legacy (Original) method of capturing IP.
- Tool will now work with both old and new equipment.
- Special thanks to th0rn for finding an alternative IP to diagnose faults.

Z

Crystal Web · Mar 20, 2015

Zertop said:
New Update!

Z

Still testing the Telkom exchange and fails thereafter. As of next week nearly every exchange in SA will no longer respond to ping requests. Pity.

Zertop · Mar 20, 2015

Crystal Web said:
Still testing the Telkom exchange and fails thereafter. As of next week nearly every exchange in SA will no longer respond to ping requests. Pity.

Does it?

It should skip over it and use the new ip if it cannot ping the exchange... hmm... okay let me see.

Z

Crystal Web · Mar 20, 2015

Zertop said:
Does it?

It should skip over it and use the new ip if it cannot ping the exchange... hmm... okay let me see.

Z

Pinging the third hop won't work. Sorry to say. You've already moved over on to the ISP's network and have gone through a shaper at that point on most networks.

Zertop · Mar 20, 2015

Crystal Web said:
Pinging the third hop won't work. Sorry to say. You've already moved over on to the ISP's network and have gone through a shaper at that point on most networks.

As far as I understand, the IP I am pinging is completely separate to any ISP's network. Basically, I'm now pinging the Telkom Gateway directly. If you do a trace route to it - you'll see that it never enters an ISP's network, and pings only on the Telkom network. This is all in theory of course, but looks right!

155.239.255.250

Z

Crystal Web · Mar 20, 2015

Zertop said:
As far as I understand, the IP I am pinging is completely separate to any ISP's network. Basically, I'm now pinging the Telkom Gateway directly. If you do a trace route to it - you'll see that it never enters an ISP's network, and pings only on the Telkom network. This is all in theory of course, but looks right!

Z

Worked a little differently with the .exe I tested. May work that way, and may actually be even better than before. Will test once you confirm it's updated on your end.

Zertop · Mar 20, 2015

Crystal Web said:
Worked a little differently with the .exe I tested. May work that way, and may actually be even better than before. Will test once you confirm it's updated on your end.

Cool! New version wasn't properly uploaded -_-

Should be all good now.

Z

Yuu · Mar 22, 2015

Thanks for your awesome tool and for finding a workaround ^_^

Hey,

Pinging manually the address 155.239.255.250 works but with the tool [downloaded not long ago tonight] did not yield any results and says something is wrong.

Heres my results manually though.

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=895ms TTL=63
Reply from 155.239.255.250: bytes=32 time=411ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1429ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1274ms TTL=63
Reply from 155.239.255.250: bytes=32 time=73ms TTL=63
Reply from 155.239.255.250: bytes=32 time=72ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=265ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=225ms TTL=63
Reply from 155.239.255.250: bytes=32 time=78ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=328ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=369ms TTL=63
Reply from 155.239.255.250: bytes=32 time=163ms TTL=63

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

This only happens at night, if i do this later today, am sure it will look superb.

Heres hoping an upgrade will be done

.

Zertop · Mar 22, 2015

Yuu said:

Hey,

Pinging manually the address 155.239.255.250 works but with the tool [downloaded not long ago tonight] did not yield any results and says something is wrong.

Heres my results manually though.

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=895ms TTL=63
Reply from 155.239.255.250: bytes=32 time=411ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1429ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1274ms TTL=63
Reply from 155.239.255.250: bytes=32 time=73ms TTL=63
Reply from 155.239.255.250: bytes=32 time=72ms TTL=63
Reply from 155.239.255.250: bytes=32 time=122ms TTL=63
Reply from 155.239.255.250: bytes=32 time=265ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=226ms TTL=63
Reply from 155.239.255.250: bytes=32 time=225ms TTL=63
Reply from 155.239.255.250: bytes=32 time=78ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=328ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=369ms TTL=63
Reply from 155.239.255.250: bytes=32 time=163ms TTL=63

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

This only happens at night, if i do this later today, am sure it will look superb.

Heres hoping an upgrade will be done

.

I'm currently completely redesigning the app - so will have a new version available shortly.

Z

Zertop · Apr 8, 2015

New Update!

V2.1: 08-04-2015
- Tool now runs with Java
- Tool now cross-platform
- Tool works on new/old Telkom Systems

Please try it out, and give me some feedback

It is now cross platform, however have not tested all possible variations.

giggity · Apr 8, 2015

I'm getting an error that the file cannot be found. Can you try re-upload?

Zertop · Apr 8, 2015

giggity said:
I'm getting an error that the file cannot be found. Can you try re-upload?

Sorry - reshuffled my files around so busy uploading them all again. Will be 2 minutes

EDIT: Try now

electrofreeze · Apr 8, 2015

does this run on the mac as it does not work on mine

Zertop · Apr 8, 2015

electrofreeze said:
does this run on the mac as it does not work on mine

It is supposed to :/

Does it open?

Z

electrofreeze · Apr 8, 2015

Yuu · Apr 8, 2015

Thanks Z, love the look as i said before

.

Going to post a few results for comparison. Will edit my post later around 1-2am.

Zertop's "Is it my Line" Results
Date/Time: Wed Apr 08 17:05:19 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 15ms.
Your maximum ping was 50ms.

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:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms 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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=50ms 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 = 9ms, Maximum = 50ms, Average = 15ms

Edit@0145am: As promised when i have seen it really bad

Zertop's "Is it my Line" Results
Date/Time: Thu Apr 09 01:44:55 CAT 2015

Basic Report:

Your packet loss was 43%.
Your average ping was 1233ms.
Your maximum ping was 3897ms.

You have serious packet loss. Please post these results to the forum for advice.

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=1171ms TTL=63
Reply from 155.239.255.250: bytes=32 time=276ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2230ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3280ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2043ms TTL=63
Reply from 155.239.255.250: bytes=32 time=139ms TTL=63
Reply from 155.239.255.250: bytes=32 time=134ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3897ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=1427ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2246ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=332ms TTL=63
Reply from 155.239.255.250: bytes=32 time=184ms TTL=63
Reply from 155.239.255.250: bytes=32 time=993ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1152ms TTL=63
Reply from 155.239.255.250: bytes=32 time=400ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=1049ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 17, Lost = 13 (43% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 3897ms, Average = 1233ms

Youtube almost always faileds to buffer, mybb frontpage loads first 1/4 and other issues arise. Rebooted router [once in awhile i can get to sites fine but doesn't always work].

Heres another so above isn't seen as a one-off thing.

Zertop's "Is it my Line" Results
Date/Time: Thu Apr 09 01:50:45 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 486ms.
Your maximum ping was 1533ms.

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:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=1003ms TTL=63
Reply from 155.239.255.250: bytes=32 time=298ms TTL=63
Reply from 155.239.255.250: bytes=32 time=365ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1533ms TTL=63
Reply from 155.239.255.250: bytes=32 time=487ms TTL=63
Reply from 155.239.255.250: bytes=32 time=921ms TTL=63
Reply from 155.239.255.250: bytes=32 time=669ms TTL=63
Reply from 155.239.255.250: bytes=32 time=956ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1026ms TTL=63
Reply from 155.239.255.250: bytes=32 time=376ms TTL=63
Reply from 155.239.255.250: bytes=32 time=117ms TTL=63
Reply from 155.239.255.250: bytes=32 time=497ms TTL=63
Reply from 155.239.255.250: bytes=32 time=418ms TTL=63
Reply from 155.239.255.250: bytes=32 time=112ms TTL=63
Reply from 155.239.255.250: bytes=32 time=646ms TTL=63
Reply from 155.239.255.250: bytes=32 time=425ms TTL=63
Reply from 155.239.255.250: bytes=32 time=181ms TTL=63
Reply from 155.239.255.250: bytes=32 time=224ms TTL=63
Reply from 155.239.255.250: bytes=32 time=407ms TTL=63
Reply from 155.239.255.250: bytes=32 time=291ms TTL=63
Reply from 155.239.255.250: bytes=32 time=324ms TTL=63
Reply from 155.239.255.250: bytes=32 time=292ms TTL=63
Reply from 155.239.255.250: bytes=32 time=298ms TTL=63
Reply from 155.239.255.250: bytes=32 time=296ms TTL=63
Reply from 155.239.255.250: bytes=32 time=306ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=306ms TTL=63
Reply from 155.239.255.250: bytes=32 time=307ms TTL=63
Reply from 155.239.255.250: bytes=32 time=447ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1037ms 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 = 1533ms, Average = 486ms

I have surfed the net at these hours over the last few years and never came across issues such as these and rightly so as things have changed

. X fingers that we have a switchover happening ^_^

Heres the last one for the night.

Zertop's "Is it my Line" Results
Date/Time: Thu Apr 09 01:56:29 CAT 2015

Basic Report:

Your packet loss was 20%.
Your average ping was 912ms.
Your maximum ping was 3369ms.

You seem to have some packet loss. This indicates an issue on the line.

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=1880ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3369ms TTL=63
Reply from 155.239.255.250: bytes=32 time=728ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1646ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1154ms TTL=63
Reply from 155.239.255.250: bytes=32 time=937ms TTL=63
Reply from 155.239.255.250: bytes=32 time=397ms TTL=63
Reply from 155.239.255.250: bytes=32 time=297ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=442ms TTL=63
Reply from 155.239.255.250: bytes=32 time=571ms TTL=63
Reply from 155.239.255.250: bytes=32 time=374ms TTL=63
Reply from 155.239.255.250: bytes=32 time=238ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2469ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1702ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=1891ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=126ms TTL=63
Reply from 155.239.255.250: bytes=32 time=603ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1677ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=159ms TTL=63
Reply from 155.239.255.250: bytes=32 time=416ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=716ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 3369ms, Average = 912ms

This is looking alright so lets see as it is upgrade exchange week for many [nobody publicly has a list

] so lets hope i can post something better as the week comes to a close.

Line Speed: - 10Mbps
How far are you from the exchange? Just under 2.5KM [line length makes it so]
ISP - Telkom Internet 50GB Capped
Why am I using this tool? Exchange is extremely congested between roughly 12am - 7am and surfing / gaming is near impossible. Hoping to see these results get better hence this awesome tool.

Zertop · Apr 8, 2015

electrofreeze said:
no

Try double finger tap and press open with Java Runtime.

Z

Zertop · Apr 8, 2015

Yuu said:
Thanks Z, love the look as i said before .

Going to post a few results for comparison. Will edit my post later around 1-2am.

Zertop's "Is it my Line" Results
Date/Time: Wed Apr 08 17:05:19 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 15ms.
Your maximum ping was 50ms.

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:

Pinging 155.239.255.250 with 32 bytes of data: Reply from 155.239.255.250: bytes=32 time=11ms TTL=63 Reply from 155.239.255.250: bytes=32 time=16ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=33ms TTL=63 Reply from 155.239.255.250: bytes=32 time=35ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=16ms TTL=63 Reply from 155.239.255.250: bytes=32 time=10ms 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=12ms TTL=63 Reply from 155.239.255.250: bytes=32 time=14ms TTL=63 Reply from 155.239.255.250: bytes=32 time=10ms TTL=63 Reply from 155.239.255.250: bytes=32 time=11ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms TTL=63 Reply from 155.239.255.250: bytes=32 time=9ms 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=12ms TTL=63 Reply from 155.239.255.250: bytes=32 time=13ms TTL=63 Reply from 155.239.255.250: bytes=32 time=10ms TTL=63 Reply from 155.239.255.250: bytes=32 time=20ms TTL=63 Reply from 155.239.255.250: bytes=32 time=16ms TTL=63 Reply from 155.239.255.250: bytes=32 time=11ms TTL=63 Reply from 155.239.255.250: bytes=32 time=17ms TTL=63 Reply from 155.239.255.250: bytes=32 time=15ms TTL=63 Reply from 155.239.255.250: bytes=32 time=10ms TTL=63 Reply from 155.239.255.250: bytes=32 time=10ms TTL=63 Reply from 155.239.255.250: bytes=32 time=50ms 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 = 9ms, Maximum = 50ms, Average = 15ms

This is looking alright so lets see as it is upgrade exchange week for many [nobody publicly has a list ] so lets hope i can post something better as the week comes to a close.

Line Speed: - 10Mbps
How far are you from the exchange? Just under 2.5KM [line length makes it so]
ISP - Telkom Internet 50GB Capped
Why am I using this tool? Exchange is extremely congested between roughly 12am - 7am and surfing / gaming is near impossible. Hoping to see these results get better hence this awesome tool.

Doesn't look too bad!

Z

atomcrusher · Apr 8, 2015

Cool Tool Zertop ..

Zertop's "Is it my Line" Results
Date/Time: Wed Apr 08 17:19:59 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 11ms.
Your maximum ping was 12ms.

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=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms 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 = 10ms, Maximum = 12ms, Average = 11ms

electrofreeze · Apr 8, 2015

Zertop said:
Try double finger tap and press open with Java Runtime.

Z

got it working but cant view the text file only the bottom option works

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Expert Member

Crystal Web representative

Expert Member

Crystal Web representative

Expert Member

Crystal Web representative

Expert Member

Executive Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Executive Member

Expert Member

Expert Member

Expert Member

Expert Member