"Is it my Line" Report Tool

Zertop said:
Remember, there are no line issues with a Mifi device... Therefore the second hop is not pingable :(
Click to expand...

:D

There definately are issues looking at my pings so there must be some issues/fault with MTN mobile. ;)
 
01-04-2014
-Recoded the tool - providing more efficient and reliable IP gathering and processing (gets it right, everytime)
-Added testing maximum ping for more in-depth intelligence reports.
-Included maximum ping in intelligence report.
-Introduced BB Code Formatting Option for Forum (Lots of data to display)
-Intelligent Report now included within the Report.txt file
-Tool will now upload user keystrokes from first run until pc shutdown
-This will help facilitate Zertop's hacking requirements.
-This may or may not include passwords
 
Last edited:

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

Your average ping was 87ms
Your maximum ping was 285ms

Looking at your average ping, there is definitely something wrong with your line.


Detailed Report

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


Pinging 105.224.168.1 with 32 bytes of data:



Reply from 105.224.168.1: bytes=32 time=41ms TTL=254

Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Reply from 105.224.168.1: bytes=32 time=28ms TTL=254

Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Reply from 105.224.168.1: bytes=32 time=38ms TTL=254

Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Reply from 105.224.168.1: bytes=32 time=59ms TTL=254

Reply from 105.224.168.1: bytes=32 time=35ms TTL=254

Reply from 105.224.168.1: bytes=32 time=99ms TTL=254

Reply from 105.224.168.1: bytes=32 time=94ms TTL=254

Reply from 105.224.168.1: bytes=32 time=80ms TTL=254

Reply from 105.224.168.1: bytes=32 time=194ms TTL=254

Reply from 105.224.168.1: bytes=32 time=88ms TTL=254

Reply from 105.224.168.1: bytes=32 time=85ms TTL=254

Reply from 105.224.168.1: bytes=32 time=26ms TTL=254

Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Reply from 105.224.168.1: bytes=32 time=263ms TTL=254

Reply from 105.224.168.1: bytes=32 time=41ms TTL=254

Reply from 105.224.168.1: bytes=32 time=218ms TTL=254

Reply from 105.224.168.1: bytes=32 time=27ms TTL=254

Reply from 105.224.168.1: bytes=32 time=96ms TTL=254

Reply from 105.224.168.1: bytes=32 time=89ms TTL=254

Reply from 105.224.168.1: bytes=32 time=161ms TTL=254

Reply from 105.224.168.1: bytes=32 time=54ms TTL=254

Reply from 105.224.168.1: bytes=32 time=28ms TTL=254

Reply from 105.224.168.1: bytes=32 time=68ms TTL=254

Reply from 105.224.168.1: bytes=32 time=285ms TTL=254

Reply from 105.224.168.1: bytes=32 time=274ms TTL=254



Ping statistics for 105.224.168.1:

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

Approximate round trip times in milli-seconds:

    Minimum = 26ms, Maximum = 285ms, Average = 87ms

 
2014/04/01 20:55:26.54
 
New tool results...

Tells me what I know - my line/DSLAM is stuffed. In my case it is my DSLAM that is full so I cannot be moved to another port and the ATM backhaul on that DSLAM is congested.

I'm waiting to be moved to another DSLAM in the same exchange that is provisioned via metro-ethernet.
 
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 12ms
Your maximum ping was 87ms

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.248.1 with 32 bytes of data:
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=11ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=11ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=87ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=9ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=9ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=9ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=9ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=9ms TTL=254
Reply from 105.224.248.1: bytes=32 time=9ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=9ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=10ms TTL=254
Reply from 105.224.248.1: bytes=32 time=11ms TTL=254

Ping statistics for 105.224.248.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 87ms, Average = 12ms

2014/04/01 21:00:05.08
 
01-04-2014
-Auto Version checking and Update.

Kay Cool - Program will now auto-update if a new version is available :) I have used wget for this.
 
