Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
The quality of the capped accounts have gone down significantly lately.

Higher latency, packet loss (both local and international).

I hope this is just a transition from MTN buying afrihost and that it improves very very soon, because like it is now I cannot use it.

MTN buying their stake in AH has got nothing to do with the degradation of service.

I just got sick and tired of the litany of problems that has crept into AH's service since they moved onto the MTN backbone. Right now I've had to switch onto another provider because AH has gone tits up again, performance is totally erratic, latency is all over the place and I'm just fed up.

I'm taking my business elsewhere as from the end of this month
 
Reason for asking (I see you are Newton Park btw), this is my trace from Lorraine (Charlo exchange)

EDIT: Afriman is aware and I understand MTN are looking into it..

Tracing route to cms-gm.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [10.0.0.2]
2 * * * Request timed out.
3 39 ms 39 ms 39 ms 41.181.178.42
4 39 ms 40 ms 39 ms ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178.41]
5 39 ms 39 ms 38 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
6 39 ms 39 ms 99 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
7 52 ms 41 ms 42 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
8 42 ms 40 ms 51 ms 196.44.31.99
9 38 ms 37 ms 38 ms 196.31.220.8
10 48 ms 47 ms 47 ms 196.31.220.25
11 40 ms 40 ms 40 ms 196.31.63.206
12 45 ms 45 ms 46 ms 196.30.42.133
13 47 ms 48 ms 48 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Funny that 2nd hop hey?

