"Is it my Line" Report Tool

[Crystal Web]

You should be pinging 105.233.4.1 and not 196.210.132.1

Hopefully it's a minor issue...

 

[Anakha56]

Ummm, where do you see that IP? :wtf: And, the follow up question, how will it get fixed? Rebooting the router does not solve anything, so maybe its my account? Would you like me to PM you my username CWR?

 

[Zertop]

Ummm, where do you see that IP? :wtf: And, the follow up question, how will it get fixed? Rebooting the router does not solve anything, so maybe its my account? Would you like me to PM you my username CWR?

I will have to help with this a bit later! My tool is not picking up the correct IP

Z

 

[Anakha56]

Ah, okay. No worries, glad I have helped get this fixed then .

 

[Crystal Web]

Ummm, where do you see that IP? :wtf: And, the follow up question, how will it get fixed? Rebooting the router does not solve anything, so maybe its my account? Would you like me to PM you my username CWR?

It's an issue with Zertop's tool and not our account. Zertop however is fantastic at resolving these sorts of things for users of his tools, and I'm sure he'll fix it for you shortly...

 

[Zertop]

Cool! Found the issue

It seems that your second hop does not resolve.

For example, Mine:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 8 ms 13 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]

Yours:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 15 ms 13 ms 12 ms 105.233.4.1

My tool takes the IP from whatever is in the [ ] brackets, however - seeing that yours doesn't resolve properly - it is unable to get the correct IP :/

I will re-design the process of getting the IP to account for this situation

Z

 

[Zertop]

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

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

Look like you may have a line issue :/

How does the line perform with a different ISP?

Z

 

[Zertop]

Updated

01-06-2014
- Fixed general bug - introduced new method for finding IP address of second hop.

 

[DarthCat]

Look like you may have a line issue :/

How does the line perform with a different ISP?

Z

Only have Telkom as isp. they say line is 2mb but sync at 1mb

 

[Descartian]

Hi Zertop,

On a 4Mps business uncapped package, been having very slow download speeds lately

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

Your average ping was 33ms
Your maximum ping was 42ms

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 105.236.8.1 with 32 bytes of data:
Request timed out.
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=38ms TTL=254
Reply from 105.236.8.1: bytes=32 time=27ms TTL=254
Reply from 105.236.8.1: bytes=32 time=35ms TTL=254
Reply from 105.236.8.1: bytes=32 time=40ms TTL=254
Reply from 105.236.8.1: bytes=32 time=29ms TTL=254
Reply from 105.236.8.1: bytes=32 time=37ms TTL=254
Reply from 105.236.8.1: bytes=32 time=29ms TTL=254
Reply from 105.236.8.1: bytes=32 time=38ms TTL=254
Request timed out.
Reply from 105.236.8.1: bytes=32 time=34ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Reply from 105.236.8.1: bytes=32 time=42ms TTL=254
Reply from 105.236.8.1: bytes=32 time=38ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Request timed out.
Reply from 105.236.8.1: bytes=32 time=42ms TTL=254
Reply from 105.236.8.1: bytes=32 time=30ms TTL=254
Reply from 105.236.8.1: bytes=32 time=42ms TTL=254
Reply from 105.236.8.1: bytes=32 time=31ms TTL=254
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Reply from 105.236.8.1: bytes=32 time=27ms TTL=254
Reply from 105.236.8.1: bytes=32 time=35ms TTL=254
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=41ms TTL=254
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=31ms TTL=254

Ping statistics for 105.236.8.1:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 42ms, Average = 33ms

2014/06/15 16:03:21.92

 

[Zertop]

Hi Zertop,

On a 4Mps business uncapped package, been having very slow download speeds lately

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

