Afrihost Uncapped ADSL Feedback (Pt2)

Status
Not open for further replies.
on a 2mb uncapped account with AH , used to get betweeb 1.4 - 1.8mpbs on speedtest now i'm lucky to even get 1mbps on a good day..its usually between 400 - 700kbps ... trouble seems to have started roubd about when telkom started with their line upgrades.

used the afrihost tool now, here the results

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=59 time=87 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=59 time=123 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=59 time=69 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=59 time=115 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=248 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=235 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=248 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=245 ms


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 1 ms 1 ms
2 105.236.8.6 49 ms
41.181.221.2 70 ms
3 41.181.221.2 62 ms
41.181.198.1 59 ms
4 196.44.31.1 64 ms 80 ms
5 196.44.31.6 74 ms 87 ms
6 196.31.220.1 82 ms
196.44.0.2 87 ms
7 196.31.220.2 97 ms 88 ms
8 197.242.144.1 58 ms
196.31.63.1 95 ms


traceroute -n 8.8.8.8

1 10.0.0.2 1 ms 1 ms
2 105.236.8.6 73 ms
41.181.53.1 79 ms
3 41.181.53.1 78 ms
41.181.198.1 64 ms
4 196.44.18.2 41 ms 80 ms
5 41.181.139.1 94 ms
196.44.31.1 69 ms
6 72.14.194.7 84 ms
41.181.139.1 133 ms
7 Request timed out *
72.14.194.7 59 ms
8 66.249.95.8 228 ms
9 Request timed out *
10 8.8.8.8 236 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 173.194.34.180
Name: www.google.com
Address: 173.194.34.177
Name: www.google.com
Address: 173.194.34.179
Name: www.google.com
Address: 173.194.34.178
Name: www.google.com
Address: 173.194.34.176


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

I rest my case, nice idea, but this "tool" is completely useless in achieving it's objective.

Case in point: I have ZERO issues, and yet I get weird pings and timeouts - tracerts that only show 1-2 pings instead of 3 etc.

If I do these tests myself manually, then I get solid pings, no timeouts and tracerts with 3 pings.

I suggest you do the tests manually.
 
on a 2mb uncapped account with AH , used to get betweeb 1.4 - 1.8mpbs on speedtest now i'm lucky to even get 1mbps on a good day..its usually between 400 - 700kbps ... trouble seems to have started roubd about when telkom started with their line upgrades.

used the afrihost tool now, here the results

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=59 time=87 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=59 time=123 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=59 time=69 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=59 time=115 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=248 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=235 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=248 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=245 ms


Trace Test:

traceroute -n 197.242.144.102

110.0.0.2 1 ms 1 ms
2105.236.8.6 49 ms
41.181.221.2 70 ms
341.181.221.2 62 ms
41.181.198.1 59 ms
4196.44.31.1 64 ms 80 ms
5196.44.31.6 74 ms 87 ms
6196.31.220.1 82 ms
196.44.0.2 87 ms
7196.31.220.2 97 ms 88 ms
8197.242.144.1 58 ms
196.31.63.1 95 ms


traceroute -n 8.8.8.8

110.0.0.2 1 ms 1 ms
2105.236.8.6 73 ms
41.181.53.1 79 ms
341.181.53.1 78 ms
41.181.198.1 64 ms
4196.44.18.2 41 ms 80 ms
541.181.139.1 94 ms
196.44.31.1 69 ms
672.14.194.7 84 ms
41.181.139.1 133 ms
7Request timed out *
72.14.194.7 59 ms
866.249.95.8 228 ms
9Request timed out *
108.8.8.8 236 ms


DNS Test:

nslookup www.afrihost.com

Name:www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name:www.google.com
Address: 173.194.34.180
Name:www.google.com
Address: 173.194.34.177
Name:www.google.com
Address: 173.194.34.179
Name:www.google.com
Address: 173.194.34.178
Name:www.google.com
Address: 173.194.34.176


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Looks like a telkom line issue :/ you'll have to report a fault :(
 
