Afrihost Business Uncapped Feedback

Status
Not open for further replies.
ENOUGH NOW, step away from the keyboard, you are disrupting this thread. Stop posting on this thread since you aren't a AH member.


Go find another ISP.

This a open forum, I am allowed to express my views.
 
Last edited:
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 42ms
Your maximum ping was 410ms

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=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=295ms TTL=254
Reply from 105.236.4.129: bytes=32 time=39ms TTL=254
Reply from 105.236.4.129: bytes=32 time=196ms TTL=254
Reply from 105.236.4.129: bytes=32 time=410ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=11ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=17ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=17ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=11ms TTL=254
Reply from 105.236.4.129: bytes=32 time=11ms TTL=254
Reply from 105.236.4.129: bytes=32 time=19ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=16ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=11ms 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 = 11ms, Maximum = 410ms, Average = 42ms

09-Apr-14 13:40:52.34
 
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 42ms
Your maximum ping was 410ms

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=295ms TTL=254
Reply from 105.236.4.129: bytes=32 time=39ms TTL=254
Reply from 105.236.4.129: bytes=32 time=196ms TTL=254
Reply from 105.236.4.129: bytes=32 time=410ms 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 = 11ms, Maximum = 410ms, Average = 42ms

09-Apr-14 13:40:52.34

Worrying,

Looks like an intermittant line issue :( This should not, however, affect your line speed thaat much.

How does the account perform on other accounts?

Z
 
Ok managed to find the issue....i hard coded the dns to 8.8.8.8
but now i remember the other issue....sometimes my line dies and it seems that the DNS assigned is dead...
once i change to google i can work again.... :(
 
after changing DNS to auto assign....

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

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.236.4.129 with 32 bytes of data:
Reply from 105.236.4.129: bytes=32 time=15ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=163ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=146ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=37ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=46ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=42ms TTL=254
Reply from 105.236.4.129: bytes=32 time=11ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=15ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms 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 = 11ms, Maximum = 163ms, Average = 24ms

09-Apr-14 14:23:07.27
 
after changing DNS to auto assign....

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

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.236.4.129 with 32 bytes of data:
Reply from 105.236.4.129: bytes=32 time=15ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=163ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=146ms TTL=254
Reply from 105.236.4.129: bytes=32 time=14ms TTL=254
Reply from 105.236.4.129: bytes=32 time=37ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=46ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=42ms TTL=254
Reply from 105.236.4.129: bytes=32 time=11ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=15ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=12ms TTL=254
Reply from 105.236.4.129: bytes=32 time=13ms 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 = 11ms, Maximum = 163ms, Average = 24ms

09-Apr-14 14:23:07.27

Still some high pings :/

Uhmm.... are you having any speed issues?

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

Pinging 105.236.13.129 with 32 bytes of data:
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=159ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254

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

2014/04/09 15:16:53.23

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 home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 9 ms 7 ms 8 ms 41.181.201.94
4 8 ms 7 ms 7 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 18 ms 18 ms 19 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 9 ms 8 ms 196.44.31.106
7 9 ms 9 ms 13 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 10 ms 9 ms 10 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 15 ms 15 ms 16 ms 197-84-7-1.cpt.mweb.co.za [197.84.7.1]
10 10 ms 9 ms 9 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
11 10 ms 10 ms 10 ms 196.28.178.66
12 11 ms 10 ms 9 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 10 ms 10 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 10 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 15 ms 13 ms 13 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 home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 8 ms 8 ms 41.181.51.182
4 8 ms 7 ms 8 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 15 ms 14 ms 14 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 12 ms 12 ms 13 ms 196.44.31.106
7 152 ms 152 ms 198 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 151 ms 152 ms 151 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 152 ms 152 ms 151 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 156 ms 155 ms 152 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 153 ms 151 ms 151 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 22 seconds. (904.11 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 27 seconds. (583.41 KB/s)




Test End Timestamp
2014/04/09 15:19:08.41


I do seem to get very choppy and stuttering speed tests.... maybe I need to log a call with Telkom AGAIN? :(
 
Also the news servers are creeping....and that is local...10KB/s....dying over here...but that is prob shaping....
I will see after the 10th....otherwise I'm going capped...90 + 90
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X