Afrihost Uncapped ADSL Feedback (Pt2)

Status
Not open for further replies.
For Romark :)

View attachment 99239

Last Result:
Download Speed: 3766 kbps (470.8 KB/sec transfer rate)
Upload Speed: 407 kbps (50.9 KB/sec transfer rate)
Latency: 204 ms
12/2/2014 08:10:55

2495895978.png

Last Result:
Download Speed: 3451 kbps (431.4 KB/sec transfer rate)
Upload Speed: 423 kbps (52.9 KB/sec transfer rate)
Latency: 47 ms
12/2/2014 08:14:44
 
Shamus said:
In the EC and shaped to 25% download - why????
Click to expand...

EC routes through the South IPC and we're seeing increasing demand in that region. Shaping is still effectively maximising throughput and latency, but please do schedule downloads and torrents overnight so that we can minimise daytime shaping as much as possible :(
 
Monthly report:

Happy with Afrihost in all aspects. I would like a t-shirt tho, those red ones are awesome. :)
 
RoMark said:
Well if you look at my post #9853 you will see that my local speed test indicate 2Mbps.


2495263569.png



2495267903.png



Is this normal Afrihost?

I've added a MTR test to afrihost.co.za or do I need to test another location.
Maybe it sheds some info.
Click to expand...

It really depends. Remember that you're also testing off different overseas servers on different networks, so speedtests may vary greatly depending on where you test, or which ISP or server you hit even in the same city.

Try using BitMeter OS to check your actual throughput.

I also find that if there is a small degree of latency or packet loss on local, it gets multiplied ten times or more on international. So local may seem perfect, but international shows more symptoms of line issues. Not saying that is necessarily the case here, but have seen this in the past :(
 
Last edited:
wingnut771 said:
Back in the day when I did have my line with you, out of curiosity, I tried this facility on numerous occasions but never worked, or should I say never finished, longest 3 minutes of my life.

If it did work, then I would see the benefit, but alas, there was none, so moved it back to Telkom when I ditched home uncapped after the MTN move.

While on the subject of diag tools, the network test tool gives me time-outs when there are none, ie; I have a perfect line/exchange and doing the same tests that the tool does, all looks normal, but the tool makes my line look like swiss cheese.

So, nice tool set concept you have but just a big paper weight for me as they don't work.
Click to expand...

Sometimes the exchange returns an error, which kind of breaks the tool. Most of the time it works pretty well.
 
AfriMan said:
It really depends. Remember that you're also testing off different overseas servers on different networks, so speedtests may vary greatly depending on where you test, or which ISP or server you hit even in the same city.

Try using BitMeter OS to check your actual throughput.
Click to expand...

This is why I only use the MyBB servers, keeping things simple.
 
Fudzy said:
You should have left it unbundled and you wouldn't have to battle with constant line issues.
Click to expand...

Nah, definitely prefer to have it with us. I'm on a pretty old exchange my lines are pretty old as well. I have regular date with Telkom every six months or so where they use sellotape and chappies to get everything working a little better, but had a constant crackle on the line for about .... 10 years, I think :(

But my data works great when it works, especially since we moved over to MTN. :)
 
wingnut771 said:
ping -n 100 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=194ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=193ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=202ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 189ms, Maximum = 202ms, Average = 190ms
Click to expand...

Those are quite consistent, however I do usually get 160ms-ish.
 
wingnut771 said:
I should have included Zertop's tool in my previous comment, as that just backs up my theory AH tool is broken.

Case in point:

Zertop:

Local Tracert

Tracing route to google.co.za [173.194.34.119]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.1]
3 22 ms 21 ms 21 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 21 ms 22 ms 21 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 23 ms 22 ms 22 ms core1a-pkl-te-1-1.ip.isnet.net [196.26.0.60]
6 21 ms 21 ms 19 ms 168.209.1.179
7 23 ms 21 ms 21 ms 74.125.49.66
8 187 ms 186 ms 185 ms 66.249.95.8
9 186 ms 186 ms 185 ms 209.85.253.47
10 184 ms 184 ms 184 ms lhr14s20-in-f23.1e100.net [173.194.34.119]

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.1.1
2 8 ms 9 ms 9 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.1]
3 20 ms 24 ms 21 ms 196.38.72.229
4 22 ms 20 ms 19 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 24 ms 24 ms 22 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 189 ms 186 ms 187 ms 168.209.201.93
7 186 ms 184 ms 184 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
8 193 ms 193 ms 192 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
9 190 ms 189 ms 203 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 49 seconds. (412.04 KB/s)

Local Speedtest


Test End Timestamp
2014/02/12 7:59:02.05

