Afrihost Uncapped Latency problems on the new network (MTN)

I had crazy lag on my Fifa games last night, which is mostly played against Europeans. Compared to Monday night when everything was smooth sailing. I hope they get the CT IPC up ASAP.

+1, online gaming has been a no go zone. I'm in JHB btw.
 
Seems the latency issues are sorted out, BUT however there is a speed issue...

tracert here:

Tracing route to www.amazon.co.uk [178.236.6.251]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 105-236-5-129-esr-lo.mtnbusiness.co.za [105.236.5.129]
3 38 ms 30 ms 30 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 42 ms 31 ms 31 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 54 ms 33 ms 35 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 45 ms 30 ms 30 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 242 ms 239 ms 239 ms ct-cr-2.za--ct-cr-1.za.mtnns.net [196.44.31.35]
8 230 ms 222 ms 222 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
9 234 ms 261 ms 410 ms TenGigabitEthernet8-2.ar6.LON3.gblx.net [208.48.238.185]
10 230 ms 229 ms 231 ms ldn-b5-link.telia.net [213.248.81.73]
11 225 ms 243 ms 227 ms ldn-bb2-link.telia.net [80.91.247.93]
12 241 ms 235 ms 236 ms dln-b2-link.telia.net [213.155.134.93]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


However when downloading from any site outside of SA then I get nowhere above 200kbps (I have a 10mbps uncapped account and I am in Cape Town)

I did download tests from Australia from a FTP site which has no throttle.

No idea why this is happening... Seems most of their customer base is in JHB and now CPT is feeling what happens when you don't plan properly for the whole network.
 
I am just using @afrigamer, untill they sort out the MTN network, as @afrigamer are still on the IS network and way better latency and speed than what we get now.
 
Well I have just installed an ADSL line in our Ballito Apartment.
I am very satisfied with the service I received from Afrihost. I got my Netgear Wireless modem from then and have started using their prepaid data. We only come down here a few times a year and the prepaid which is usable over a 12 month period is great for my application. (Their Netgear modem is about R400 cheaper than the same item at IC)
Here's my Speedtest results:

http://www.speedtest.net/result/2252750819.png

The latency could be better but not too bad over the distance. ( MTN Business Johannesburg)

So I may switch my 4mb uncapped in Boksburg from Mweb to Afrihost. Their 10mb uncapped is about the same price.
 
I see that Afrihost has removed on their website the issue of latency from Cape Town. Well it is true that is better but still not what we use to get with IS.

A ping to google DNS (8.8.8.8) use to take 180ms on the IS network. After the migration to MTN we were at 300ms. Today we are 230ms. Roughly 50% better, but there is some room for improvement!

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 10.0.0.1 (10.0.0.1) 0.873 ms 0.454 ms 0.480 ms
2 105-236-8-193-esr-lo.mtnbusiness.co.za (105.236.8.193) 6.498 ms 6.900 ms 6.756 ms
3 ipc-recieve-rb-1a.za.mtnbusiness.net (41.181.178.53) 43.441 ms 29.640 ms 29.723 ms
4 rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120) 32.714 ms
rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 76.860 ms 63.129 ms
5 jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 37.711 ms 28.686 ms 27.968 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 53.216 ms 27.896 ms 27.970 ms
7 ct-cr-2.za--ct-cr-1.za-d.mtnns.net (196.44.31.35) 237.097 ms 236.243 ms 271.064 ms
8 ls-pr-1.uk--ls-cr-2.uk-a.mtn.net (209.212.111.201) 219.376 ms 220.772 ms 212.599 ms
9 195.66.224.125 (195.66.224.125) 217.597 ms 215.862 ms 213.847 ms
10 209.85.240.61 (209.85.240.61) 321.774 ms 246.344 ms
209.85.240.63 (209.85.240.63) 228.085 ms
11 209.85.253.90 (209.85.253.90) 221.617 ms
209.85.253.94 (209.85.253.94) 226.896 ms
209.85.253.90 (209.85.253.90) 215.138 ms
12 209.85.243.33 (209.85.243.33) 226.329 ms
209.85.240.28 (209.85.240.28) 228.627 ms 224.307 ms
13 216.239.49.36 (216.239.49.36) 235.131 ms 235.113 ms 231.587 ms
14 * * *
15 google-public-dns-a.google.com (8.8.8.8) 231.823 ms 226.457 ms 229.080 ms
 