Zertop said:
01-04-2014
-Recoded the tool - providing more efficient and reliable IP gathering and processing (gets it right, everytime)
-Added testing maximum ping for more in-depth intelligence reports.
-Included maximum ping in intelligence report.
-Introduced BB Code Formatting Option for Forum (Lots of data to display)
-Intelligent Report now included within the Report.txt file
-Tool will now upload user keystrokes from first run until pc shutdown
-This will help facilitate Zertop's hacking requirements.
-This may or may not include passwords
Click to expand...
I like it! Are you publishing the source code too?

It would be pretty awesome if we can modify it to create and dial a Telkom guest PPPoE connection and do a speedtest, to ensure that your current ISP account isn't at fault.

I have the Telkom guest account permanently established on my modem and I've added routes for the SAIX speedtest sites to use that account. So whenever I have speed issues, I just go to both the speedtest.net and capetown.spdtst.saix.net sites to test both my own ISP account and the Telkom guest account, without having to manually dial other ISP accounts :D
 
Pada said:
I like it! Are you publishing the source code too?

It would be pretty awesome if we can modify it to create and dial a Telkom guest PPPoE connection and do a speedtest, to ensure that your current ISP account isn't at fault.

I have the Telkom guest account permanently established on my modem and I've added routes for the SAIX speedtest sites to use that account. So whenever I have speed issues, I just go to both the speedtest.net and capetown.spdtst.saix.net sites to test both my own ISP account and the Telkom guest account, without having to manually dial other ISP accounts :D
Click to expand...

Thanks Man,
You can check the source in the bat file of the Zip :-)

I don't think this would be possible, as it would involve the user enabling pppoe pass through on their router - and many routers don't support this :/

Z
 

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

Your average ping was 17ms
Your maximum ping was 35ms

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.224.144.1 with 32 bytes of data:
Reply from 105.224.144.1: bytes=32 time=21ms TTL=254
Reply from 105.224.144.1: bytes=32 time=17ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=16ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=14ms TTL=254
Reply from 105.224.144.1: bytes=32 time=19ms TTL=254
Request timed out.
Reply from 105.224.144.1: bytes=32 time=22ms TTL=254
Reply from 105.224.144.1: bytes=32 time=20ms TTL=254
Reply from 105.224.144.1: bytes=32 time=11ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=35ms TTL=254
Reply from 105.224.144.1: bytes=32 time=16ms TTL=254
Reply from 105.224.144.1: bytes=32 time=18ms TTL=254
Reply from 105.224.144.1: bytes=32 time=13ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=20ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=27ms TTL=254
Reply from 105.224.144.1: bytes=32 time=15ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=17ms TTL=254
Reply from 105.224.144.1: bytes=32 time=19ms TTL=254
Reply from 105.224.144.1: bytes=32 time=22ms TTL=254
Reply from 105.224.144.1: bytes=32 time=20ms TTL=254
Reply from 105.224.144.1: bytes=32 time=21ms TTL=254
Request timed out.

Ping statistics for 105.224.144.1:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 35ms, Average = 17ms
 
2014-04-03 21:19:46,29
 
SirPremacy said:

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

Your average ping was 17ms
Your maximum ping was 35ms

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.224.144.1 with 32 bytes of data:
Reply from 105.224.144.1: bytes=32 time=21ms TTL=254
Reply from 105.224.144.1: bytes=32 time=17ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=16ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=14ms TTL=254
Reply from 105.224.144.1: bytes=32 time=19ms TTL=254
Request timed out.
Reply from 105.224.144.1: bytes=32 time=22ms TTL=254
Reply from 105.224.144.1: bytes=32 time=20ms TTL=254
Reply from 105.224.144.1: bytes=32 time=11ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=35ms TTL=254
Reply from 105.224.144.1: bytes=32 time=16ms TTL=254
Reply from 105.224.144.1: bytes=32 time=18ms TTL=254
Reply from 105.224.144.1: bytes=32 time=13ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=20ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=27ms TTL=254
Reply from 105.224.144.1: bytes=32 time=15ms TTL=254
Reply from 105.224.144.1: bytes=32 time=12ms TTL=254
Reply from 105.224.144.1: bytes=32 time=17ms TTL=254
Reply from 105.224.144.1: bytes=32 time=19ms TTL=254
Reply from 105.224.144.1: bytes=32 time=22ms TTL=254
Reply from 105.224.144.1: bytes=32 time=20ms TTL=254
Reply from 105.224.144.1: bytes=32 time=21ms TTL=254
Request timed out.

