"Is it my Line" Report Tool

TiCKoMasta said:
I'm trying to see if I can connect to the router via the Internet, but it's a bit of a grey area for me, can't seem to find any resources relating my router.

I don't think I'll be able to change anything on it before 16:40-17:00 that's about the earliest I can get back home. Bit far from work to drive in on lunch time.

I think I'll quickly give Telkom a call tomorrow during lunch and if they don't help I'll email through at lunch time and setup the router for Tuesday morning for the tech guys from your side to run some diagnostics? :)
Click to expand...

Use www.teamviewer.com to remote with. Setup unattended access at home and choose a familiar password, install at work and use your home ID and password to connect.
 
You could always TeamView into a connected PC and connect that way, but this all requires a working connection. Haha. Email if you need. Happy to try help...
 
Ok will try that. :)
Downloading TV now, will see if I can remote in tomorrow and then send through an email.
Else I'll try give Telkom a call, maybe it's a quite day at their offices and someone answers with a "Goeie more, hoe mag ek u help vandag". :D
 
Used the tool and tested Afrihost Capped account:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 8ms
Your maximum ping was 10ms

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.236.13.65 with 32 bytes of data:
Request timed out.
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=10ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Request timed out.
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=7ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254

Ping statistics for 105.236.13.65:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 10ms, Average = 8ms

2014/05/26 9:54:26.47

And then OW uncapped Account:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 75ms
Your maximum ping was 81ms

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 (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice

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

Pinging 196.215.214.1 with 32 bytes of data:
Reply from 196.215.214.1: bytes=32 time=75ms TTL=254
Reply from 196.215.214.1: bytes=32 time=77ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=73ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=79ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=79ms TTL=254
Reply from 196.215.214.1: bytes=32 time=69ms TTL=254
Reply from 196.215.214.1: bytes=32 time=69ms TTL=254
Reply from 196.215.214.1: bytes=32 time=74ms TTL=254
Reply from 196.215.214.1: bytes=32 time=76ms TTL=254
Reply from 196.215.214.1: bytes=32 time=77ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=68ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=76ms TTL=254
Reply from 196.215.214.1: bytes=32 time=76ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=72ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=79ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=70ms TTL=254
Reply from 196.215.214.1: bytes=32 time=63ms TTL=254
Reply from 196.215.214.1: bytes=32 time=70ms TTL=254
Reply from 196.215.214.1: bytes=32 time=81ms TTL=254

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

2014/05/26 9:51:33.81

If this test to just before ISP, why the different results?
 
TiCKoMasta said:
Ok will try that. :)
Downloading TV now, will see if I can remote in tomorrow and then send through an email.
Else I'll try give Telkom a call, maybe it's a quite day at their offices and someone answers with a "Goeie more, hoe mag ek u help vandag". :D
Click to expand...

so we got to the bottom of this issue. Telkom have disabled certain packet relays on this specific exchange, perhaps to hide the fact that there's significant exchange congestion. No issues on his end at all...
 
diephoenix08 said:
Used the tool and tested Afrihost Capped account:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 8ms
Your maximum ping was 10ms

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.236.13.65 with 32 bytes of data:
Request timed out.
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=10ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Request timed out.
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=7ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=8ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254
Reply from 105.236.13.65: bytes=32 time=9ms TTL=254

Ping statistics for 105.236.13.65:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 10ms, Average = 8ms

2014/05/26 9:54:26.47