What truly gets me, is that we, the consumer, the average man on the street, KNEW this was going to be a big mistake. And yet no one at Afrihost thought that would be the case. Either it's a case of money, or just plain stupidity.
 
I also have Very high latency's since they moved to the peace of crap MTN network..
WTF where they thinking??
 
Very well said, could not have done better myself :p

What truly gets me, is that we, the consumer, the average man on the street, KNEW this was going to be a big mistake. And yet no one at Afrihost thought that would be the case. Either it's a case of money, or just plain stupidity.
 
Guys

We know the latency issue spiked again last night. I was assured that the new QoS and shaping would be implemented, but apparently this was not possible due to various reasons. Gian is personally putting pressure on the various parties to make sure this is done today, and I'm hoping this will be the case. I'm confident this will resolve these issues.

I know we got this one wrong, we need to take the rap for this. We're getting this sorted as high priority. I'll keep everyone informed as this progresses.
 
Fair enough, as long as you are aware of the problem & not asking everyone with a latency issue to send the username & speed test result, & knowing that the issue is not end-user but the link on your side where everything gets screwed up latency wise(trace routes reflecting the issue getting 200+ms ping just between end-user & MTN infrastructure).
The reason why everyone is up in arms is that I am sure that your main client base after hours use Afrihost for gaming & the product just isn't delivering what it's supposed to.
Your service is actually alienating a HUGE portion of our market & what makes it even worse is that we have to stick with this service till the 24th before we can cancel, or incur a double fee if we are looking at signing up with a new ISP.
At the moment the IPC in CPT isn't even an issue as that will not sort out the routing/latency issues MTN side, it doesn't help your stuck in a loop just trying to navigate your own country & then have to exit that merry go round to play international. As that is how it feels at the moment.
To be fair you can't expect the end-user to be happy with this situation, as it is really beyond teething, this is more like a colic baby at the moment.
I am sorry, I am at my wits end now because I am stuck between sticking it out till the end of the month & hoping everything will work as before because your track record was really good (pre-move), but if I can't game for the rest of the month why have internet then?

I know we got this one wrong, we need to take the rap for this.

But who else is to blame? Of course you need to take the rap for this, it goes without saying its your fault. You guys really screwed the pooch on this & I sincerely hope that you can get this sorted so we can have the same experience we had pre-move. In hind sight this move should have been a gradual change over & not a jump into the deep end.
This month is going to break or make you guys as I & a lot of other clients are looking at rather making a move than staying with this.
 
Last edited:
One of my main reasons for cancelling my previous ISP was because I saw the low latencies on Afrihost before the MTN move. I was ready to jump but I will hold off on this for now...even though the latencies of my previous ISP was higher, its still better than the latencies on Afrihost at the moment.

Afrihost has potential, lots of it, but this MTN deal is beginning to look suspect.

Afriman, what exactly was the reason for the move away from IS anyway?
 
I don't know if you guys recall, but latencies and speeds were really awful just before we moved networks. From our perspective, the level of complaints now is nothing compared to what was happening in the last months before the move. In terms of the volume and severity of the problems experienced.

While our original reasons were more related to getting onto a network that we could have more control over, the problems we had in the last 6-8 weeks before the change were truly abysmall for us, and there was very little we could do. Even with what people are describing now, I personally feel it's nowhere near that level, and we as we work with MTN and take more of the reigns of the network - yes, we may make mistakes, but we're becoming a better service provider in the end.
 