Your average ping was 33ms
Your maximum ping was 42ms

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 105.236.8.1 with 32 bytes of data:
Request timed out.
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=38ms TTL=254
Reply from 105.236.8.1: bytes=32 time=27ms TTL=254
Reply from 105.236.8.1: bytes=32 time=35ms TTL=254
Reply from 105.236.8.1: bytes=32 time=40ms TTL=254
Reply from 105.236.8.1: bytes=32 time=29ms TTL=254
Reply from 105.236.8.1: bytes=32 time=37ms TTL=254
Reply from 105.236.8.1: bytes=32 time=29ms TTL=254
Reply from 105.236.8.1: bytes=32 time=38ms TTL=254
Request timed out.
Reply from 105.236.8.1: bytes=32 time=34ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Reply from 105.236.8.1: bytes=32 time=42ms TTL=254
Reply from 105.236.8.1: bytes=32 time=38ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Request timed out.
Reply from 105.236.8.1: bytes=32 time=42ms TTL=254
Reply from 105.236.8.1: bytes=32 time=30ms TTL=254
Reply from 105.236.8.1: bytes=32 time=42ms TTL=254
Reply from 105.236.8.1: bytes=32 time=31ms TTL=254
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Reply from 105.236.8.1: bytes=32 time=33ms TTL=254
Reply from 105.236.8.1: bytes=32 time=27ms TTL=254
Reply from 105.236.8.1: bytes=32 time=35ms TTL=254
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=41ms TTL=254
Reply from 105.236.8.1: bytes=32 time=28ms TTL=254
Reply from 105.236.8.1: bytes=32 time=31ms TTL=254

Ping statistics for 105.236.8.1:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 42ms, Average = 33ms

2014/06/15 16:03:21.92

Hey Man!

Sorry, I've been away. Looks like a line issue to me :/
How does the account perform with a different ISP

Z

 

[TEXTILE GUY]

Hey Man!

Sorry, I've been away. Looks like a line issue to me :/

Hey welcome back ... I commented just last week that you were MIA.

Good to see you back helping folk.

 

[Zertop]

Hey welcome back ... I commented just last week that you were MIA.

Good to see you back helping folk.

Haha, yup. Been extremely busy

But I'm back now

Thanks
Z

 

[Descartian]

Hey Man!

Sorry, I've been away. Looks like a line issue to me :/
How does the account perform with a different ISP

Z

Hi Zertop, my ISP gave me another account on a different backbone to test and the speeds was still slow. I logged a fault with Telkom, waiting from Saturday for a tech to attend...

 

[Zertop]

Hi Zertop, my ISP gave me another account on a different backbone to test and the speeds was still slow. I logged a fault with Telkom, waiting from Saturday for a tech to attend...

Okay I see.

Good Luck! You can also try going to your local Telkom Branch and reporting the issue It usually helps speed up the process

Z

 

[titeroper]

Hmm, what do you make of the high max latency below?
I'm SUPPOSED to be on a 10 meg uncapped home account, but the line only syncs at 2 megs down currently.This on an MSAN capable line.
Been a nightmare trying to get them to up the speed to what I am actually paying for
They say there is an issue and its currently sitting with corrections??? Maybe this below proves something is not quite right...
Its been over a week since I sent the request and I have spent about 3 hours in total over the phone.
Anywhoo, here goes...

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

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

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=2ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=2ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=120ms TTL=63
Reply from 192.168.0.1: bytes=32 time=17ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=2ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63

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

2014-06-16 19:13:13,80

 

[killerbyte]

Your tool shows what has been suspected by AH's Critical Care department... my line is dodgy. Its a nice little tool you have developed.


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

