Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
So, A dude called Xander at AH reckons


Now Xander is quite a lekker ou. I have dealt with him in the past and I am inclined to give him the benefit of the doubt .... so I checked and got this ...

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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 152 ms 171 ms 116 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.236.1.1]

Telkom
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.1.1
2 11 ms 9 ms 7 ms dsl-165-145-8-01.telkomadsl.co.za [165.145.8.1]

I am NOT the expert here .... there are far smarter fish on these matters .... but something doesnt look good.

I think the thing to remember is that the device on that hop does not belong to Afrihost, it belongs to Telkom's installation on shared infrastructure that routes traffic (by realm) to their respective networks. This is usually indicative of congestion, but not always a given. However we have no influence whatsoever on that infrastructure as we literally do not have access to it.
 
Looking at the second hop on your Afrihost tracert - AfriPeeps will 99% tell you that your exchange is congested and it has nothing to do with your network.

However, you can see this is not the case on the Telkom Traceroute.

For good measure, Could you get a 1 Gig Crystal Web Free account - http://crystalweb.co.za/free-trial.php

And post a traceroute while using their network. So then we have 3 different ISPs and backbones we are looking at.

Remember that if this is congestion on the line or the exchange, switching accounts my temporarily improve your stats until they degrade back to what they were, depending on whether it's a degrading sync issue on the line or intermittent congestion on the entire exchange. I would think as a Telkom employee you would be clear that we don't own those network devices, they belong to Telkom exlcusively :(
 
So, I am at a house where they have 2 Business Accounts with my recomendation.
I came to have a look today as they have said the last two weeks the speed is very slow.

Have a look at this...

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.0.1
2 10 ms 10 ms 10 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.
4.193]
3 12 ms 11 ms 11 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
4 12 ms 12 ms 14 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 29 ms 12 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 37 ms 60 ms 36 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

7 36 ms 36 ms 36 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.25
5]
8 46 ms 35 ms 37 ms 196.44.31.99
9 1066 ms 1439 ms 1669 ms 196.30.1.53
10 722 ms 1026 ms 878 ms 196.31.220.27
11 185 ms 113 ms 144 ms 196.31.63.202
12 296 ms 298 ms 307 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 371 ms 392 ms 389 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.



Support is offline, chat is offline.
Every other account I have tested works perfectly and its just the Afrihost Business account that taps out at 150kb.

Webafrica to Afrihsot


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.0.1
2 10 ms 11 ms 10 ms 196-210-146-129.dynamic.isadsl.co.za [196.210.14
6.129]
3 11 ms 11 ms 11 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
4 11 ms 12 ms 11 ms 196.35.115.136
5 13 ms 12 ms 12 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1
3]
6 107 ms 128 ms 163 ms 168.209.2.130
7 11 ms 12 ms 11 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 12 ms 13 ms 12 ms 196.44.0.75
9 30 ms 31 ms 33 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

10 31 ms 31 ms 30 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
11 215 ms 173 ms 133 ms 196.31.220.12
12 183 ms 147 ms 149 ms 196.31.220.25
13 155 ms 148 ms 140 ms 196.31.63.206
14 67 ms 112 ms 143 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
15 103 ms 104 ms 124 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Looks like it may have been a temporary network issue on our corporate server. I wasn't aware of any issues but if this is still happening please post more results so I can chase this up with our team :(
 
For some AH works perfectly, for others its really bad.


Very strange.

There is a lot of variable and circumstances that come into play. If we could have all the facts down to the quality of cabling, conditions (like weather) etc, then we might have a better basis to understand the differences.

From what I can see, in general the network was doing well over the weekend.
 
Was getting terrible lag on GTA last night, eventually could not join any local hosted sessions. Anyone else having the same issues?

Get in a car as a passanger and every few seconds the car teleports across the road and cars falling out the sky, just overall not working. If I join internationally hosted session and drive around with international players it seems better.

Also not the pc, game runs perfectly on offline.

