"Is it my Line" Report Tool

F

Fulton17

Expert Member
Joined
Jul 27, 2005
Messages
1,543

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

Your average ping was 489ms
Your maximum ping was 2043ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

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

Pinging 196.210.109.1 with 32 bytes of data:
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254
Reply from 196.210.109.1: bytes=32 time=9ms TTL=254
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254
Reply from 196.210.109.1: bytes=32 time=10ms TTL=254
Reply from 196.210.109.1: bytes=32 time=15ms TTL=254
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254
Reply from 196.210.109.1: bytes=32 time=9ms TTL=254
Reply from 196.210.109.1: bytes=32 time=323ms TTL=254
Reply from 196.210.109.1: bytes=32 time=429ms TTL=254
Reply from 196.210.109.1: bytes=32 time=739ms TTL=254
Reply from 196.210.109.1: bytes=32 time=741ms TTL=254
Reply from 196.210.109.1: bytes=32 time=749ms TTL=254
Reply from 196.210.109.1: bytes=32 time=2043ms TTL=254
Reply from 196.210.109.1: bytes=32 time=2022ms TTL=254
Reply from 196.210.109.1: bytes=32 time=1998ms TTL=254
Reply from 196.210.109.1: bytes=32 time=25ms TTL=254
Reply from 196.210.109.1: bytes=32 time=10ms TTL=254
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254
Reply from 196.210.109.1: bytes=32 time=639ms TTL=254
Reply from 196.210.109.1: bytes=32 time=731ms TTL=254
Reply from 196.210.109.1: bytes=32 time=722ms TTL=254
Reply from 196.210.109.1: bytes=32 time=766ms TTL=254
Reply from 196.210.109.1: bytes=32 time=2038ms TTL=254
Reply from 196.210.109.1: bytes=32 time=593ms TTL=254
Reply from 196.210.109.1: bytes=32 time=15ms TTL=254
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254
Reply from 196.210.109.1: bytes=32 time=9ms TTL=254
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254
Reply from 196.210.109.1: bytes=32 time=8ms TTL=254

Ping statistics for 196.210.109.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 2043ms, Average = 489ms
 
2014/07/09  9:43:17.57
 
F

Fulton17

Expert Member
Joined
Jul 27, 2005
Messages
1,543
This is with my back up account - way better


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

Your average ping was 20ms
Your maximum ping was 31ms

Looking at your average ping, your line seems to be running perfectly :)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report

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

Pinging 197.245.50.1 with 32 bytes of data:
Reply from 197.245.50.1: bytes=32 time=21ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=21ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=31ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=19ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=20ms TTL=254
Reply from 197.245.50.1: bytes=32 time=21ms TTL=254

Ping statistics for 197.245.50.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 31ms, Average = 20ms
 
2014/07/09 11:39:07.38
 
P

ProfA

Honorary Master
Joined
Jul 15, 2008
Messages
13,408
My internet experience has been horrible for about 1-2 weeks now.

ISP blames Telkom (due to the results of Zertop Line test tool). So logged a fault. They asked me to do a speedtest via speedtest.net.

More or less similar results to this which I just ran now...
23ms response times.

Then I run the zertop line test tool and get these pings....

Code: 
Zertop's "Is it my Line" Results 
Basic Report: 
Your average ping was 147ms 
Your maximum ping was 934ms 
 
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.233.160.1 with 32 bytes of data:
Reply from 105.233.160.1: bytes=32 time=23ms TTL=254
Reply from 105.233.160.1: bytes=32 time=121ms TTL=254
Reply from 105.233.160.1: bytes=32 time=22ms TTL=254
Reply from 105.233.160.1: bytes=32 time=28ms TTL=254
Request timed out.
Reply from 105.233.160.1: bytes=32 time=934ms TTL=254
Reply from 105.233.160.1: bytes=32 time=183ms TTL=254
Reply from 105.233.160.1: bytes=32 time=182ms TTL=254
Reply from 105.233.160.1: bytes=32 time=83ms TTL=254
Reply from 105.233.160.1: bytes=32 time=33ms TTL=254
Reply from 105.233.160.1: bytes=32 time=140ms TTL=254
Reply from 105.233.160.1: bytes=32 time=23ms TTL=254
Reply from 105.233.160.1: bytes=32 time=28ms TTL=254
Reply from 105.233.160.1: bytes=32 time=49ms TTL=254
Reply from 105.233.160.1: bytes=32 time=24ms TTL=254
Reply from 105.233.160.1: bytes=32 time=23ms TTL=254
Reply from 105.233.160.1: bytes=32 time=249ms TTL=254
Reply from 105.233.160.1: bytes=32 time=92ms TTL=254
Request timed out.
Reply from 105.233.160.1: bytes=32 time=24ms TTL=254
Reply from 105.233.160.1: bytes=32 time=20ms TTL=254
Reply from 105.233.160.1: bytes=32 time=30ms TTL=254
Reply from 105.233.160.1: bytes=32 time=29ms TTL=254
Reply from 105.233.160.1: bytes=32 time=330ms TTL=254
Reply from 105.233.160.1: bytes=32 time=70ms TTL=254
Reply from 105.233.160.1: bytes=32 time=124ms TTL=254
Reply from 105.233.160.1: bytes=32 time=344ms TTL=254
Reply from 105.233.160.1: bytes=32 time=629ms TTL=254
Reply from 105.233.160.1: bytes=32 time=267ms TTL=254
Reply from 105.233.160.1: bytes=32 time=38ms TTL=254