Just signed up for 4mbps uncapped from TI previously. The cancellation policy was the deal maker. Here's to a better relationship than the previous one... LOL

Day 1 Not a good start at all. YouTube buffering on 480, BBC Iplayer constant buffering, Netflix getting nothing better than SD. Still have to test p2p, just feeling too disappointed right now :-(
 
Day 1 Not a good start at all. YouTube buffering on 480, BBC Iplayer constant buffering, Netflix getting nothing better than SD. Still have to test p2p, just feeling too disappointed right now :-(

How's the shaping? Also - how much do you use per month?
 
How's the shaping? Also - how much do you use per month?

No shaping according to client zone... I use around 200gb pm, but seeing as this is day one for me on AH, and I can't use streaming I am worried that I made the right call here
 
No shaping according to client zone... I use around 200gb pm, but seeing as this is day one for me on AH, and I can't use streaming I am worried that I made the right call here

Hmm... Strange? How's the speed with your free 1gb capped account?
 
No shaping according to client zone... I use around 200gb pm, but seeing as this is day one for me on AH, and I can't use streaming I am worried that I made the right call here
Same thing happened to me. I keep getting a "We're sorry" from Afrihost, which obviously doesn't help me at all. This happened from day one.

Hmm... Strange? How's the speed with your free 1gb capped account?
In my case, my FNB account works flawlessly for streaming, while the Afrihost uncapped buffers periodically and has terrible quality.
 
Same thing happened to me. I keep getting a "We're sorry" from Afrihost, which obviously doesn't help me at all. This happened from day one.


In my case, my FNB account works flawlessly for streaming, while the Afrihost uncapped buffers periodically and has terrible quality.

My uncapped account work flawlessly!
 
Last edited:
My uncapped account work flawlessly!

You are lucky it seems, this is how mine has looked for 27 days in a row now, 24/7. I have looked 2 o' clock in the morning, the whole of weekends. Whats the point of scheduling downloads at night if its constantly shaped? I'm basically paying R597 for a dial-up connection. Pathetic!

pic.jpg
 
It depend on how you've done it. If you're using a bundle, Uncapped and Capped products are discounted differently, and we charge pro-rata on the individual product value, not the bundle value. So the bundles may be priced the same, but the individual discounts are calculated differently - it's also why you have to unbundle and re-bundle when moving from say Uncapped to Capped or Business.

Ah, I read it wrong then. 150gb capped isn't close to the same price as the uncapped bundle. Damn, guess I'll have to just hope uncapped can get back to what it was.
 
Help Me Please

Popped in to ask AH clients a quick question or few - please help me if you would ....

How's the daytime shaping on AH Gold 4 Mbps, whats the torrent shaping like, and how does streaming work for you.
Last question, hows the tech support in your opinion?

Many thanks for your help. :)
 
Popped in to ask AH clients a quick question or few - please help me if you would ....

How's the daytime shaping on AH Gold 4 Mbps, whats the torrent shaping like, and how does streaming work for you.
Last question, hows the tech support in your opinion?

Many thanks for your help. :)

Shaping currently depends on your region. In the North you will be shaped a lot. At least until they get their extra capacity from Telkom. Remember that shaping is applied dynamically depending on the current strain on the network. For example most Cape Town users never experience shaping. I stream Netflix and hulu without a hitch, though some users complain that shaping affects this so it would depend. Service should be the best compared to other isp's, though I've been with afrihost ever since I got adsl.
 
Shaping currently depends on your region. In the North you will be shaped a lot. At least until they get their extra capacity from Telkom. Remember that shaping is applied dynamically depending on the current strain on the network. For example most Cape Town users never experience shaping. I stream Netflix and hulu without a hitch, though some users complain that shaping affects this so it would depend. Service should be the best compared to other isp's, though I've been with afrihost ever since I got adsl.

Tks

