Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Dianysis said:
Hi.
I managed to download the Zertop Line Tool.
Here are the results:


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

Your average ping was 28ms
Your maximum ping was 36ms

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.236.9.1 with 32 bytes of data:
Request timed out.
Reply from 105.236.9.1: bytes=32 time=32ms TTL=254
Reply from 105.236.9.1: bytes=32 time=36ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=36ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=32ms TTL=254
Reply from 105.236.9.1: bytes=32 time=35ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=36ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=35ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Request timed out.

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 36ms, Average = 28ms
 
05/11/2014 21:15:14.87

I really appreciate the help.
Click to expand...

You seem to have a bit of packet loss there, and there definitely seems to be a problem with your physical line.
Have you run the test from a WIRED computer, or are these results via WIRELESS?

Also, could you run the other tool and post the results? Would be interesting to see what throughput you're getting and the trace routes.
 
I am using wireless connection at the moment. Should i re-run the tests on wired? On the diagnostics tool, it has said "connection timed out" or "connection unexpectedly closed" a number of times already.
 
Cortexenslaver, below are the results from the diagnostics tool:

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 1 ms 1 ms 11 ms 192.168.0.1
2 19 ms 22 ms 20 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 34 ms 47 ms * ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 39 ms 27 ms 24 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 43 ms * * jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 27 ms 33 ms 79 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 58 ms 152 ms 44 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 31 ms 88 ms 43 ms postfix.wipronet.co.za [196.22.161.133]
9 75 ms 113 ms * tengig-0-7-0-3-vic-p-2.mweb.co.za [197.80.7.98]
10 * * 60 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
11 61 ms 59 ms 50 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
12 71 ms 80 ms 90 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 55 ms 54 ms 46 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
14 49 ms 53 ms 78 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 62 ms 63 ms 52 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 57 ms 49 ms 70 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * 19 ms 20 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 33 ms 56 ms 29 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 51 ms 27 ms 30 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 89 ms 82 ms 51 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 26 ms 40 ms 118 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 224 ms 229 ms 220 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 225 ms 283 ms 256 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 208 ms 225 ms 215 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 268 ms 239 ms 229 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 209 ms 204 ms 203 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 238 ms 247 ms 230 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 212 ms 232 ms 208 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 11:45 seconds. (29.01 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 3:42 seconds. (71.89 KB/s)




Test End Timestamp
05/11/2014 21:35:16.03


The international Speedtest had quite a number of "Connection unexpectedly closed" and "Connection timed out", but nothing in the local Speedtest.

Thanks again.
 
Oh, and Cortexenslave, in case I didn't mention before, I am on a 4mbps business line.
Speeds are horrendous.
 
Dianysis said:
I am using wireless connection at the moment. Should i re-run the tests on wired? On the diagnostics tool, it has said "connection timed out" or "connection unexpectedly closed" a number of times already.
Click to expand...

It's always best to run the tests wired first... that way it's easier to know if the line/connection is at fault, or whether your wireless device/router is at fault ;)
 