That's all great and well, but what about the client on the other end, who is sitting with the worst latency they have experienced over a 2 week period, in 3 years? Who has been told it's probably not going to get any better because its actually within service level, even though it is FAR worse than what he had for the past year? Because I am OVER it. Most other companies would have made a plan, or had a backup plan - in this case I must just deal with it. And that is where the problem lies. I don't care if you want to move networks to bob cotton tooth's cable, but if you do so, and you fail to meet the levels of service you had before, over a period of time, then you need to have a backup plan to provide.

This isn't a matter of having a bad ping for 2 evenings, or 2 days, or even 4 days - its been 2 weeks of abysmal latency. That is worse than it has ever been.
 
I don't know if you guys recall, but latencies and speeds were really awful just before we moved networks. From our perspective, the level of complaints now is nothing compared to what was happening in the last months before the move. In terms of the volume and severity of the problems experienced.

While our original reasons were more related to getting onto a network that we could have more control over, the problems we had in the last 6-8 weeks before the change were truly abysmall for us, and there was very little we could do. Even with what people are describing now, I personally feel it's nowhere near that level, and we as we work with MTN and take more of the reigns of the network - yes, we may make mistakes, but we're becoming a better service provider in the end.

Ok Are so you telling me it is not going to be getting any better and basically telling us to F... ourselves ??

I see a complaint at the consumer commision looming.
 
I don't know if you guys recall, but latencies and speeds were really awful just before we moved networks. From our perspective, the level of complaints now is nothing compared to what was happening in the last months before the move. In terms of the volume and severity of the problems experienced.

While our original reasons were more related to getting onto a network that we could have more control over, the problems we had in the last 6-8 weeks before the change were truly abysmall for us, and there was very little we could do. Even with what people are describing now, I personally feel it's nowhere near that level, and we as we work with MTN and take more of the reigns of the network - yes, we may make mistakes, but we're becoming a better service provider in the end.

WOW afrihost really playing dirty , really dont believe that IS network was bad there are all ways some issues on any given network , some things are all ways out of upsteam providers hands.

IS network rocks love my plugg acc.
 
Received a letter that everything is sorted out, and that the latency of the past few days is something of the past.

I don't think so!

Centurion to Jhb
http://www.speedtest.net/result/2281638802.png

Centurion to CT
http://www.speedtest.net/result/2281647784.png

Centurion to London
http://www.speedtest.net/result/2281651645.png

Centurion to San Fransisco
http://www.speedtest.net/result/2281656776.png

Don't even try and skype, or use Youtube. The buffering is enough to drive anyone insane.

Afrihost better get their act together, or I am going to get another ISP.
At this stage of the game they are absolutely pathetic.
 
Afriman don't talk putty. My service was great and never had any problems while on IS, don't try and make IS sound bad, we all knew MTN was cr@p even before the move.

How is it fair to charge users premium rates to be beta testers for this new useless network?

I don't know if you guys recall, but latencies and speeds were really awful just before we moved networks. From our perspective, the level of complaints now is nothing compared to what was happening in the last months before the move. In terms of the volume and severity of the problems experienced.

While our original reasons were more related to getting onto a network that we could have more control over, the problems we had in the last 6-8 weeks before the change were truly abysmall for us, and there was very little we could do. Even with what people are describing now, I personally feel it's nowhere near that level, and we as we work with MTN and take more of the reigns of the network - yes, we may make mistakes, but we're becoming a better service provider in the end.
 
Afriman don't talk putty. My service was great and never had any problems while on IS, don't try and make IS sound bad, we all knew MTN was cr@p even before the move.

How is it fair to charge users premium rates to be beta testers for this new useless network?

Just stating the facts from my perspective, while you as an individual client may have seen things differently, I deal with several hundreds (thousands) of clients. Similarly, I get a lot of feedback from clients saying they're getting a good stable connection on the network. Not saying there is no problem, but that I have a different perspective.
 
Top
Sign up to the MyBroadband newsletter
X