I am in the Durban area.
 
Tks

I am in the Durban area.

Durban has been known to be quite heavily shaped, but not that often. Shaping works on a demand based system, so it really depends how busy the network is.

Afrihost have ordered more capacity, and they are just waiting for it to be processed. So soon enough, shaping should ease up quite a bit :)
 
Hmm... Strange? How's the speed with your free 1gb capped account?

Streaming is flawless on a 4mbps Mweb account, and is totally useless on AH... I am going to ask AH to cancel my account immediately and rather go with Mweb. I joined yesterday so I hope that it's not going to be a problem.
 
Netflix on uncapped is stille extremely slow. I noticed it loading quite quickly for the first 1/4 of the buffer, then crawls to a halt almost where it trickles data in, which explains why it keeps pausing to buffer.

I'm switching to a different ISP since several complaints about this has gone with the answer "nothing has changed", well, obviously something changed in January.

I see that several other ISPs also posted issue relating to streaming which they claim was due to exchange congestion in the recent MyBB article on that subject. It could make a huge difference even if there is light or intermittent congestion.

The problem for us is that if this was a network issue, then all our clients would experience the same symptoms regardless of where they are in the country or exchange backhaul. We're still seeing many clients using Netflix without issues, so there must be other factors contributing to this :(
 
When Afrihost first switched over to mtn, on teamspeak my little country flag was no longer the ZA flag, but some foreign country's flag. Since then the IP location service that teamspeak servers use has been updated. Is it possible that because mtn is an international company, that some ranges of IP's are blocked due to apparent location being outside of South Africa? By now all 105's should be seen as originating from South Africa, unless the location service is out of date, or Sony is blocking the IP's because they thought they are not South African.

We register our IPs with all the major geolocation services, like MaxMind, to ensure that overseas services recognise our IP ranges correctly. However, sometimes these services only update periodically or companies that use their services only download new lists at intervals, so there could be a small period where geolocations are misrepresented until all the info is up to date.

However, the choice to block the IPs would be on the content server side, and is pretty unusual.
 
on a 2mb uncapped account with AH , used to get betweeb 1.4 - 1.8mpbs on speedtest now i'm lucky to even get 1mbps on a good day..its usually between 400 - 700kbps ... trouble seems to have started roubd about when telkom started with their line upgrades.

used the afrihost tool now, here the results

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=59 time=87 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=59 time=123 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=59 time=69 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=59 time=115 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=248 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=235 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=248 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=245 ms


Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 1 ms 1 ms
2 105.236.8.6 49 ms
41.181.221.2 70 ms
3 41.181.221.2 62 ms
41.181.198.1 59 ms
4 196.44.31.1 64 ms 80 ms
5 196.44.31.6 74 ms 87 ms
6 196.31.220.1 82 ms
196.44.0.2 87 ms
7 196.31.220.2 97 ms 88 ms
8 197.242.144.1 58 ms
196.31.63.1 95 ms


traceroute -n 8.8.8.8

1 10.0.0.2 1 ms 1 ms
2 105.236.8.6 73 ms
41.181.53.1 79 ms
3 41.181.53.1 78 ms
41.181.198.1 64 ms
4 196.44.18.2 41 ms 80 ms
5 41.181.139.1 94 ms
196.44.31.1 69 ms
6 72.14.194.7 84 ms
41.181.139.1 133 ms
7 Request timed out *
72.14.194.7 59 ms
8 66.249.95.8 228 ms
9 Request timed out *
10 8.8.8.8 236 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 173.194.34.180
Name: www.google.com
Address: 173.194.34.177
Name: www.google.com
Address: 173.194.34.179
Name: www.google.com
Address: 173.194.34.178
Name: www.google.com
Address: 173.194.34.176


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

There is definitely too much latency on your results. If you posted this in the evening, there should be good latency, even with shaping, so this is pretty unusual. I would suspect line fault or exchange congestion, but we'd need to run further tests to confirm :(
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X