And then OW uncapped Account:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 75ms
Your maximum ping was 81ms

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 (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice

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

Pinging 196.215.214.1 with 32 bytes of data:
Reply from 196.215.214.1: bytes=32 time=75ms TTL=254
Reply from 196.215.214.1: bytes=32 time=77ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=73ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=79ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=79ms TTL=254
Reply from 196.215.214.1: bytes=32 time=69ms TTL=254
Reply from 196.215.214.1: bytes=32 time=69ms TTL=254
Reply from 196.215.214.1: bytes=32 time=74ms TTL=254
Reply from 196.215.214.1: bytes=32 time=76ms TTL=254
Reply from 196.215.214.1: bytes=32 time=77ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=68ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=76ms TTL=254
Reply from 196.215.214.1: bytes=32 time=76ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=80ms TTL=254
Reply from 196.215.214.1: bytes=32 time=72ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=79ms TTL=254
Reply from 196.215.214.1: bytes=32 time=78ms TTL=254
Reply from 196.215.214.1: bytes=32 time=70ms TTL=254
Reply from 196.215.214.1: bytes=32 time=63ms TTL=254
Reply from 196.215.214.1: bytes=32 time=70ms TTL=254
Reply from 196.215.214.1: bytes=32 time=81ms TTL=254

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

2014/05/26 9:51:33.81

If this test to just before ISP, why the different results?
Click to expand...

You're connecting directly, aren't you?

Z
 
Thanks to Zertop for this tool.

I hope someone can help met with my adsl speed issue.

I have ran a tracert and zertop's tool and noticed very high latency. As one can see, problems start at hop 2. What does hop 2 on this tracert mean?

Your help will be appreciated.


C:\>tracert www.google.co.za

Tracing route to www.google.co.za [74.125.233.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 407 ms 405 ms 408 ms dsl-197-245-35-1.voxdsl.co.za [197.245.35.1]
3 397 ms 416 ms 439 ms 196.41.29.166
4 412 ms 382 ms 322 ms 196.41.29.233
5 328 ms 342 ms 381 ms 41.193.119.6
6 436 ms 428 ms 440 ms google.jb1.napafrica.net [196.46.25.166]
7 301 ms 308 ms 308 ms 64.233.174.21
8 336 ms 341 ms 344 ms jnb01s01-in-f23.1e100.net [74.125.233.55]

Trace complete.

Herewith Zertop's tool results:

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 351ms
Your maximum ping was 495ms

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
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)


Pinging 197.245.35.1 with 32 bytes of data:



Reply from 197.245.35.1: bytes=32 time=417ms TTL=254

Reply from 197.245.35.1: bytes=32 time=343ms TTL=254

Reply from 197.245.35.1: bytes=32 time=370ms TTL=254

Reply from 197.245.35.1: bytes=32 time=358ms TTL=254

Reply from 197.245.35.1: bytes=32 time=415ms TTL=254

Reply from 197.245.35.1: bytes=32 time=339ms TTL=254

Reply from 197.245.35.1: bytes=32 time=276ms TTL=254

Reply from 197.245.35.1: bytes=32 time=221ms TTL=254

Reply from 197.245.35.1: bytes=32 time=245ms TTL=254

Reply from 197.245.35.1: bytes=32 time=287ms TTL=254

Reply from 197.245.35.1: bytes=32 time=290ms TTL=254

Reply from 197.245.35.1: bytes=32 time=376ms TTL=254

Reply from 197.245.35.1: bytes=32 time=372ms TTL=254

Reply from 197.245.35.1: bytes=32 time=370ms TTL=254

Reply from 197.245.35.1: bytes=32 time=334ms TTL=254

Reply from 197.245.35.1: bytes=32 time=329ms TTL=254

Reply from 197.245.35.1: bytes=32 time=387ms TTL=254

Reply from 197.245.35.1: bytes=32 time=373ms TTL=254

Reply from 197.245.35.1: bytes=32 time=364ms TTL=254

Reply from 197.245.35.1: bytes=32 time=328ms TTL=254

Reply from 197.245.35.1: bytes=32 time=235ms TTL=254

Reply from 197.245.35.1: bytes=32 time=339ms TTL=254

Reply from 197.245.35.1: bytes=32 time=420ms TTL=254

Reply from 197.245.35.1: bytes=32 time=493ms TTL=254

Reply from 197.245.35.1: bytes=32 time=495ms TTL=254

Reply from 197.245.35.1: bytes=32 time=360ms TTL=254

Reply from 197.245.35.1: bytes=32 time=327ms TTL=254

Reply from 197.245.35.1: bytes=32 time=342ms TTL=254

Reply from 197.245.35.1: bytes=32 time=384ms TTL=254

Reply from 197.245.35.1: bytes=32 time=348ms TTL=254



Ping statistics for 197.245.35.1:

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

Approximate round trip times in milli-seconds:

Minimum = 221ms, Maximum = 495ms, Average = 351ms
 
Zertop said:
You're connecting directly, aren't you?

Z
Click to expand...

Connecting with cable to router on gig network.

both connections have to go thru same exchange, only difference is where they are going to. Funny results, i would assume both connections would have same results, and if their is problem between me and provider both connections will show it.
 
diephoenix08 said:
Connecting with cable to router on gig network.

both connections have to go thru same exchange, only difference is where they are going to. Funny results, i would assume both connections would have same results, and if their is problem between me and provider both connections will show it.
Click to expand...

While they both go to the same exchange, they will each go to a different card at the exchange (or just before the IPC).

I don't see why there should be different results though.

I will definitely research into it!

Z
 
@DJ... Earlier in this thread I posted about the tool closing on me with no result and I finally worked out why ;).


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