Your average ping was 31ms
Your maximum ping was 40ms

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 105.236.3.129 with 32 bytes of data:
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254
Reply from 105.236.3.129: bytes=32 time=38ms TTL=254
Reply from 105.236.3.129: bytes=32 time=36ms TTL=254
Reply from 105.236.3.129: bytes=32 time=38ms TTL=254
Reply from 105.236.3.129: bytes=32 time=26ms TTL=254
Reply from 105.236.3.129: bytes=32 time=28ms TTL=254
Reply from 105.236.3.129: bytes=32 time=33ms TTL=254
Reply from 105.236.3.129: bytes=32 time=28ms TTL=254
Reply from 105.236.3.129: bytes=32 time=29ms TTL=254
Reply from 105.236.3.129: bytes=32 time=35ms TTL=254
Reply from 105.236.3.129: bytes=32 time=27ms TTL=254
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=23ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=37ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 105.236.3.129: bytes=32 time=33ms TTL=254
Reply from 105.236.3.129: bytes=32 time=34ms TTL=254
Reply from 105.236.3.129: bytes=32 time=24ms TTL=254
Reply from 105.236.3.129: bytes=32 time=30ms TTL=254
Reply from 105.236.3.129: bytes=32 time=26ms TTL=254
Reply from 105.236.3.129: bytes=32 time=26ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=33ms TTL=254
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254
Reply from 105.236.3.129: bytes=32 time=40ms TTL=254
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254

Ping statistics for 105.236.3.129:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 40ms, Average = 31ms
 
2014-06-16 19:28:04,88

 

[Zertop]

Hmm, what do you make of the high max latency below?
I'm SUPPOSED to be on a 10 meg uncapped home account, but the line only syncs at 2 megs down currently.This on an MSAN capable line.
Been a nightmare trying to get them to up the speed to what I am actually paying for
They say there is an issue and its currently sitting with corrections??? Maybe this below proves something is not quite right...
Its been over a week since I sent the request and I have spent about 3 hours in total over the phone.
Anywhoo, here goes...

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

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

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=2ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=2ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=120ms TTL=63
Reply from 192.168.0.1: bytes=32 time=17ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=2ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63

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

2014-06-16 19:13:13,80

Seems to be very intermittent :/ Seems to be a line fault, if your max speed is affected. Could you PM a screenshot of your router stats for me (found on the router status page ). If you need any help finding them, just shout

Please would you also check that all your phones/alarms etc have ADSL Filters on them Those things can cause chaos on any line

Z

 

[Zertop]

Your tool shows what has been suspected by AH's Critical Care department... my line is dodgy. Its a nice little tool you have developed.


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

Your average ping was 31ms
Your maximum ping was 40ms

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 105.236.3.129 with 32 bytes of data:
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254
Reply from 105.236.3.129: bytes=32 time=38ms TTL=254
Reply from 105.236.3.129: bytes=32 time=36ms TTL=254
Reply from 105.236.3.129: bytes=32 time=38ms TTL=254
Reply from 105.236.3.129: bytes=32 time=26ms TTL=254
Reply from 105.236.3.129: bytes=32 time=28ms TTL=254
Reply from 105.236.3.129: bytes=32 time=33ms TTL=254
Reply from 105.236.3.129: bytes=32 time=28ms TTL=254
Reply from 105.236.3.129: bytes=32 time=29ms TTL=254
Reply from 105.236.3.129: bytes=32 time=35ms TTL=254
Reply from 105.236.3.129: bytes=32 time=27ms TTL=254
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=23ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=37ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Request timed out.
Reply from 105.236.3.129: bytes=32 time=33ms TTL=254
Reply from 105.236.3.129: bytes=32 time=34ms TTL=254
Reply from 105.236.3.129: bytes=32 time=24ms TTL=254
Reply from 105.236.3.129: bytes=32 time=30ms TTL=254
Reply from 105.236.3.129: bytes=32 time=26ms TTL=254
Reply from 105.236.3.129: bytes=32 time=26ms TTL=254
Reply from 105.236.3.129: bytes=32 time=25ms TTL=254
Reply from 105.236.3.129: bytes=32 time=33ms TTL=254
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254
Reply from 105.236.3.129: bytes=32 time=40ms TTL=254
Reply from 105.236.3.129: bytes=32 time=39ms TTL=254

Ping statistics for 105.236.3.129:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 40ms, Average = 31ms
 
2014-06-16 19:28:04,88

Seems like it :/

Have you tried running these tests with a different backbone (WebAfrica's free GB for example)

Thanks for the kind comment!
Z

 

[Zertop]

Update 23-06-2014
- Fixed bug with telkom guest account. The program will now work when using the guest account.