Dianysis said:
Cortexenslaver, below are the results from the diagnostics tool:

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 1 ms 1 ms 11 ms 192.168.0.1
2 19 ms 22 ms 20 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 34 ms 47 ms * ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 39 ms 27 ms 24 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 43 ms * * jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 27 ms 33 ms 79 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 58 ms 152 ms 44 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 31 ms 88 ms 43 ms postfix.wipronet.co.za [196.22.161.133]
9 75 ms 113 ms * tengig-0-7-0-3-vic-p-2.mweb.co.za [197.80.7.98]
10 * * 60 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
11 61 ms 59 ms 50 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
12 71 ms 80 ms 90 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 55 ms 54 ms 46 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
14 49 ms 53 ms 78 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 62 ms 63 ms 52 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 57 ms 49 ms 70 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * 19 ms 20 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 33 ms 56 ms 29 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 51 ms 27 ms 30 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 89 ms 82 ms 51 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 26 ms 40 ms 118 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 224 ms 229 ms 220 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 225 ms 283 ms 256 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 208 ms 225 ms 215 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 268 ms 239 ms 229 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 209 ms 204 ms 203 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 238 ms 247 ms 230 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 212 ms 232 ms 208 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 11:45 seconds. (29.01 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 3:42 seconds. (71.89 KB/s)




Test End Timestamp
05/11/2014 21:35:16.03


The international Speedtest had quite a number of "Connection unexpectedly closed" and "Connection timed out", but nothing in the local Speedtest.

Thanks again.
Click to expand...

Those speeds are terrible :(
From the above, it would appear that your connection is suffering at the exchange, and then dies at the IPC.
I think if you can run the tests again via a wired connection, it might give a more accurate indication of where the fault actually is ;)

Your whole traffic route appears very erratic and intermittent. You may have to call Telkom out to have a look at your line... there may some degradation of the copper which they may be able to fix.
 
cortexenslaver said:
Those speeds are terrible :(
From the above, it would appear that your connection is suffering at the exchange, and then dies at the IPC.
I think if you can run the tests again via a wired connection, it might give a more accurate indication of where the fault actually is ;)
Click to expand...

Ok. Will do wired connect now.
Really appreciate the help.
 
cortexenslaver said:
Those speeds are terrible :(
From the above, it would appear that your connection is suffering at the exchange, and then dies at the IPC.
I think if you can run the tests again via a wired connection, it might give a more accurate indication of where the fault actually is ;)

Your whole traffic route appears very erratic and intermittent. You may have to call Telkom out to have a look at your line... there may some degradation of the copper which they may be able to fix.
Click to expand...

I think I will definitely phone Telkom myself, as AH doesn't seem to be doing much to help me.
 
HI Cortexenslaver.

Below are the results of the Line Tool on Wired Connection:


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

Your average ping was 26ms
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.236.9.1 with 32 bytes of data:
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=25ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=25ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=35ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=32ms TTL=254

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 35ms, Average = 26ms
 
05/11/2014 21:53:10.28
 
Dianysis said:
HI Cortexenslaver.

Below are the results of the Line Tool on Wired Connection:


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

Your average ping was 26ms
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.236.9.1 with 32 bytes of data:
Reply from 105.236.9.1: bytes=32 time=22ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=30ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=25ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=25ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=34ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=35ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=32ms TTL=254

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 35ms, Average = 26ms
 
05/11/2014 21:53:10.28
Click to expand...

Those look about the same... I think you should log a fault online with Telkom (faster) - which area are in?

Also, which router are you using?
 
I am in the Vaal Triangle - about 25 km south of Alberton.
And yes, i definitely will be phoning Telkom.
Will post the results from the Diagnostics Tool as soon as it is done.

As for router, I am using a Netgear DGN2200 that I bought directly from AH.
 
Results from Diagnostics Tool on Wired Connection:

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 20 ms 19 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 21 ms 20 ms 20 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 36 ms 36 ms 36 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 23 ms 72 ms 48 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 42 ms 45 ms 84 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 41 ms 42 ms 35 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 24 ms 23 ms 25 ms postfix.wipronet.co.za [196.22.161.133]
9 79 ms * * tengig-0-7-0-3-vic-p-2.mweb.co.za [197.80.7.98]
10 62 ms * * tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
11 72 ms 45 ms 73 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
12 55 ms 63 ms 62 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 51 ms 51 ms 50 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
14 45 ms 53 ms 45 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 57 ms 76 ms * 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 45 ms 68 ms * 41-86-110-143.mweb.co.za [41.86.110.143]
17 44 ms 53 ms 57 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 20 ms 23 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 43 ms 61 ms 21 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 35 ms 24 ms 23 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 34 ms 36 ms 30 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 23 ms 44 ms 22 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 221 ms 218 ms 226 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 247 ms 240 ms 219 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 228 ms 211 ms 234 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 221 ms 233 ms 218 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 211 ms 208 ms 257 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 252 ms 223 ms 224 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 * 214 ms 203 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 6:53 seconds. (49.51 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 1:59 seconds. (134.13 KB/s)




Test End Timestamp
05/11/2014 22:05:55.43
 
Dianysis said:
I am in the Vaal Triangle - about 25 km south of Alberton.
And yes, i definitely will be phoning Telkom.
Will post the results from the Diagnostics Tool as soon as it is done.

As for router, I am using a Netgear DGN2200 that I bought directly from AH.
Click to expand...

The router should be OK, but the only way to know if it is the cause of your discomfort, is to connect a different router and test. When you log the call with Telkom, ask them to bring another router to test with ;)
 
Dianysis said:
Results from Diagnostics Tool on Wired Connection:

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 20 ms 19 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 21 ms 20 ms 20 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 36 ms 36 ms 36 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 23 ms 72 ms 48 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 42 ms 45 ms 84 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 41 ms 42 ms 35 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 24 ms 23 ms 25 ms postfix.wipronet.co.za [196.22.161.133]
9 79 ms * * tengig-0-7-0-3-vic-p-2.mweb.co.za [197.80.7.98]
10 62 ms * * tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
11 72 ms 45 ms 73 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
12 55 ms 63 ms 62 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 51 ms 51 ms 50 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
14 45 ms 53 ms 45 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 57 ms 76 ms * 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 45 ms 68 ms * 41-86-110-143.mweb.co.za [41.86.110.143]
17 44 ms 53 ms 57 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 20 ms 23 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 43 ms 61 ms 21 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 35 ms 24 ms 23 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 34 ms 36 ms 30 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 23 ms 44 ms 22 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 221 ms 218 ms 226 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 247 ms 240 ms 219 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 228 ms 211 ms 234 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 221 ms 233 ms 218 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 211 ms 208 ms 257 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 252 ms 223 ms 224 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 * 214 ms 203 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 6:53 seconds. (49.51 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 1:59 seconds. (134.13 KB/s)




Test End Timestamp
05/11/2014 22:05:55.43
Click to expand...

Speeds are slightly better, but the latency on the various hops seems a bit high and inconsistent. If you test a different router and get the same results, then I would definitely get Telkom to check the copper from your location to the exchange.
 
Ok cool. Thank you. Will try get hold of a router and do the tests again to see. And thanks again for all your help. Feel like i am at least getting somewhere now.
 
One last question- i have a test capped account with AH. Would running the test on that account be able to help?
 
Dianysis said:
One last question- i have a test capped account with AH. Would running the test on that account be able to help?
Click to expand...

If you run the tests again on the test account, and the results are the same, then it's definitely your line.
Why not sign up a free account with another provider and do the tests. If there is a big variance in your results, then, again, there must be something fishy with your line.
 
Line Tool on test account (Wired):

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

Your average ping was 23ms
Your maximum ping was 33ms

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.236.9.1 with 32 bytes of data:
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=27ms TTL=254
Reply from 105.236.9.1: bytes=32 time=31ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=28ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=24ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=29ms TTL=254
Reply from 105.236.9.1: bytes=32 time=33ms TTL=254
Reply from 105.236.9.1: bytes=32 time=23ms TTL=254
Reply from 105.236.9.1: bytes=32 time=21ms TTL=254
Reply from 105.236.9.1: bytes=32 time=26ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254
Reply from 105.236.9.1: bytes=32 time=20ms TTL=254

Ping statistics for 105.236.9.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 33ms, Average = 23ms
 
05/11/2014 22:24:26.72


Diagnostics Tool on test account (Wired):

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 18 ms 18 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 20 ms 20 ms 20 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 32 ms 26 ms 21 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 22 ms 20 ms 20 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 20 ms 20 ms 21 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 45 ms 22 ms 23 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 22 ms 22 ms 22 ms postfix.wipronet.co.za [196.22.161.133]
9 51 ms 51 ms 51 ms tengig-0-7-0-3-vic-p-1.mweb.co.za [197.80.7.1]
10 48 ms 47 ms 47 ms tengig-0-0-0-0-cpt-p-2.mweb.co.za [197.84.4.46]
11 48 ms 47 ms 46 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
12 47 ms 47 ms 47 ms 196.28.178.66
13 47 ms 46 ms 47 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 48 ms 47 ms 46 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 48 ms 48 ms 47 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 51 ms 47 ms 48 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 19 ms 18 ms 19 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 21 ms 21 ms 21 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 23 ms 21 ms 22 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 22 ms 40 ms 22 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 25 ms 21 ms 20 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 225 ms 219 ms 220 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 218 ms 219 ms 218 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 219 ms 218 ms 219 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 305 ms 227 ms 222 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 202 ms 212 ms 216 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 220 ms 220 ms 220 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 203 ms 202 ms 208 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 4:21 seconds. (78.25 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 43 seconds. (364.35 KB/s)




Test End Timestamp
05/11/2014 22:32:33.54


What a difference!!
 
Not only is there a huge difference between capped and business but also international vs national.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X