Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
TEXTILE GUY said:
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.
Click to expand...

ghostR said:
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.
Click to expand...

CW Tracert


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 8 ms 9 ms 8 ms 196-210-132-1.dynamic.isadsl.co.za [196.210.132.
1]
3 10 ms 10 ms 25 ms cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.2
45]
4 10 ms 9 ms 9 ms cdsl1-umh-bd150.ip.isnet.net [196.26.210.192]
5 11 ms 10 ms 9 ms mi-za-umh-p7-ten-0-0-0-1.ip.isnet.net [168.209.9
3.203]
6 25 ms 23 ms 24 ms mi-za-bry-p7-lo0.ip.isnet.net [168.209.255.208]

7 28 ms 22 ms 22 ms core2a-bry-gi0-0-0.ip.isnet.net [168.209.217.2]

8 22 ms 25 ms 21 ms 168.209.100.205
9 21 ms 24 ms 21 ms 196.26.0.10
10 28 ms 23 ms 24 ms mtnns-2.jinx.net.za [196.223.14.31]
11 25 ms 26 ms 27 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

12 24 ms 25 ms 43 ms 196.44.31.99
13 25 ms 25 ms 41 ms 196.30.1.39
14 24 ms * 24 ms 196.31.220.23
15 28 ms 24 ms 24 ms 196.31.63.206
16 27 ms 24 ms 24 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
17 26 ms 24 ms 24 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Okeeeee dokeeeee - seems AH has a problem

Tks @GhostR

EDit CW test account is REALLY smooth .... maybe I should .......
 
TEXTILE GUY said:
CW Tracert


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 8 ms 9 ms 8 ms 196-210-132-1.dynamic.isadsl.co.za [196.210.132.
1]
3 10 ms 10 ms 25 ms cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.2
45]
4 10 ms 9 ms 9 ms cdsl1-umh-bd150.ip.isnet.net [196.26.210.192]
5 11 ms 10 ms 9 ms mi-za-umh-p7-ten-0-0-0-1.ip.isnet.net [168.209.9
3.203]
6 25 ms 23 ms 24 ms mi-za-bry-p7-lo0.ip.isnet.net [168.209.255.208]

7 28 ms 22 ms 22 ms core2a-bry-gi0-0-0.ip.isnet.net [168.209.217.2]

8 22 ms 25 ms 21 ms 168.209.100.205
9 21 ms 24 ms 21 ms 196.26.0.10
10 28 ms 23 ms 24 ms mtnns-2.jinx.net.za [196.223.14.31]
11 25 ms 26 ms 27 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

12 24 ms 25 ms 43 ms 196.44.31.99
13 25 ms 25 ms 41 ms 196.30.1.39
14 24 ms * 24 ms 196.31.220.23
15 28 ms 24 ms 24 ms 196.31.63.206
16 27 ms 24 ms 24 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
17 26 ms 24 ms 24 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Okeeeee dokeeeee - seems AH has a problem

Tks @GhostR

EDit CW test account is REALLY smooth .... maybe I should .......
Click to expand...

Well - There, Your problem is solved - You know what to do before the 24th of the month...
 
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.
 
Last edited:
Rickster said:
For some AH works perfectly, for others its really bad.


Very strange.
Click to expand...

The few that are happy all the time are mostly in JHB.
Nearly ALL of us poor sods in Cape Town have constant issues.... been struggling with high latency for the last month, and now that it "magically" fixed itself, I am being limited on ALL protocols (even SFTP/SSH). My torrents have slowed to the point that I now wait the whole day to get 4 well seeded files (in excess of 1000 seeds each), where it normally takes 1 hour.

AH's stock answer is "exchange congestion"... but it cannot be that every exchange in the country is congested (and only on MTN-based accounts).

The truth, ONCE AGAIN, is that their IPC is congested - they once again need more capacity, and this will be the 4th time in a year. It is really hard to accept that a company can be this poor at planning ALL THE TIME. One would think that they would have learnt from the last 3 fiasco's :(
 