Ping statistics for 105.233.160.1:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 934ms, Average = 147ms
 
2014-07-09 21:34:47,41

So what do I tell the Telkom people as they say if Speedtest.net is fine, then they consider everything fine.
 
P

ProfA

Honorary Master
Joined
Jul 15, 2008
Messages
13,408
Switched modem off and on.

Ran Speedtest and Zertop tool again. Very different resuts...



Code: 
Zertop's "Is it my Line" Results 
Basic Report: 
Your average ping was 985ms 
Your maximum ping was 6271ms 
 
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.233.160.1 with 32 bytes of data:
Reply from 105.233.160.1: bytes=32 time=21ms TTL=254
Reply from 105.233.160.1: bytes=32 time=24ms TTL=254
Reply from 105.233.160.1: bytes=32 time=23ms TTL=254
Reply from 105.233.160.1: bytes=32 time=22ms TTL=254
Reply from 105.233.160.1: bytes=32 time=25ms TTL=254
Reply from 105.233.160.1: bytes=32 time=69ms TTL=254
Reply from 105.233.160.1: bytes=32 time=72ms TTL=254
Reply from 105.233.160.1: bytes=32 time=96ms TTL=254
Reply from 105.233.160.1: bytes=32 time=54ms TTL=254
Reply from 105.233.160.1: bytes=32 time=100ms TTL=254
Reply from 105.233.160.1: bytes=32 time=138ms TTL=254
Reply from 105.233.160.1: bytes=32 time=310ms TTL=254
Reply from 105.233.160.1: bytes=32 time=2234ms TTL=254
Reply from 105.233.160.1: bytes=32 time=533ms TTL=254
Reply from 105.233.160.1: bytes=32 time=6271ms TTL=254
Reply from 105.233.160.1: bytes=32 time=3162ms TTL=254
Reply from 105.233.160.1: bytes=32 time=847ms TTL=254
Reply from 105.233.160.1: bytes=32 time=3019ms TTL=254
Reply from 105.233.160.1: bytes=32 time=1217ms TTL=254
Reply from 105.233.160.1: bytes=32 time=2363ms TTL=254
Reply from 105.233.160.1: bytes=32 time=1541ms TTL=254
Reply from 105.233.160.1: bytes=32 time=166ms TTL=254
Reply from 105.233.160.1: bytes=32 time=3048ms TTL=254
Reply from 105.233.160.1: bytes=32 time=1342ms TTL=254
Reply from 105.233.160.1: bytes=32 time=187ms TTL=254
Reply from 105.233.160.1: bytes=32 time=981ms TTL=254
Reply from 105.233.160.1: bytes=32 time=527ms TTL=254
Request timed out.
Reply from 105.233.160.1: bytes=32 time=154ms TTL=254
Reply from 105.233.160.1: bytes=32 time=40ms TTL=254

Ping statistics for 105.233.160.1:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 6271ms, Average = 985ms
 
2014-07-09 21:51:50,79
 
D

Damac10

Senior Member
Joined
Jun 22, 2014
Messages
655
ambroseg1 said:
My internet experience has been horrible for about 1-2 weeks now.

ISP blames Telkom (due to the results of Zertop Line test tool). So logged a fault. They asked me to do a speedtest via speedtest.net.

More or less similar results to this which I just ran now...
23ms response times.

Then I run the zertop line test tool and get these pings....

