"Is it my Line" Report Tool

mugikhan · Apr 13, 2014

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

Your average ping was 104ms
Your maximum ping was 654ms

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.2.65 with 32 bytes of data:
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=18ms TTL=254
Reply from 105.236.2.65: bytes=32 time=181ms TTL=254
Reply from 105.236.2.65: bytes=32 time=49ms TTL=254
Reply from 105.236.2.65: bytes=32 time=19ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=60ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=18ms TTL=254
Reply from 105.236.2.65: bytes=32 time=48ms TTL=254
Reply from 105.236.2.65: bytes=32 time=66ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=19ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=18ms TTL=254
Reply from 105.236.2.65: bytes=32 time=93ms TTL=254
Reply from 105.236.2.65: bytes=32 time=501ms TTL=254
Reply from 105.236.2.65: bytes=32 time=654ms TTL=254
Reply from 105.236.2.65: bytes=32 time=518ms TTL=254
Reply from 105.236.2.65: bytes=32 time=616ms TTL=254

Ping statistics for 105.236.2.65:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 654ms, Average = 104ms
 
2014-04-13 14:05:41,39

I don't know what to do about this I am experiencing very intermittent connectivity and when it does work it is very slow and Telkom hasn't sent out a technician for over a week now.

Zertop · Apr 13, 2014

mugikhan said:

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

Your average ping was 104ms
Your maximum ping was 654ms

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.2.65 with 32 bytes of data:
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=18ms TTL=254
Reply from 105.236.2.65: bytes=32 time=181ms TTL=254
Reply from 105.236.2.65: bytes=32 time=49ms TTL=254
Reply from 105.236.2.65: bytes=32 time=19ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=60ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=18ms TTL=254
Reply from 105.236.2.65: bytes=32 time=48ms TTL=254
Reply from 105.236.2.65: bytes=32 time=66ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=19ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=16ms TTL=254
Reply from 105.236.2.65: bytes=32 time=17ms TTL=254
Reply from 105.236.2.65: bytes=32 time=18ms TTL=254
Reply from 105.236.2.65: bytes=32 time=93ms TTL=254
Reply from 105.236.2.65: bytes=32 time=501ms TTL=254
Reply from 105.236.2.65: bytes=32 time=654ms TTL=254
Reply from 105.236.2.65: bytes=32 time=518ms TTL=254
Reply from 105.236.2.65: bytes=32 time=616ms TTL=254

Ping statistics for 105.236.2.65:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 654ms, Average = 104ms
 
2014-04-13 14:05:41,39

I don't know what to do about this I am experiencing very intermittent connectivity and when it does work it is very slow and Telkom hasn't sent out a technician for over a week now.

Looks bad :/

Unfortunately, this seems like exchange issues

How does the line perform when you use accounts from other ISP's? You can sign up for a trial from WebAfrica/Axxess/Afrihost

Z

mugikhan · Apr 13, 2014

I will try my webafrica account now and report back...

Zertop · Apr 13, 2014

mugikhan said:
I will try my webafrica account now and report back...

Okay great!

Yuu · Apr 14, 2014

Thanks Zertop, just what i needed to help diagnose a friend's line that has been giving issues at late evenings.

My results

Code:

Zertop's "Is it my Line" Results 
Basic Report: 
Your average ping was 13ms 
Your maximum ping was 24ms 
 
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 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.224.16.1 with 32 bytes of data:
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=17ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=11ms TTL=254
Reply from 105.224.16.1: bytes=32 time=15ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=24ms TTL=254
Reply from 105.224.16.1: bytes=32 time=15ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=15ms TTL=254

Ping statistics for 105.224.16.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 24ms, Average = 13ms
 
14-Apr-14  8:09:15.23

Zertop · Apr 14, 2014

Yuu said:

Thanks Zertop, just what i needed to help diagnose a friend's line that has been giving issues at late evenings.

My results

Code:

Zertop's "Is it my Line" Results 
Basic Report: 
Your average ping was 13ms 
Your maximum ping was 24ms 
 
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 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.224.16.1 with 32 bytes of data:
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=17ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=11ms TTL=254
Reply from 105.224.16.1: bytes=32 time=15ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=13ms TTL=254
Reply from 105.224.16.1: bytes=32 time=12ms TTL=254
Reply from 105.224.16.1: bytes=32 time=24ms TTL=254
Reply from 105.224.16.1: bytes=32 time=15ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=14ms TTL=254
Reply from 105.224.16.1: bytes=32 time=15ms TTL=254

Ping statistics for 105.224.16.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 24ms, Average = 13ms
 
14-Apr-14  8:09:15.23