Your average ping was 12ms
Your maximum ping was 25ms

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: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 196.210.132.1 with 32 bytes of data:
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=13ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=25ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=13ms TTL=254
Reply from 196.210.132.1: bytes=32 time=13ms TTL=254
Reply from 196.210.132.1: bytes=32 time=11ms TTL=254
Reply from 196.210.132.1: bytes=32 time=11ms TTL=254
Reply from 196.210.132.1: bytes=32 time=11ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254
Reply from 196.210.132.1: bytes=32 time=13ms TTL=254
Reply from 196.210.132.1: bytes=32 time=11ms TTL=254
Reply from 196.210.132.1: bytes=32 time=11ms TTL=254
Reply from 196.210.132.1: bytes=32 time=11ms TTL=254
Reply from 196.210.132.1: bytes=32 time=11ms TTL=254
Reply from 196.210.132.1: bytes=32 time=12ms TTL=254

Ping statistics for 196.210.132.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 25ms, Average = 12ms
 
2014-06-01  9:26:17,09

Thats from my OpenWeb account and the next one is from my CrystalWeb account:

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

2014-06-01 9:34:49,43

Your average ping was =ms
Your maximum ping was =ms
Click to expand...

Any ideas? Both results were run one after the other starting with OpenWeb.
 
We are pinging 196.210.132.1 just fine which is an Internet Solutions box. We don't run on the IS backbone with these new accounts so this could explain why you're not seeing return packets from this box on our new Crystal Clear Uncapped products.

Anakha, out of curiosity what DNS settings are you using?
 
Last edited:
When did you guys get a Rep? And you have a 121 posts. I must browse new posts more often :p. I wonder if there is a CrystalWeb support thread as well...
/goes off to find it...

To answer your question, according to my router my DNS is:

196.41.124.10
196.41.124.11
Click to expand...

Even if I change to my Netflix DNS I still cannot run the tool with the CW credentials...
 
Are you sure you're pinging the correct address? The box you're pinging is an Internet Solutions box, which shouldn't be the second hop on your route, although I'm not really familiar with this tool (yet).

zertop, going to send you a PM shortly...
 

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

Your average ping was 27ms
Your maximum ping was 218ms

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 serious intermittent fault on the line. This could be a cause of an issue. 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.224.72.1 with 32 bytes of data:
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=103ms TTL=254
Reply from 105.224.72.1: bytes=32 time=218ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=26ms TTL=254
Reply from 105.224.72.1: bytes=32 time=18ms TTL=254
Reply from 105.224.72.1: bytes=32 time=36ms TTL=254
Reply from 105.224.72.1: bytes=32 time=18ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=19ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=22ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254
Reply from 105.224.72.1: bytes=32 time=16ms TTL=254
Reply from 105.224.72.1: bytes=32 time=18ms TTL=254
Reply from 105.224.72.1: bytes=32 time=17ms TTL=254

Ping statistics for 105.224.72.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 218ms, Average = 27ms
 
2014-06-01 10:11:53,73
 
Zertop said:
Please would you do a traceroute for me to google.co.za :)

Z
Click to expand...

Tracing route to www.google.co.za [74.125.233.63]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 15 ms 13 ms 12 ms 105.233.4.1
3 22 ms 22 ms 22 ms telkom-gw-ipc-up.jhbcore.net [196.6.121.198]
4 32 ms 34 ms 35 ms 72.14.220.38
5 56 ms 51 ms 80 ms 64.233.174.21
6 24 ms 24 ms 23 ms jnb01s01-in-f31.1e100.net [74.125.233.63]

Trace complete.
Click to expand...

Hope it helps. :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X