We ran some extensive tests on GTA 5 using capped and uncapped accounts, and so far the tests seem positive in terms of game performance. We're still testing further to see under which scenarios the game does not, however it does seem from forum reports that there could be some factors within the game design as well :(
 
Now we wait for one of the AfriTeam to come and apologise for the poor performance over the weekend, and make empty promises....

Latency up the creek this morning again! :mad:

Latency definitely looks pretty solid this morning over the general network.

Can you show me some results to look at?
 
We ran some extensive tests on GTA 5 using capped and uncapped accounts, and so far the tests seem positive in terms of game performance. We're still testing further to see under which scenarios the game does not, however it does seem from forum reports that there could be some factors within the game design as well :(

It's really weird, pings all seem okay, will post when I get home tonight after trying again.

Seems only when playing on a locally hosted session.
 
Traceroute to the game server may help us see what could be happening :(

Any idea how to get that information, checked in most of the settings cannot seem to find any server information so would know what to ping.
 
Any idea how to get that information, checked in most of the settings cannot seem to find any server information so would know what to ping.

When connected to the server, ALT-Tab out and open your network connections under the Resource monitor. You should be able to see the IP of the server from there.
 
When connected to the server, ALT-Tab out and open your network connections under the Resource monitor. You should be able to see the IP of the server from there.

Shweet, did'nt even think about that, suppose I could also just use netstat and check for connections opened by the process. Was raging last night gave up after two hours of not being able to join the crew session.
 
Shweet, did'nt even think about that, suppose I could also just use netstat and check for connections opened by the process. Was raging last night gave up after two hours of not being able to join the crew session.

Indeed. Any network traffic monitoring tool should work just as well - if not better (ease of use) - than the built in monitor.

Should actually get a nice network monitoring tool myself now that I think about it. Hope you come right!
 
Latency definitely looks pretty solid this morning over the general network.

Can you show me some results to look at?

You guys said you have identified the problem and are waiting for MTN?
Nothing has changed since November 2014?
I post trace routes and nothing changes on my end?
I have pm'ed everyone AfriGenie, AfriGuy and yourself tons of results?

One would have thought that seeing as this fault is affecting an entire group of exchanges this would be rectified quickly? :confused:
It would seem I am beating a dead horse here, I can clearly see now that lip service is all that is on offer, not trying to be funny but I spend a good sum of money for this S*** and I would expect faster turn around times.
6 months is very patient don't you think?

1 105-237-134-1-esr-lo.mtnbusiness.co.za 3.568 ms 3.988 ms 4.133 ms
2 41.181.221.213 (41.181.221.213) 117.611 ms 161.040 ms 166.058 ms
3 41.181.221.214 (41.181.221.214) 140.375 ms 126.740 ms 122.657 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 146.627 ms 1205.640 ms 129.569 ms
5 rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 125.420 ms 178.214 ms 1110.910 ms
6 jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221) 175.098 ms
196.44.31.97 (196.44.31.97) 128.961 ms 129.758 ms
7 196.31.220.10 (196.31.220.10) 129.139 ms 156.459 ms 184.548 ms
8 196.31.220.21 (196.31.220.21) 129.805 ms 129.175 ms 137.159 ms
9 196.31.63.202 (196.31.63.202) 175.718 ms 176.312 ms 129.096 ms
10 vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133) 128.775 ms 158.705 ms 130.792 ms
11 cms-gm.afrihost.com (197.242.144.102) 142.880 ms 131.894 ms 162.579 ms
 
I think the thing to remember is that the device on that hop does not belong to Afrihost, it belongs to Telkom's installation on shared infrastructure that routes traffic (by realm) to their respective networks. This is usually indicative of congestion, but not always a given. However we have no influence whatsoever on that infrastructure as we literally do not have access to it.

Ok, but heres the thing ....

I just cant continue with these sudden connectivity drops.

If other ISPs had the same - fine. but as soon as I swing over to another ISP, the problem goes away.

Surely there is enough evidence for you look into my account?
Remember too, that you changed my log in details and all that fine stuff not so long ago because of authentication issues on your side - this after we had just this discussion.