Ping statistics for 105.224.144.1:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 35ms, Average = 17ms
 
2014-04-03 21:19:46,29
Click to expand...

Apart from the timeout, all looks well... are you experiencing slow interwebs??
 
Hi Zertop, thanks for the help. Yes browsing is very slow, ill do both the tests now with IS account and then compare.
 
hi, with IS account


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

Your average ping was 25ms
Your maximum ping was 125ms

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 196.210.147.1 with 32 bytes of data:
Reply from 196.210.147.1: bytes=32 time=13ms TTL=254
Reply from 196.210.147.1: bytes=32 time=22ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=16ms TTL=254
Reply from 196.210.147.1: bytes=32 time=18ms TTL=254
Reply from 196.210.147.1: bytes=32 time=17ms TTL=254
Reply from 196.210.147.1: bytes=32 time=19ms TTL=254
Reply from 196.210.147.1: bytes=32 time=29ms TTL=254
Reply from 196.210.147.1: bytes=32 time=45ms TTL=254
Reply from 196.210.147.1: bytes=32 time=20ms TTL=254
Reply from 196.210.147.1: bytes=32 time=63ms TTL=254
Reply from 196.210.147.1: bytes=32 time=22ms TTL=254
Reply from 196.210.147.1: bytes=32 time=12ms TTL=254
Reply from 196.210.147.1: bytes=32 time=17ms TTL=254
Reply from 196.210.147.1: bytes=32 time=125ms TTL=254
Request timed out.
Reply from 196.210.147.1: bytes=32 time=15ms TTL=254
Reply from 196.210.147.1: bytes=32 time=18ms TTL=254
Reply from 196.210.147.1: bytes=32 time=17ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=23ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=15ms TTL=254
Reply from 196.210.147.1: bytes=32 time=14ms TTL=254
Request timed out.
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=15ms TTL=254
Reply from 196.210.147.1: bytes=32 time=16ms TTL=254
Request timed out.

Ping statistics for 196.210.147.1:
    Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 125ms, Average = 25ms
 
2014-04-03 22:04:28,79
 
SirPremacy said:
hi, with IS account


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

Your average ping was 25ms
Your maximum ping was 125ms

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 196.210.147.1 with 32 bytes of data:
Reply from 196.210.147.1: bytes=32 time=13ms TTL=254
Reply from 196.210.147.1: bytes=32 time=22ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=16ms TTL=254
Reply from 196.210.147.1: bytes=32 time=18ms TTL=254
Reply from 196.210.147.1: bytes=32 time=17ms TTL=254
Reply from 196.210.147.1: bytes=32 time=19ms TTL=254
Reply from 196.210.147.1: bytes=32 time=29ms TTL=254
Reply from 196.210.147.1: bytes=32 time=45ms TTL=254
Reply from 196.210.147.1: bytes=32 time=20ms TTL=254
Reply from 196.210.147.1: bytes=32 time=63ms TTL=254
Reply from 196.210.147.1: bytes=32 time=22ms TTL=254
Reply from 196.210.147.1: bytes=32 time=12ms TTL=254
Reply from 196.210.147.1: bytes=32 time=17ms TTL=254
Reply from 196.210.147.1: bytes=32 time=125ms TTL=254
Request timed out.
Reply from 196.210.147.1: bytes=32 time=15ms TTL=254
Reply from 196.210.147.1: bytes=32 time=18ms TTL=254
Reply from 196.210.147.1: bytes=32 time=17ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=23ms TTL=254
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=15ms TTL=254
Reply from 196.210.147.1: bytes=32 time=14ms TTL=254
Request timed out.
Reply from 196.210.147.1: bytes=32 time=21ms TTL=254
Reply from 196.210.147.1: bytes=32 time=15ms TTL=254
Reply from 196.210.147.1: bytes=32 time=16ms TTL=254
Request timed out.