Looking perfect to me? What have the issues been? If it's late evening, I would need the results from when the line was performing badly

It could be exchange issues, but it could also be the ISP (Afrihost are having a few issues right now, but it shouldn't affect users late at night).

Z

Yuu · Apr 14, 2014

No, that is my line, just posting for reference

. Still got to get my friend to send me his results so will post later on. Sorry for the confusion

Zertop · Apr 14, 2014

Yuu said:
No, that is my line, just posting for reference . Still got to get my friend to send me his results so will post later on. Sorry for the confusion

Haha, Well you've got good line performance then

Nice

genetic · Apr 14, 2014

Downloaded and bookmarked this thread. Thanks Zertop.

Zertop · Apr 14, 2014

genetic said:
Downloaded and bookmarked this thread. Thanks Zertop.

Thanks for the support!

Z

mugikhan · Apr 14, 2014

Still a similar problem with my webafrica acount.

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

Your average ping was 162ms
Your maximum ping was 360ms

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.2.65 with 32 bytes of data:
Reply from 105.236.2.65: bytes=32 time=226ms TTL=254
Reply from 105.236.2.65: bytes=32 time=298ms TTL=254
Reply from 105.236.2.65: bytes=32 time=55ms TTL=254
Reply from 105.236.2.65: bytes=32 time=53ms TTL=254
Reply from 105.236.2.65: bytes=32 time=159ms TTL=254
Reply from 105.236.2.65: bytes=32 time=262ms TTL=254
Reply from 105.236.2.65: bytes=32 time=126ms TTL=254
Reply from 105.236.2.65: bytes=32 time=191ms TTL=254
Reply from 105.236.2.65: bytes=32 time=171ms TTL=254
Reply from 105.236.2.65: bytes=32 time=159ms TTL=254
Reply from 105.236.2.65: bytes=32 time=226ms TTL=254
Reply from 105.236.2.65: bytes=32 time=200ms TTL=254
Reply from 105.236.2.65: bytes=32 time=89ms TTL=254
Reply from 105.236.2.65: bytes=32 time=86ms TTL=254
Reply from 105.236.2.65: bytes=32 time=172ms TTL=254
Reply from 105.236.2.65: bytes=32 time=142ms TTL=254
Reply from 105.236.2.65: bytes=32 time=218ms TTL=254
Reply from 105.236.2.65: bytes=32 time=246ms TTL=254
Reply from 105.236.2.65: bytes=32 time=137ms TTL=254
Reply from 105.236.2.65: bytes=32 time=161ms TTL=254
Reply from 105.236.2.65: bytes=32 time=187ms TTL=254
Reply from 105.236.2.65: bytes=32 time=154ms TTL=254
Reply from 105.236.2.65: bytes=32 time=211ms TTL=254
Reply from 105.236.2.65: bytes=32 time=360ms TTL=254
Reply from 105.236.2.65: bytes=32 time=194ms TTL=254
Reply from 105.236.2.65: bytes=32 time=76ms TTL=254
Reply from 105.236.2.65: bytes=32 time=132ms TTL=254
Reply from 105.236.2.65: bytes=32 time=11ms TTL=254
Reply from 105.236.2.65: bytes=32 time=12ms TTL=254
Request timed out.

Ping statistics for 105.236.2.65:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 360ms, Average = 162ms
 
2014-04-14 22:03:58,78

Zertop · Apr 14, 2014

mugikhan said:

Still a similar problem with my webafrica acount.

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

Your average ping was 162ms
Your maximum ping was 360ms

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.2.65 with 32 bytes of data:
Reply from 105.236.2.65: bytes=32 time=226ms TTL=254
Reply from 105.236.2.65: bytes=32 time=298ms TTL=254
Reply from 105.236.2.65: bytes=32 time=55ms TTL=254
Reply from 105.236.2.65: bytes=32 time=53ms TTL=254
Reply from 105.236.2.65: bytes=32 time=159ms TTL=254
Reply from 105.236.2.65: bytes=32 time=262ms TTL=254
Reply from 105.236.2.65: bytes=32 time=126ms TTL=254
Reply from 105.236.2.65: bytes=32 time=191ms TTL=254
Reply from 105.236.2.65: bytes=32 time=171ms TTL=254
Reply from 105.236.2.65: bytes=32 time=159ms TTL=254
Reply from 105.236.2.65: bytes=32 time=226ms TTL=254
Reply from 105.236.2.65: bytes=32 time=200ms TTL=254
Reply from 105.236.2.65: bytes=32 time=89ms TTL=254
Reply from 105.236.2.65: bytes=32 time=86ms TTL=254
Reply from 105.236.2.65: bytes=32 time=172ms TTL=254
Reply from 105.236.2.65: bytes=32 time=142ms TTL=254
Reply from 105.236.2.65: bytes=32 time=218ms TTL=254
Reply from 105.236.2.65: bytes=32 time=246ms TTL=254
Reply from 105.236.2.65: bytes=32 time=137ms TTL=254
Reply from 105.236.2.65: bytes=32 time=161ms TTL=254
Reply from 105.236.2.65: bytes=32 time=187ms TTL=254
Reply from 105.236.2.65: bytes=32 time=154ms TTL=254
Reply from 105.236.2.65: bytes=32 time=211ms TTL=254
Reply from 105.236.2.65: bytes=32 time=360ms TTL=254
Reply from 105.236.2.65: bytes=32 time=194ms TTL=254
Reply from 105.236.2.65: bytes=32 time=76ms TTL=254
Reply from 105.236.2.65: bytes=32 time=132ms TTL=254
Reply from 105.236.2.65: bytes=32 time=11ms TTL=254
Reply from 105.236.2.65: bytes=32 time=12ms TTL=254
Request timed out.

Ping statistics for 105.236.2.65:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 360ms, Average = 162ms
 
2014-04-14 22:03:58,78

Yup, definite issue as before

Why don't you try contacting your local telkom shop as opposed to the hotline? They can sometimes speed up the process

Z

Zertop · Apr 14, 2014

zyro said:
Just the usual windows firewall.. tried disabling it but no luck.

.exe doesn't create any text files, but the zipped version does.. although just had what I pasted in my previous message in it.

Maybe my net is on another level of screwed..

Sorry - didn't want to clog up the AH thread

Yea, the timeout is something like an hour so it should work

Thanks, I will look in the app and see if something is broken

EXE would just display the file at the end. The issue you are having is with the tracert and not detecting the IP correctly :/

Please would you do a manual tracert to google.co.za for me

Z

zyro · Apr 14, 2014

Zertop said:
Sorry - didn't want to clog up the AH thread

Yea, the timeout is something like an hour so it should work

Thanks, I will look in the app and see if something is broken EXE would just display the file at the end. The issue you are having is with the tracert and not detecting the IP correctly :/

Please would you do a manual tracert to google.co.za for me

Z

Cool, yeah best to move the discussion here! Tracert is below.

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 900 ms 954 ms 1020 ms 41.181.54.85
4 706 ms 762 ms 782 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

5 1015 ms 1184 ms 1062 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 997 ms 1037 ms 1013 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 1038 ms 1056 ms 860 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 890 ms 939 ms 936 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

9 928 ms 899 ms 920 ms 41.181.139.109
10 657 ms 473 ms 468 ms 72.14.194.74
11 716 ms 871 ms 1001 ms 64.233.174.57
12 1015 ms 875 ms 867 ms jnb01s02-in-f19.1e100.net [74.125.233.83]

Trace complete.

Zertop · Apr 14, 2014

zyro said:
Cool, yeah best to move the discussion here! Tracert is below.

Aha - that's seriously timing out badly, however my tool should be able to bypass that.

I will take a look at the code tomorrow

By the looks of it, there is some serious issue here

How long have you been experiencing slow speeds?

Z

zyro · Apr 14, 2014

Zertop said:
Aha - that's seriously timing out badly, however my tool should be able to bypass that.

I will take a look at the code tomorrow By the looks of it, there is some serious issue here

How long have you been experiencing slow speeds?

Z

Other than the AH southern IPC crap over the last while, first time it's been this bad. It is raining here, although not badly, had worse and it was fine.

Zertop · Apr 14, 2014

zyro said:
Other than the AH southern IPC crap over the last while, first time it's been this bad. It is raining here, although not badly, had worse and it was fine.

Hmm... Strange...

Maybe it's temporary, give it a night

Z

zyro · Apr 14, 2014

Zertop said:
Hmm... Strange...

Maybe it's temporary, give it a night

Z

Yeah, hopefully comes right.. At the very least, you'll have a more solid app out of this

Zertop · Apr 15, 2014

zyro said:
Yeah, hopefully comes right.. At the very least, you'll have a more solid app out of this

Hahaha, yea - I'll definitely look into it!

Z

Treious · May 8, 2014

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

Join the MyBroadband community

Get started

"Is it my Line" Report Tool

Senior Member

Expert Member

Senior Member

Expert Member

Executive Member

Expert Member

Executive Member

Expert Member

Honorary Master

Expert Member

Senior Member

Expert Member

Expert Member

Active Member

Expert Member

Active Member

Expert Member

Active Member

Expert Member

Member