Sign up with Google
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Yep. Unfortunately I had to remove the support for the old systems for now :/
I will be adding it back soon. Just don't have a mac to test it on.
Z
-
Ask a question and get free supportUnlock new privileges and see hidden discussionsWin prizes and earn reputation
-
Question of the day ~ How often do you braai?
-
Afristay giveaway.Win a 2-night stay for two people at an establishment of your choice with R1,000 in spending money. Enter here.
"Is it my Line" Report Tool
- Thread starter Zertop
- Start date
Yep. Unfortunately I had to remove the support for the old systems for now :/
I will be adding it back soon. Just don't have a mac to test it on.
Z
Awesome !
Zertop's "Is it my Line" Results
Date/Time: Fri Jun 19 07:20:24 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 9ms.
Your maximum ping was 11ms.
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:
Zertop's "Is it my Line" Results
Date/Time: Fri Jun 19 07:20:24 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 9ms.
Your maximum ping was 11ms.
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 41.133.92.1 with 32 bytes of data:
Reply from 41.133.92.1: bytes=32 time=11ms TTL=254
Reply from 41.133.92.1: bytes=32 time=11ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=11ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=11ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Ping statistics for 41.133.92.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 11ms, Average = 9msZertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Zertop's "Is it my Line" Results
Date/Time: Fri Jun 26 08:08:31 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 10ms.
Your maximum ping was 11ms.
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 41.133.92.1 with 32 bytes of data:
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=11ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=11ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=9ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=10ms TTL=254
Reply from 41.133.92.1: bytes=32 time=11ms TTL=254
Ping statistics for 41.133.92.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 11ms, Average = 10msZertop's "Is it my Line" Results
Date/Time: Sat Jun 27 11:39:07 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 7ms.
Your maximum ping was 29ms.
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:
Date/Time: Sat Jun 27 11:39:07 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 7ms.
Your maximum ping was 29ms.
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:
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
FrostBiteZA
New Member
- Joined
- Jul 14, 2015
- Messages
- 1
Zertop's "Is it my Line" Results
Date/Time: Tue Jul 14 21:46:07 CAT 2015
Basic Report:
Your packet loss was 3%.
Your average ping was 37ms.
Your maximum ping was 69ms.
You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Date/Time: Tue Jul 14 21:46:07 CAT 2015
Basic Report:
Your packet loss was 3%.
Your average ping was 37ms.
Your maximum ping was 69ms.
You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!
Detailed Report:
Code:
Pinging 105.224.88.1 with 32 bytes of data:
Reply from 105.224.88.1: bytes=32 time=45ms TTL=254
Reply from 105.224.88.1: bytes=32 time=31ms TTL=254
Reply from 105.224.88.1: bytes=32 time=37ms TTL=254
Reply from 105.224.88.1: bytes=32 time=51ms TTL=254
Reply from 105.224.88.1: bytes=32 time=36ms TTL=254
Reply from 105.224.88.1: bytes=32 time=36ms TTL=254
Reply from 105.224.88.1: bytes=32 time=38ms TTL=254
Request timed out.
Reply from 105.224.88.1: bytes=32 time=69ms TTL=254
Reply from 105.224.88.1: bytes=32 time=30ms TTL=254
Reply from 105.224.88.1: bytes=32 time=36ms TTL=254
Reply from 105.224.88.1: bytes=32 time=24ms TTL=254
Reply from 105.224.88.1: bytes=32 time=37ms TTL=254
Reply from 105.224.88.1: bytes=32 time=36ms TTL=254
Reply from 105.224.88.1: bytes=32 time=52ms TTL=254
Reply from 105.224.88.1: bytes=32 time=57ms TTL=254
Reply from 105.224.88.1: bytes=32 time=44ms TTL=254
Reply from 105.224.88.1: bytes=32 time=52ms TTL=254
Reply from 105.224.88.1: bytes=32 time=51ms TTL=254
Reply from 105.224.88.1: bytes=32 time=18ms TTL=254
Reply from 105.224.88.1: bytes=32 time=15ms TTL=254
Reply from 105.224.88.1: bytes=32 time=31ms TTL=254
Reply from 105.224.88.1: bytes=32 time=68ms TTL=254
Reply from 105.224.88.1: bytes=32 time=39ms TTL=254
Reply from 105.224.88.1: bytes=32 time=29ms TTL=254
Reply from 105.224.88.1: bytes=32 time=37ms TTL=254
Reply from 105.224.88.1: bytes=32 time=35ms TTL=254
Reply from 105.224.88.1: bytes=32 time=17ms TTL=254
Reply from 105.224.88.1: bytes=32 time=18ms TTL=254
Reply from 105.224.88.1: bytes=32 time=32ms TTL=254
Ping statistics for 105.224.88.1:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 69ms, Average = 37msZertop's "Is it my Line" Results
Date/Time: Wed Jul 15 22:53:04 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 146ms.
Your maximum ping was 291ms.
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:
Date/Time: Wed Jul 15 22:53:04 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 146ms.
Your maximum ping was 291ms.
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 196.210.148.129 with 32 bytes of data:
Reply from 196.210.148.129: bytes=32 time=94ms TTL=254
Reply from 196.210.148.129: bytes=32 time=15ms TTL=254
Reply from 196.210.148.129: bytes=32 time=199ms TTL=254
Reply from 196.210.148.129: bytes=32 time=167ms TTL=254
Reply from 196.210.148.129: bytes=32 time=210ms TTL=254
Reply from 196.210.148.129: bytes=32 time=291ms TTL=254
Reply from 196.210.148.129: bytes=32 time=270ms TTL=254
Reply from 196.210.148.129: bytes=32 time=261ms TTL=254
Reply from 196.210.148.129: bytes=32 time=156ms TTL=254
Reply from 196.210.148.129: bytes=32 time=13ms TTL=254
Reply from 196.210.148.129: bytes=32 time=174ms TTL=254
Reply from 196.210.148.129: bytes=32 time=11ms TTL=254
Reply from 196.210.148.129: bytes=32 time=40ms TTL=254
Reply from 196.210.148.129: bytes=32 time=161ms TTL=254
Reply from 196.210.148.129: bytes=32 time=176ms TTL=254
Reply from 196.210.148.129: bytes=32 time=189ms TTL=254
Reply from 196.210.148.129: bytes=32 time=215ms TTL=254
Reply from 196.210.148.129: bytes=32 time=211ms TTL=254
Reply from 196.210.148.129: bytes=32 time=142ms TTL=254
Reply from 196.210.148.129: bytes=32 time=181ms TTL=254
Reply from 196.210.148.129: bytes=32 time=168ms TTL=254
Reply from 196.210.148.129: bytes=32 time=154ms TTL=254
Reply from 196.210.148.129: bytes=32 time=155ms TTL=254
Reply from 196.210.148.129: bytes=32 time=216ms TTL=254
Reply from 196.210.148.129: bytes=32 time=100ms TTL=254
Reply from 196.210.148.129: bytes=32 time=131ms TTL=254
Reply from 196.210.148.129: bytes=32 time=153ms TTL=254
Reply from 196.210.148.129: bytes=32 time=122ms TTL=254
Reply from 196.210.148.129: bytes=32 time=13ms TTL=254
Reply from 196.210.148.129: bytes=32 time=11ms TTL=254
Ping statistics for 196.210.148.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 291ms, Average = 146msZertop's "Is it my Line" Results
Date/Time: Thu Jul 16 11:20:36 CAT 2015
Basic Report:
Your packet loss was 33%.
Your average ping was 55ms.
Your maximum ping was 300ms.
You have serious packet loss. Please post these results to the forum for advice.
Detailed Report:
Date/Time: Thu Jul 16 11:20:36 CAT 2015
Basic Report:
Your packet loss was 33%.
Your average ping was 55ms.
Your maximum ping was 300ms.
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:
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=100ms TTL=63
Reply from 155.239.255.250: bytes=32 time=300ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 20, Lost = 10 (33% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 300ms, Average = 55msZertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
That packet loss would indicate an issue with the line, rather than with MWEB. Do all your phones/alarms etc have POTS filters on them? Without, that can sometime cause packet loss... surprisingly
Z
It's strange cause the 1st day after loadshedding my line goes completely ape like it does now, then I have too restart the router to be A ok, then 1 hour later it starts again, then I restart router and it's fine :/ So I don't know if perhaps my router has been damaged lately that's causing this?
This is 5 - 10 minutes after I reset my router.
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 13:57:43 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 39ms.
Your maximum ping was 41ms.
Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!
Detailed Report:
This is 5 - 10 minutes after I reset my router.
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 13:57:43 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 39ms.
Your maximum ping was 41ms.
Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, 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=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms TTL=63
Reply from 155.239.255.250: bytes=32 time=39ms 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 = 37ms, Maximum = 41ms, Average = 39ms
Last edited:
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 15:28:59 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
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:
This right only pings 1st hop ?
Not that I am complaining
Date/Time: Thu Jul 16 15:28:59 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
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:
Pinging 169.0.14.1 with 32 bytes of data:
Reply from 169.0.14.1: bytes=32 time=13ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=14ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=16ms TTL=254
Reply from 169.0.14.1: bytes=32 time=13ms TTL=254
Reply from 169.0.14.1: bytes=32 time=15ms TTL=254
Reply from 169.0.14.1: bytes=32 time=14ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=31ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=11ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Reply from 169.0.14.1: bytes=32 time=12ms TTL=254
Ping statistics for 169.0.14.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 31ms, Average = 12msThis right only pings 1st hop ?
Code:
Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 9 ms 14 ms 169-0-14-1-access.afrihost.co.za [169.0.14.1]
3 14 ms 12 ms 13 ms 41.170.79.230
4 12 ms 11 ms 12 ms 41.170.79.236
5 12 ms 13 ms 12 ms google.jb1.napafrica.net [196.46.25.166]
6 12 ms 12 ms 12 ms 72.14.237.239
7 11 ms 12 ms 22 ms jnb01s07-in-f3.1e100.net [216.58.223.3]
Trace complete.Not that I am complaining
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 15:28:59 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 12ms.
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:Pinging 169.0.14.1 with 32 bytes of data: Reply from 169.0.14.1: bytes=32 time=13ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=14ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=16ms TTL=254 Reply from 169.0.14.1: bytes=32 time=13ms TTL=254 Reply from 169.0.14.1: bytes=32 time=15ms TTL=254 Reply from 169.0.14.1: bytes=32 time=14ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=31ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=11ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Reply from 169.0.14.1: bytes=32 time=12ms TTL=254 Ping statistics for 169.0.14.1: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 31ms, Average = 12ms
This right only pings 1st hop ?
Code:Tracing route to www.google.co.za [216.58.223.3] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 9 ms 9 ms 14 ms 169-0-14-1-access.afrihost.co.za [169.0.14.1] 3 14 ms 12 ms 13 ms 41.170.79.230 4 12 ms 11 ms 12 ms 41.170.79.236 5 12 ms 13 ms 12 ms google.jb1.napafrica.net [196.46.25.166] 6 12 ms 12 ms 12 ms 72.14.237.239 7 11 ms 12 ms 22 ms jnb01s07-in-f3.1e100.net [216.58.223.3] Trace complete.
Not that I am complaining
You connected directly to the new Afrihost network, by any chance?
Yup lol using AfriGreen...
Zertop
Expert Member
- Joined
- Mar 9, 2013
- Messages
- 3,105
Yeah. You're obviously using a direct PPPOE connection from the desktop, hence the tool using that as your IP
Z
Interesting results from my normal Afrihost.co.za 1GB DSL Test Acc..
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 22:42:12 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 2ms.
Your maximum ping was 9ms.
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:
Zertop's "Is it my Line" Results
Date/Time: Thu Jul 16 22:42:12 CAT 2015
Basic Report:
Your packet loss was 0%.
Your average ping was 2ms.
Your maximum ping was 9ms.
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 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=2ms TTL=30
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Reply from 192.168.1.1: bytes=32 time=2ms TTL=30
Reply from 192.168.1.1: bytes=32 time=2ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=4ms TTL=30
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Reply from 192.168.1.1: bytes=32 time=2ms TTL=30
Reply from 192.168.1.1: bytes=32 time=6ms TTL=30
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Reply from 192.168.1.1: bytes=32 time=4ms TTL=30
Reply from 192.168.1.1: bytes=32 time=9ms TTL=30
Reply from 192.168.1.1: bytes=32 time=5ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Reply from 192.168.1.1: bytes=32 time=2ms TTL=30
Reply from 192.168.1.1: bytes=32 time=2ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=3ms TTL=30
Reply from 192.168.1.1: bytes=32 time=2ms TTL=30
Reply from 192.168.1.1: bytes=32 time=1ms TTL=30
Ping statistics for 192.168.1.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 9ms, Average = 2ms