Code: 
Zertop's "Is it my Line" Results 
Basic Report: 
Your average ping was 147ms 
Your maximum ping was 934ms 
 
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.233.160.1 with 32 bytes of data:
Reply from 105.233.160.1: bytes=32 time=23ms TTL=254
Reply from 105.233.160.1: bytes=32 time=121ms TTL=254
Reply from 105.233.160.1: bytes=32 time=22ms TTL=254
Reply from 105.233.160.1: bytes=32 time=28ms TTL=254
Request timed out.
Reply from 105.233.160.1: bytes=32 time=934ms TTL=254
Reply from 105.233.160.1: bytes=32 time=183ms TTL=254
Reply from 105.233.160.1: bytes=32 time=182ms TTL=254
Reply from 105.233.160.1: bytes=32 time=83ms TTL=254
Reply from 105.233.160.1: bytes=32 time=33ms TTL=254
Reply from 105.233.160.1: bytes=32 time=140ms TTL=254
Reply from 105.233.160.1: bytes=32 time=23ms TTL=254
Reply from 105.233.160.1: bytes=32 time=28ms TTL=254
Reply from 105.233.160.1: bytes=32 time=49ms TTL=254
Reply from 105.233.160.1: bytes=32 time=24ms TTL=254
Reply from 105.233.160.1: bytes=32 time=23ms TTL=254
Reply from 105.233.160.1: bytes=32 time=249ms TTL=254
Reply from 105.233.160.1: bytes=32 time=92ms TTL=254
Request timed out.
Reply from 105.233.160.1: bytes=32 time=24ms TTL=254
Reply from 105.233.160.1: bytes=32 time=20ms TTL=254
Reply from 105.233.160.1: bytes=32 time=30ms TTL=254
Reply from 105.233.160.1: bytes=32 time=29ms TTL=254
Reply from 105.233.160.1: bytes=32 time=330ms TTL=254
Reply from 105.233.160.1: bytes=32 time=70ms TTL=254
Reply from 105.233.160.1: bytes=32 time=124ms TTL=254
Reply from 105.233.160.1: bytes=32 time=344ms TTL=254
Reply from 105.233.160.1: bytes=32 time=629ms TTL=254
Reply from 105.233.160.1: bytes=32 time=267ms TTL=254
Reply from 105.233.160.1: bytes=32 time=38ms TTL=254

Ping statistics for 105.233.160.1:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 934ms, Average = 147ms
 
2014-07-09 21:34:47,41

So what do I tell the Telkom people as they say if Speedtest.net is fine, then they consider everything fine.
Click to expand...

I'm in the same boat...Suddenly nearly two week s ago my 4mb line turned into a 0.1 to 1mb speed line that fluctuates. Reported fault. line stats were Attenuation 50.5 N/R 11 down when sync at 4mb...Speedtest at 3.44mb on average and upload 0.4mb but line was struggling to load webpages and play 240p Youtube.

Thought it might be throttled (although on uncapped 4mb and data usage below 180 gbs at the time )but slow speed continued into new month. After technician visited line attentuation increased to fluctuating 54-58db and line n/r at 6-7 syncing at 1.8 - 2mb... Now theres static on voice calls and speed is still extremely slow. Todays technician blames underground cable. Line not fixed but sms saying service restored received.

Third times a charm...Will log fault again tomorrow....Sometimes Speedtest.net causes more problems than it solves with Telkom....
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Hey Peeps,

Sorry for that - was away. If you still need help, just PM me :p

Z
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Damac10 said:
I'm in the same boat...Suddenly nearly two week s ago my 4mb line turned into a 0.1 to 1mb speed line that fluctuates. Reported fault. line stats were Attenuation 50.5 N/R 11 down when sync at 4mb...Speedtest at 3.44mb on average and upload 0.4mb but line was struggling to load webpages and play 240p Youtube.

Thought it might be throttled (although on uncapped 4mb and data usage below 180 gbs at the time )but slow speed continued into new month. After technician visited line attentuation increased to fluctuating 54-58db and line n/r at 6-7 syncing at 1.8 - 2mb... Now theres static on voice calls and speed is still extremely slow. Todays technician blames underground cable. Line not fixed but sms saying service restored received.

Third times a charm...Will log fault again tomorrow....Sometimes Speedtest.net causes more problems than it solves with Telkom....
Click to expand...

This happens when the speedtest is run in a moment when the line is functioning properly :/ (Deceiving... I know :D )

Is this sorted yet?

Z :)
 
L

Lope