cortexenslaver said:
AH's stock answer is "exchange congestion"... but it cannot be that every exchange in the country is congested (and only on MTN-based accounts).
(
Click to expand...

Damn exchange .... its picking on AH,

It doesnt have a problem with Telkom or CW .... its picking on AH.

Dammit
 
Playing a game of Lol and I can see my ping steadily increasing the whole time. From 220, which already isn't the lowest, all the way to 280 over the course of 10 minutes. Switch to Vox and I get 195ms.

Please can you guys just sort your **** out already. This is not the first time this happened...
 
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.
 
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:
 
ghostR said:
Probably a lot of it... But they don't care... Wait till something magical happens
Click to expand...

Yo dude

Please can you stop posting our threads as a client. when we know that you work for Telkom and as far as I know you are not even using our products. These threads are for us Afrihost Reps to engage with Afrihost clients.

What you are doing is not cool at all. :(
 
Dianysis said:
Don't have the patience for this right now.

And AH, when I do eventually get a reply on Monday, please:

1. Don't tell me that there isn't any issues on the network - I really don't care. I am having an issue and that is what matters to me.

2. Don't just tell me that there was a peak in demand between X pm and Y pm - I really don't care. If there is a peak in demand - then why is your network affected so badly?

3. Don't ask me if I am seeing any problems with other protocals - EVERYTHING is slow.

4. Don't ask me how latencies are - they are high on AH as can be seen on the tracerts.

Please provide a reply that can actually improve my situation.

Thank you.
Click to expand...

I totally understand your frustration and I do want to assure you that we are doing everything possible to resolve this situation with every resource we have available. From your post, I take it you do have an understanding of the challenges we face, so the best I can do here is assure you that we are working on this as our highest priority and we won't spare any effort or expense to improve your experience.
 
Gavin107 said:
Something has been wrong all day...

I dont understand why if the trace route shows relatively low latency (am I wrong?), throughput should be so bad? What are these "Request time out" - is this congestion or packet loss and what causes it?

2858781399.png

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=18 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=18 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=18 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=18 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=19 ms


ping 8.8.8.8

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


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 28.648 ms 18.287 ms 18.111 ms
4 41.181.221.218 18.054 ms 18.104 ms 17.506 ms
5 41.181.165.118 49.489 ms 17.867 ms
Request timed out *
6 Request timed out * *
196.44.31.122 18.623 ms
7 196.44.0.221 18.207 ms 18.604 ms 18.63 ms
8 196.30.1.53 18.696 ms
196.31.220.10 18.057 ms
196.30.1.39 18.998 ms
9 Request timed out *
196.31.220.21 18.128 ms
196.31.220.27 19.017 ms
10 196.31.63.206 21.878 ms 18.319 ms
196.31.63.202 18.344 ms
11 196.30.42.133 18.492 ms 18.436 ms 18.292 ms
12 Request timed out *
197.242.144.102 19.193 ms 18.908 ms
13 197.242.144.102 18.444 ms


traceroute -n 8.8.8.8

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 18.383 ms 18.655 ms 17.816 ms
4 41.181.221.218 20.124 ms 17.747 ms 17.319 ms
5 41.181.165.118 17.644 ms 17.407 ms 17.503 ms
6 196.44.0.155 17.856 ms
196.44.31.122 18.177 ms 55.705 ms
7 41.181.139.99 20.142 ms 21.64 ms 18.132 ms
8 72.14.194.74 24.145 ms 18.153 ms 18.754 ms
9 72.14.239.35 19.043 ms 18.469 ms
72.14.239.33 19.048 ms
10 Request timed out *
8.8.8.8 21.05 ms 19.124 ms
11 8.8.8.8 18.47 ms
Click to expand...

We have several systems running on the network that attempt to protect latency as highest priority and throughput secondary. This is not by any kind of shaping but how we have setup of the broadband traffic structures to that latency dependant services can still operate even if throughput is not optimal at time.s
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X