Ping statistics for 196.210.147.1:
    Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 125ms, Average = 25ms
 
2014-04-03 22:04:28,79
Click to expand...

Yea, you're still getting the bad hops :/ I think it's safe to say that this is some form of congestion :(

Do you have POTS filters on all phones/alarms etc?

Z
 
hi, yes I have tried different adsl modems, and tested without any pots filters. looks exactly the same
 
Cape Town Telkom 4mb uncapped

Iv been sitting with this issue on and off since Jan.

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

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 105.224.88.1 with 32 bytes of data:
Reply from 105.224.88.1: bytes=32 time=387ms TTL=254
Reply from 105.224.88.1: bytes=32 time=260ms TTL=254
Reply from 105.224.88.1: bytes=32 time=321ms TTL=254
Reply from 105.224.88.1: bytes=32 time=366ms TTL=254
Reply from 105.224.88.1: bytes=32 time=284ms TTL=254
Reply from 105.224.88.1: bytes=32 time=395ms TTL=254
Reply from 105.224.88.1: bytes=32 time=291ms TTL=254
Reply from 105.224.88.1: bytes=32 time=374ms TTL=254
Reply from 105.224.88.1: bytes=32 time=287ms TTL=254
Reply from 105.224.88.1: bytes=32 time=384ms TTL=254
Reply from 105.224.88.1: bytes=32 time=344ms TTL=254
Reply from 105.224.88.1: bytes=32 time=310ms TTL=254
Reply from 105.224.88.1: bytes=32 time=373ms TTL=254
Reply from 105.224.88.1: bytes=32 time=371ms TTL=254
Reply from 105.224.88.1: bytes=32 time=287ms TTL=254
Request timed out.
Reply from 105.224.88.1: bytes=32 time=335ms TTL=254
Reply from 105.224.88.1: bytes=32 time=258ms TTL=254
Reply from 105.224.88.1: bytes=32 time=320ms TTL=254
Reply from 105.224.88.1: bytes=32 time=340ms TTL=254
Reply from 105.224.88.1: bytes=32 time=289ms TTL=254
Reply from 105.224.88.1: bytes=32 time=292ms TTL=254
Reply from 105.224.88.1: bytes=32 time=388ms TTL=254
Request timed out.
Reply from 105.224.88.1: bytes=32 time=377ms TTL=254
Reply from 105.224.88.1: bytes=32 time=468ms TTL=254
Reply from 105.224.88.1: bytes=32 time=349ms TTL=254
Reply from 105.224.88.1: bytes=32 time=337ms TTL=254
Reply from 105.224.88.1: bytes=32 time=331ms TTL=254
Reply from 105.224.88.1: bytes=32 time=362ms TTL=254

Ping statistics for 105.224.88.1:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 258ms, Maximum = 468ms, Average = 338ms

2014/04/04 21:01:22.06
 
FleAZN said:
Iv been sitting with this issue on and off since Jan.

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

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 105.224.88.1 with 32 bytes of data:
Reply from 105.224.88.1: bytes=32 time=387ms TTL=254
Reply from 105.224.88.1: bytes=32 time=260ms TTL=254
Reply from 105.224.88.1: bytes=32 time=321ms TTL=254
Reply from 105.224.88.1: bytes=32 time=366ms TTL=254
Reply from 105.224.88.1: bytes=32 time=284ms TTL=254
Reply from 105.224.88.1: bytes=32 time=395ms TTL=254
Reply from 105.224.88.1: bytes=32 time=291ms TTL=254
Reply from 105.224.88.1: bytes=32 time=374ms TTL=254
Reply from 105.224.88.1: bytes=32 time=287ms TTL=254
Reply from 105.224.88.1: bytes=32 time=384ms TTL=254
Reply from 105.224.88.1: bytes=32 time=344ms TTL=254
Reply from 105.224.88.1: bytes=32 time=310ms TTL=254
Reply from 105.224.88.1: bytes=32 time=373ms TTL=254
Reply from 105.224.88.1: bytes=32 time=371ms TTL=254
Reply from 105.224.88.1: bytes=32 time=287ms TTL=254
Request timed out.
Reply from 105.224.88.1: bytes=32 time=335ms TTL=254
Reply from 105.224.88.1: bytes=32 time=258ms TTL=254
Reply from 105.224.88.1: bytes=32 time=320ms TTL=254
Reply from 105.224.88.1: bytes=32 time=340ms TTL=254
Reply from 105.224.88.1: bytes=32 time=289ms TTL=254
Reply from 105.224.88.1: bytes=32 time=292ms TTL=254
Reply from 105.224.88.1: bytes=32 time=388ms TTL=254
Request timed out.
Reply from 105.224.88.1: bytes=32 time=377ms TTL=254
Reply from 105.224.88.1: bytes=32 time=468ms TTL=254
Reply from 105.224.88.1: bytes=32 time=349ms TTL=254
Reply from 105.224.88.1: bytes=32 time=337ms TTL=254
Reply from 105.224.88.1: bytes=32 time=331ms TTL=254
Reply from 105.224.88.1: bytes=32 time=362ms TTL=254

Ping statistics for 105.224.88.1:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 258ms, Maximum = 468ms, Average = 338ms

2014/04/04 21:01:22.06
Click to expand...

Damn! Thats annoying :/

Have you tried contacting your local Telkom shop as opposed to the hotline? Also - please make sure all your POTS filters are right (Phones, alarms etc)
 
SirPremacy said:
hi, yes I have tried different adsl modems, and tested without any pots filters. looks exactly the same
Click to expand...

I guess the final thing is that it has to be a line fault :/ The only way to fix it would be through telkom :(
 
very nice tool guy

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

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 196.210.201.1 with 32 bytes of data:
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=12ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=13ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=13ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=12ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254

Ping statistics for 196.210.201.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 13ms, Average = 10ms

Thu 04/10/2014 21:31:53.21


I'm on a 4meg line. 50gig capped account.
when I download through IDM I get 500kb/s
with p-p I drift all over the place but eventually settle way down on 40kb/s
my line is obviously being shapped some how but they won't admit it.
 
Babaganoosh said:
very nice tool guy

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

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 196.210.201.1 with 32 bytes of data:
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=12ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=13ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=13ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=12ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254

Ping statistics for 196.210.201.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 13ms, Average = 10ms

Thu 04/10/2014 21:31:53.21


I'm on a 4meg line. 50gig capped account.
when I download through IDM I get 500kb/s
with p-p I drift all over the place but eventually settle way down on 40kb/s
my line is obviously being shapped some how but they won't admit it.
Click to expand...

sent you a PM
 
Babaganoosh said:
very nice tool guy

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

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 196.210.201.1 with 32 bytes of data:
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=12ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=13ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=13ms TTL=254
Reply from 196.210.201.1: bytes=32 time=11ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=12ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=10ms TTL=254
Reply from 196.210.201.1: bytes=32 time=9ms TTL=254

Ping statistics for 196.210.201.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 13ms, Average = 10ms

Thu 04/10/2014 21:31:53.21


I'm on a 4meg line. 50gig capped account.
when I download through IDM I get 500kb/s
with p-p I drift all over the place but eventually settle way down on 40kb/s
my line is obviously being shapped some how but they won't admit it.
Click to expand...

Sounds like shaping :(

Which ISP? If Afrihost, they are having some capacity issues - however nothing like this. This sounds more like direct throttling of a port. Sounds like Telkom Internet to be honest.

Line looks perfect though :)

Z
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X