Well-Known Member
Joined
Apr 19, 2007
Messages
478
The problem with a tool like this is threefold
* Telkom does not care. Proving there is a fault does not mean they will fix it.
* We should not have to resort to running tests like this, it is Telkom's responsibility to run tests and make repairs. We do not pay Telkom so that we can do their jobs for them. The joke is I've asked a technician if I can come to the exchange and run a ping test there. He said customers are not allowed there. So even though they're not doing the job they're paid to do, they won't allow us to do their job either.
* Even if we run tests and gather the data, there is no contact address at Telkom to send it to, no way to email a technician etc.
The best I've achieved so far for the last point is showing a technician the results. But he was an old timer and just scratched his head and said "Well... it's on your equipment, so it doesn't count." I said "Can you please get someone with a laptop to come here and run the same test?" He said he would and he would come back. He never returned.

SNR logging software for windows
Previously I made a SNR logging tool on windows and logged the data for 2 months. For lack of anywhere to send it, I uploaded it to dropbox with a sharing link and sent the link in a complaint to telkom. (the only way to send them a text message). There was never any response.

SNR logging software for linux
I've made a new SNR logging script for linux now, that I've been running for a few days. There isn't much point to doing this really, it's just useful to know for yourself what's going on, I guess.
Telkom ADSL 15% Packet Loss for 1.5-2 years, I report the fault every day.

Telkom is too lazy and incompetent or miserly to fix intermittent faults
After two years (coming up shortly) they will have received over R8500, money that is meant to pay for a working service. In that time I've reported the fault probably 70x from the beginning, right through; sometimes daily. I've spoken to supervisors, 2nd level support, etc.
Ultimately they're too incompetent or miserly to run the proper tests, and consider replacing some connections or a piece of wire.

Freedom from Telkom
When is Telkom going to get the boot?
When is a company who's head is not up their backside going to get the opportunity to provide last mile connectivity?
 
Last edited:
P

ProfA

Honorary Master
Joined
Jul 15, 2008
Messages
13,408
Lope said:
The problem with a tool like this is threefold
* Telkom does not care. Proving there is a fault does not mean they will fix it.
* We should not have to resort to running tests like this, it is Telkom's responsibility to run tests and make repairs. We do not pay Telkom so that we can do their jobs for them. The joke is I've asked a technician if I can come to the exchange and run a ping test there. He said customers are not allowed there. So even though they're not doing the job they're paid to do, they won't allow us to do their job either.
* Even if we run tests and gather the data, there is no contact address at Telkom to send it to, no way to email a technician etc.
The best I've achieved so far for the last point is showing a technician the results. But he was an old timer and just scratched his head and said "Well... it's on your equipment, so it doesn't count." I said "Can you please get someone with a laptop to come here and run the same test?" He said he would and he would come back. He never returned.

SNR logging software for windows
Previously I made a SNR logging tool on windows and logged the data for 2 months. For lack of anywhere to send it, I uploaded it to dropbox with a sharing link and sent the link in a complaint to telkom. (the only way to send them a text message). There was never any response.

SNR logging software for linux
I've made a new SNR logging script for linux now, that I've been running for a few days. There isn't much point to doing this really, it's just useful to know for yourself what's going on, I guess.
Telkom ADSL 15% Packet Loss for 1.5-2 years, I report the fault every day.

Telkom is too lazy and incompetent or miserly to fix intermittent faults
After two years (coming up shortly) they will have received over R8500, money that is meant to pay for a working service. In that time I've reported the fault probably 70x from the beginning, right through; sometimes daily. I've spoken to supervisors, 2nd level support, etc.
Ultimately they're too incompetent or miserly to run the proper tests, and consider replacing some connections or a piece of wire.

Freedom from Telkom
When is Telkom going to get the boot?
When is a company who's head is not up their backside going to get the opportunity to provide last mile connectivity?
Click to expand...

Have you resorted to asking the almighty TelkomZA for help? I doubt you will get it now though with the above post LOL.
 
I

iru786