Edit - I am sure I have seen other customers posting similar symptoms - surely there is enough cause for concern from your end.

I dont want to be one of those hard a rsed posters on your thread. Really I dont, but I say again .... there MUST be more to this than simply its a Telkom issue?
 
Last edited:
Any idea how to get that information, checked in most of the settings cannot seem to find any server information so would know what to ping.

Some games have standard lists of servers by region (or may show the server when you test in game ping). Depends on the game.
 
You guys said you have identified the problem and are waiting for MTN?
Nothing has changed since November 2014?
I post trace routes and nothing changes on my end?
I have pm'ed everyone AfriGenie, AfriGuy and yourself tons of results?

One would have thought that seeing as this fault is affecting an entire group of exchanges this would be rectified quickly? :confused:
It would seem I am beating a dead horse here, I can clearly see now that lip service is all that is on offer, not trying to be funny but I spend a good sum of money for this S*** and I would expect faster turn around times.
6 months is very patient don't you think?

1 105-237-134-1-esr-lo.mtnbusiness.co.za 3.568 ms 3.988 ms 4.133 ms
2 41.181.221.213 (41.181.221.213) 117.611 ms 161.040 ms 166.058 ms
3 41.181.221.214 (41.181.221.214) 140.375 ms 126.740 ms 122.657 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 146.627 ms 1205.640 ms 129.569 ms
5 rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 125.420 ms 178.214 ms 1110.910 ms
6 jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221) 175.098 ms
196.44.31.97 (196.44.31.97) 128.961 ms 129.758 ms
7 196.31.220.10 (196.31.220.10) 129.139 ms 156.459 ms 184.548 ms
8 196.31.220.21 (196.31.220.21) 129.805 ms 129.175 ms 137.159 ms
9 196.31.63.202 (196.31.63.202) 175.718 ms 176.312 ms 129.096 ms
10 vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133) 128.775 ms 158.705 ms 130.792 ms
11 cms-gm.afrihost.com (197.242.144.102) 142.880 ms 131.894 ms 162.579 ms

I think it's just important to note that the latency is not on our side, it's on the Telkom infrastructure. How that is able to perform differently on a SAIX account say, only Telkom can answer because how traffic gets routed from your line to the exchange to the BRAS and then eventually to our network is totally in their hands.
 
Ok, but heres the thing ....

I just cant continue with these sudden connectivity drops.

If other ISPs had the same - fine. but as soon as I swing over to another ISP, the problem goes away.

Surely there is enough evidence for you look into my account?
Remember too, that you changed my log in details and all that fine stuff not so long ago because of authentication issues on your side - this after we had just this discussion.

Edit - I am sure I have seen other customers posting similar symptoms - surely there is enough cause for concern from your end.

I dont want to be one of those hard a rsed posters on your thread. Really I dont, but I say again .... there MUST be more to this than simply its a Telkom issue?

It's definitely not a good situation and I totally feel your pain. I've raised this issue several times and MTN and our engineers have proven that 2nd hope latency to ESR hardware cannot be controlled or affected by our network in any way. However, it does seem like for some users they switch IP addresses at times and their experience is completely different, which I don't fully understand. I've asked our team to use one client's example to raise with Telkom to try to unpack what could be happening :(
 
I think it's just important to note that the latency is not on our side, it's on the Telkom infrastructure. How that is able to perform differently on a SAIX account say, only Telkom can answer because how traffic gets routed from your line to the exchange to the BRAS and then eventually to our network is totally in their hands.

What I find totally strange is that only MTN based accounts are affected? All other ISP backbones are perfect?
 
What I find totally strange is that only MTN based accounts are affected? All other ISP backbones are perfect?

We have asked Telkom why this is and what can be done by their technicians to resolve this. It could be how they are treating traffic from our realms :(
 
We have asked Telkom why this is and what can be done by their technicians to resolve this. It could be how they are treating traffic from our realms :(

Surely MTN has a SLA in place with Telkom? It is not like I have a line fault, rather a bulk fault. As it would make no difference if I was connected to a different DP I would still encounter the same fault...
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X