AH Test Tool:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=24 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=56 time=24 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=56 time=23 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=56 time=23 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=191 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=190 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=190 ms
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1192.168.1.1 1 ms 1 ms
2196.210.157.1 10 ms 8 ms
3196.38.73.1 57 ms 20 ms
4196.38.73.1 20 ms
168.209.1.1 23 ms
5168.209.1.1 42 ms 20 ms
6168.209.1.1 22 ms
41.208.29.1 22 ms
741.208.29.1 61 ms
196.44.0.2 23 ms
8196.44.0.2 24 ms
196.44.31.9 23 ms
9196.44.31.9 23 ms
196.31.220.6 22 ms
10196.31.220.6 46 ms
196.31.220.2 23 ms
11196.31.63.1 36 ms
197.242.144.1 24 ms
12197.242.144.1 23 ms


traceroute -n 8.8.8.8

1192.168.1.1 1 ms 1 ms
2196.210.157.1 9 ms 9 ms
3196.38.73.1 19 ms 19 ms
4196.38.73.1 19 ms 20 ms
5168.209.1.1 22 ms 21 ms
6168.209.1.1 19 ms 19 ms
774.125.49.6 35 ms
Request timed out *
8Request timed out *


DNS Test:

nslookup www.afrihost.com

Name:www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name:www.google.com
Address: 74.125.132.104
Name:www.google.com
Address: 74.125.132.106
Name:www.google.com
Address: 74.125.132.99
Name:www.google.com
Address: 74.125.132.103
Name:www.google.com
Address: 74.125.132.147
Name:www.google.com
Address: 74.125.132.105


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

Exchange looking solid? What speed should you be getting?
 
Daytime uncapped speeds

Hi.

I'm reviewing my ISP selectirfon, and I was wondering - how is the AfriHost 2mb uncapped DAY time http traffic shaping, on, for example, GMail. Right now, I can't open international sites on my current host, but their support tells me "everything is fine". I work from home from time to time, so while I do understand that on uncapped I will have poor downloads during the day, I was brought under the impression that I'd still be able to do Google searches, access Bitbucket etc., but that's not the case.

Has anyone experienced similar usage on AfriHost, and what is your opinion of day-time internet usage?

Thanks for any feedback.
 
AfriMan said:
It really depends. Remember that you're also testing off different overseas servers on different networks, so speedtests may vary greatly depending on where you test, or which ISP or server you hit even in the same city.

Try using BitMeter OS to check your actual throughput.

I also find that if there is a small degree of latency or packet loss on local, it gets multiplied ten times or more on international. So local may seem perfect, but international shows more symptoms of line issues. Not saying that is necessarily the case here, but have seen this in the past :(
Click to expand...

We are running in circles here.
I've posted several local speedtest that are running sub par 4Mbps speeds and you keep on harping on International speeds.

LOCAL SPEED TEST with uncapped 4Mbps

2495935238.png


LOCAL SPEED TEST WITH CAPPED 4Mbps

2495943170.png


The capped speed test is purely to show that there is not much wrong with my line, but there is clearly an issue with the uncapped account.

I'm in Kirkwood, about 80km from PE, Eastern Cape.
No shaping on my account.

Is it part of the IPC issue or what is going on?

My tracert does not show any problems as far as I can see.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Jupiter>tracert afrihost.co.za

Tracing route to afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.
8.129]
3 33 ms 33 ms 33 ms 41.181.51.182
4 33 ms 33 ms 34 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 34 ms 34 ms 34 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 26 ms 27 ms 27 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 57 ms 57 ms 55 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

8 56 ms 59 ms 50 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
9 48 ms 48 ms 49 ms 196.30.1.53
10 57 ms 56 ms 56 ms tengigabitethernet9-1.gw21.jnb6.za.mtnbusiness.n
et [196.31.220.27]
11 49 ms 49 ms 48 ms tengigabitethernet5-2.hr15.jnb6.za.mtnbusiness.n
et [196.31.63.194]
12 57 ms 59 ms 58 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\Jupiter>
Click to expand...


Router stats;

SNR stats.jpg


I'm busy installing the Bitmeter OS and will see the type of info it yields.

Edit:
Installed BitMeter OS, but the localhost:2605 does not load in my browser. No error message, just a spinning circle.
Win7 x64
Chrome
 
Last edited:
envo said:
That's a lie. It is shaped
Click to expand...
Can someone clarify this please?
I was under the impression that gaming goes through as a real time service?
Afrihost QoS does not refer to gaming as far I could see?

There are two main types of traffic that you can use when connected to the Internet:

Instant, Realtime traffic protocols such as: Web browsing (HTTPS); Live Streaming (YouTube); Secure browsing (HTTPS); VOIP; Email; Terminal services (SSH)
Non-Realtime Downloading protocols such as: HTTP Downloads (downloading a file from your browser), Torrents (BitTorrent), News servers (NNTP)
Click to expand...

Source
 
@Afriman

Quick question Capped account contention ratio?
Which account is immune to P2P downloading.
 
Just saw on the front page of MyBB that Afrihost will be looking at price cuts, is this only for Capped products or on all products/services?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X