Well-Known Member
Joined
Jan 29, 2012
Messages
127
Hi Guys,
I am on AH uncapped unshapped business account. Have issues with speed consistency so ran the test. Below are the results.

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

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.4.129 with 32 bytes of data:
Reply from 105.236.4.129: bytes=32 time=60ms TTL=254
Reply from 105.236.4.129: bytes=32 time=64ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=83ms TTL=254
Reply from 105.236.4.129: bytes=32 time=99ms TTL=254
Reply from 105.236.4.129: bytes=32 time=220ms TTL=254
Reply from 105.236.4.129: bytes=32 time=107ms TTL=254
Reply from 105.236.4.129: bytes=32 time=50ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=65ms TTL=254
Reply from 105.236.4.129: bytes=32 time=58ms TTL=254
Reply from 105.236.4.129: bytes=32 time=127ms TTL=254
Reply from 105.236.4.129: bytes=32 time=62ms TTL=254
Reply from 105.236.4.129: bytes=32 time=67ms TTL=254
Reply from 105.236.4.129: bytes=32 time=58ms TTL=254
Reply from 105.236.4.129: bytes=32 time=64ms TTL=254
Reply from 105.236.4.129: bytes=32 time=80ms TTL=254
Reply from 105.236.4.129: bytes=32 time=49ms TTL=254
Reply from 105.236.4.129: bytes=32 time=50ms TTL=254
Reply from 105.236.4.129: bytes=32 time=51ms TTL=254
Reply from 105.236.4.129: bytes=32 time=89ms TTL=254
Reply from 105.236.4.129: bytes=32 time=66ms TTL=254
Reply from 105.236.4.129: bytes=32 time=81ms TTL=254
Reply from 105.236.4.129: bytes=32 time=81ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=62ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=48ms TTL=254
Reply from 105.236.4.129: bytes=32 time=51ms TTL=254
Reply from 105.236.4.129: bytes=32 time=65ms TTL=254

Ping statistics for 105.236.4.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 220ms, Average = 74ms

26/07/2014 8:44:41.75
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
iru786 said:
Hi Guys,
I am on AH uncapped unshapped business account. Have issues with speed consistency so ran the test. Below are the results.

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

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.4.129 with 32 bytes of data:
Reply from 105.236.4.129: bytes=32 time=60ms TTL=254
Reply from 105.236.4.129: bytes=32 time=64ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=83ms TTL=254
Reply from 105.236.4.129: bytes=32 time=99ms TTL=254
Reply from 105.236.4.129: bytes=32 time=220ms TTL=254
Reply from 105.236.4.129: bytes=32 time=107ms TTL=254
Reply from 105.236.4.129: bytes=32 time=50ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=65ms TTL=254
Reply from 105.236.4.129: bytes=32 time=58ms TTL=254
Reply from 105.236.4.129: bytes=32 time=127ms TTL=254
Reply from 105.236.4.129: bytes=32 time=62ms TTL=254
Reply from 105.236.4.129: bytes=32 time=67ms TTL=254
Reply from 105.236.4.129: bytes=32 time=58ms TTL=254
Reply from 105.236.4.129: bytes=32 time=64ms TTL=254
Reply from 105.236.4.129: bytes=32 time=80ms TTL=254
Reply from 105.236.4.129: bytes=32 time=49ms TTL=254
Reply from 105.236.4.129: bytes=32 time=50ms TTL=254
Reply from 105.236.4.129: bytes=32 time=51ms TTL=254
Reply from 105.236.4.129: bytes=32 time=89ms TTL=254
Reply from 105.236.4.129: bytes=32 time=66ms TTL=254
Reply from 105.236.4.129: bytes=32 time=81ms TTL=254
Reply from 105.236.4.129: bytes=32 time=81ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=62ms TTL=254
Reply from 105.236.4.129: bytes=32 time=71ms TTL=254
Reply from 105.236.4.129: bytes=32 time=48ms TTL=254
Reply from 105.236.4.129: bytes=32 time=51ms TTL=254
Reply from 105.236.4.129: bytes=32 time=65ms TTL=254

Ping statistics for 105.236.4.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 220ms, Average = 74ms

26/07/2014 8:44:41.75
Click to expand...

Heyo!

Looks pretty bad :/ How does the line perform with another ISP account? You can sign up for a webafrica free capped account :)

Z
 
I

iru786

Well-Known Member
Joined
Jan 29, 2012
Messages
127
Zertop said:
Heyo!

Looks pretty bad :/ How does the line perform with another ISP account? You can sign up for a webafrica free capped account :)

Z
Click to expand...

Just moved to SA and got connected to AH. So wont know about another ISP. But i will signup to free account as you suggested and check.
 
Drifter

Drifter

Honorary Master
Joined
Dec 19, 2012
Messages
22,825
Cant get it to run on Win 7 Ultimate. I downloaded the .EXE version, when I run that, I get press any key, and then the window just shuts down. Cant find a .txt report anywhere.
 
Zertop

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Gerhardva said:
Cant get it to run on Win 7 Ultimate. I downloaded the .EXE version, when I run that, I get press any key, and then the window just shuts down. Cant find a .txt report anywhere.
Click to expand...

Hmm Strange?

The zip version? :)

Z
 
Drifter

Drifter

Honorary Master
Joined
Dec 19, 2012
Messages
22,825
.EXE version

** Edit , just tried the .ZIP and I get

The system cannot find the batch label specified - GOODMAX
 
Last edited:
You must log in or register to reply here.
Top