Definitely something wrong there. I see another post mentions the same. Have sent through all the info to MTN to check why the routing is not as it should be :(
 
The quality of the capped accounts have gone down significantly lately.

Higher latency, packet loss (both local and international).

I hope this is just a transition from MTN buying afrihost and that it improves very very soon, because like it is now I cannot use it.

Performance should be improving already in the North now that we've had an upgrade, and we expect the South will receive one very soon. This should definitely improve the overall experience for clients in the region.

I think if we work together we can also make the most of the resources we have by scheduling bog downloads (especially torrents and other P2P) overnight, so that we make use of the downtime on the network during that period. This will also help us motivate for future capacity upgrades.
 
Definitely something wrong there. I see another post mentions the same. Have sent through all the info to MTN to check why the routing is not as it should be :(

Thanks.
it is really sad that I went up from 2mb line to 4mb line and did not really see an increase in speed? Please keep us informed.
I see when I do a speed test I get a couple of servers. Cape town, George, Maseru, not sure what does it mean.
 
Hi Guys in PE, I'm on the Charlo exchange and my speeds have been lousy for two days. I have had my port reset by Telkom but it's still lousy at 10:15 tonight.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Gareth>tracert www.afrihost.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 788 ms 903 ms 965 ms 41.181.221.249
4 1035 ms 1038 ms 1126 ms 41.181.221.250
5 700 ms 745 ms 836 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 973 ms 1021 ms 932 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
7 883 ms 921 ms 988 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
8 908 ms 784 ms 786 ms 196.44.31.99
9 1182 ms 852 ms 943 ms 196.30.1.39
10 871 ms 846 ms 914 ms 196.31.220.21
11 997 ms 1098 ms 880 ms 196.31.63.202
12 977 ms 949 ms 1028 ms 196.30.42.133
13 889 ms 665 ms 788 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\Gareth>

Saw similar things with roadcat and another poster. I'm going to update my query with MTN with these results so we can see what's going on :(
 


Both looking pretty bleak there. Latency looks OK, but it's best to run some full testing before we eliminate anything. From what I can see on the reports, we shouldn't have been contending, so this is pretty unusual. I was getting full throughput last night, and I didn't see general complaints from the North :(

Please PM me so I can get some more troubleshooting going.
 
Thanks.
it is really sad that I went up from 2mb line to 4mb line and did not really see an increase in speed? Please keep us informed.
I see when I do a speed test I get a couple of servers. Cape town, George, Maseru, not sure what does it mean.

Speedtest automatically chooses the server it thinks is closest. If it doesn't know your IP range, it can choose something a little weird.

You can always use speedtest.afrihost.com (which runs off our Gallo Manor DC).
 
<1mbps throughput on the 10meg capped line this morning. Been noticing packet loss and strong jitter issues lately.
 
I'm also on the Charlo Exchange but routing properly.


1 <1 ms <1 ms <1 ms home.gateway.pace.net [10.0.0.2]
2 7 ms 7 ms 7 ms 105-236-10-65-esr-lo.mtnbusiness.co.za [105.236.
10.65]
3 33 ms 31 ms 32 ms 41.181.221.254
4 25 ms 73 ms 25 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 27 ms 25 ms 25 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 26 ms 26 ms 26 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 53 ms 54 ms 53 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

8 44 ms 51 ms 51 ms 196.44.31.97
9 51 ms 51 ms 53 ms 196.30.1.53
10 53 ms 53 ms 53 ms 196.31.220.25
11 51 ms 51 ms 51 ms 196.31.63.206
12 54 ms 53 ms 53 ms 196.30.42.133
13 53 ms 53 ms 53 ms cms-gm.afrihost.com [197.242.144.102]
 
I'm also on the Charlo Exchange but routing properly.


1 <1 ms <1 ms <1 ms home.gateway.pace.net [10.0.0.2]
2 7 ms 7 ms 7 ms 105-236-10-65-esr-lo.mtnbusiness.co.za [105.236.
10.65]
3 33 ms 31 ms 32 ms 41.181.221.254
4 25 ms 73 ms 25 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 27 ms 25 ms 25 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 26 ms 26 ms 26 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 53 ms 54 ms 53 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

8 44 ms 51 ms 51 ms 196.44.31.97
9 51 ms 51 ms 53 ms 196.30.1.53
10 53 ms 53 ms 53 ms 196.31.220.25
11 51 ms 51 ms 51 ms 196.31.63.206
12 54 ms 53 ms 53 ms 196.30.42.133
13 53 ms 53 ms 53 ms cms-gm.afrihost.com [197.242.144.102]
I'm located in Broadwood and only 750 m from the DSLAM outside Builders Warehouse. Could it be my line?
 
I'm located in Broadwood and only 750 m from the DSLAM outside Builders Warehouse. Could it be my line?

No, I have the same thing. I am not at home, but after seeing Masik3R's post I did a reverse trace to my line and it goes via Cape Town, so maybe something has changed. Waiting for my wife to get home in 25 minutes and will remote and test.
 
Afrihost support blamed "server congestion" On my speed issues, but the problem is that all my speeds were really crap.
They even dropped my line down to 8Mb (grrr, it's a mission to get it back up to 10).
But all in all no problem solving was done. Only blame shifting :(
 
Both looking pretty bleak there. Latency looks OK, but it's best to run some full testing before we eliminate anything. From what I can see on the reports, we shouldn't have been contending, so this is pretty unusual. I was getting full throughput last night, and I didn't see general complaints from the North :(

Please PM me so I can get some more troubleshooting going.

Here is my tracert to Afrihost run at 1_43 today.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\tracert www.afrihost.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * 545 ms 607 ms 41.181.221.249
4 823 ms 770 ms * 41.181.221.250
5 838 ms 839 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 613 ms 623 ms 730 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
7 726 ms 667 ms 662 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
8 444 ms 428 ms 387 ms 196.44.31.99
9 867 ms 893 ms * 196.30.1.39
10 55 ms 53 ms 52 ms 196.31.220.21
11 714 ms 818 ms 834 ms 196.31.63.202
12 * 513 ms 516 ms 196.30.42.133
13 836 ms 886 ms 838 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\
 
Here is my tracert to Afrihost run at 1_43 today.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\tracert www.afrihost.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.

Hmmm, Charlo has two DSL segments (041367x and 041368x). I am guessing you are also 368 as I am. Masik3R must be 041367x
 
Last edited:
Here is my tracert to Afrihost run at 1_43 today.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\tracert www.afrihost.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * 545 ms 607 ms 41.181.221.249
4 823 ms 770 ms * 41.181.221.250
5 838 ms 839 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 613 ms 623 ms 730 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
7 726 ms 667 ms 662 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
8 444 ms 428 ms 387 ms 196.44.31.99
9 867 ms 893 ms * 196.30.1.39
10 55 ms 53 ms 52 ms 196.31.220.21
11 714 ms 818 ms 834 ms 196.31.63.202
12 * 513 ms 516 ms 196.30.42.133
13 836 ms 886 ms 838 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\

We're chatting to MTN about this, should have some feedback here soon :(
 
Afrihost support blamed "server congestion" On my speed issues, but the problem is that all my speeds were really crap.
They even dropped my line down to 8Mb (grrr, it's a mission to get it back up to 10).
But all in all no problem solving was done. Only blame shifting :(

I haven't been dealing with this, but I'd like to check up to see what's happening here.
Is there a ref# I can follow up on?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X