Afrihost Business Uncapped Feedback

Status
Not open for further replies.
Gatecrasher said:
What is the point of quoting that? It rules out very little. Does it say don't complain? No, it doesn't. Feedback surely incorporates complaining. And the complaint poses a very good question:

Since so many premium clients in the South are hitting capacity constraints (streaming is hopeless again tonight) what is the rationale of another massive gigabyte giveaway? Should they not have waited until the new capacity goes live?
Click to expand...

My point exactly, but suppose some people like to come here and say everything is fine, and lets give Afrihost more awards for fanstastic service and quality.
 
If that includes me - just remember, I'm in the exact same boat as you with these capacity issues,
 
And this is what I get on a 4mb line at midnight on a Friday. It took around 5 minutes just to post this thing.




traceroute to afrihost.co.za (197.242.144.102), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 20.744 ms 0.848 ms 0.713 ms
2 105-236-0-129-esr-lo.mtnbusiness.co.za (105.236.0.129) 799.493 ms 754.173 ms 747.508 ms
3 41.181.222.42 (41.181.222.42) 934.475 ms 778.774 ms 712.183 ms
4 ng-mse-1--ng-cr-1-a.za.mtnns.net (196.44.27.68) 917.276 ms 702.791 ms 821.999 ms
5 jh-cr-1.za--ng-cr-1.za.mtnns.net (196.44.31.176) 740.057 ms 663.488 ms 765.785 ms
6 rb-cr-2.za--jh-cr-1.za.mtnns.net (196.44.0.43) 918.217 ms 1055.426 ms 1245.762 ms
7 qux--rb-dca-2.za-b.za.mtnbusiness.net (41.181.165.119) 1228.954 ms 1117.033 ms 1091.445 ms
8 196.30.1.53 (196.30.1.53) 1274.986 ms
196.30.1.39 (196.30.1.39) 1182.604 ms 702.978 ms
9 196.31.220.21 (196.31.220.21) 875.774 ms
196.31.220.25 (196.31.220.25) 895.946 ms 809.904 ms
10 196.31.63.202 (196.31.63.202) 823.032 ms 808.247 ms
196.31.63.206 (196.31.63.206) 852.106 ms
11 196.30.42.133 (196.30.42.133) 761.337 ms 635.544 ms 917.001 ms
12 cms-gm.afrihost.com (197.242.144.102) 1186.162 ms !Z 1441.727 ms !Z 1387.736 ms !Z
 
This morning my 10mb business account is flying. YIPEEE!
 
So I'm on 10mb business in in Durban, one of the lucky few that have little-to-no issues.

One weird thing that's happening is I am unable to load www.buzzfeed.com. Anybody else?

I'm using UnoTelly's Jhb & Germany DNS servers.

Here's a tracert:

tracert www.buzzfeed.com

Tracing route to e6454.g.akamaiedge.net [23.221.59.115] over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 105-236-0-129-esr-lo.mtnbusiness.co.za [105.236.0.129]
3 17 ms 19 ms 21 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14]
4 17 ms 17 ms 17 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]
5 20 ms 17 ms 20 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]
6 17 ms 17 ms 17 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
7 17 ms 17 ms 16 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.165.119]
8 39 ms 50 ms 56 ms ct-cr-1.za--ct-cr-2.za-a.mtnns.net [196.44.31.109]
9 197 ms 194 ms 195 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
10 181 ms 181 ms 182 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
11 185 ms 184 ms 184 ms 195.50.122.181
12 * * * Request timed out.
13 185 ms 189 ms 185 ms 196.41.24.122
14 184 ms 219 ms 184 ms 41.193.119.14
15 184 ms 187 ms 184 ms 41.193.160.54
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.

Also, Facebook videos do not load at all.

Besides that, everything seems to be great (full speed browsing & downloads / normal latency).

Anyone have any idea as to whats going on?

Thanks
 
isabelladol said:
And this is what I get on a 4mb line at midnight on a Friday. It took around 5 minutes just to post this thing.




traceroute to afrihost.co.za (197.242.144.102), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 20.744 ms 0.848 ms 0.713 ms
2 105-236-0-129-esr-lo.mtnbusiness.co.za (105.236.0.129) 799.493 ms 754.173 ms 747.508 ms
3 41.181.222.42 (41.181.222.42) 934.475 ms 778.774 ms 712.183 ms
4 ng-mse-1--ng-cr-1-a.za.mtnns.net (196.44.27.68) 917.276 ms 702.791 ms 821.999 ms
5 jh-cr-1.za--ng-cr-1.za.mtnns.net (196.44.31.176) 740.057 ms 663.488 ms 765.785 ms
6 rb-cr-2.za--jh-cr-1.za.mtnns.net (196.44.0.43) 918.217 ms 1055.426 ms 1245.762 ms
7 qux--rb-dca-2.za-b.za.mtnbusiness.net (41.181.165.119) 1228.954 ms 1117.033 ms 1091.445 ms
8 196.30.1.53 (196.30.1.53) 1274.986 ms
196.30.1.39 (196.30.1.39) 1182.604 ms 702.978 ms
9 196.31.220.21 (196.31.220.21) 875.774 ms
196.31.220.25 (196.31.220.25) 895.946 ms 809.904 ms
10 196.31.63.202 (196.31.63.202) 823.032 ms 808.247 ms
196.31.63.206 (196.31.63.206) 852.106 ms
11 196.30.42.133 (196.30.42.133) 761.337 ms 635.544 ms 917.001 ms
12 cms-gm.afrihost.com (197.242.144.102) 1186.162 ms !Z 1441.727 ms !Z 1387.736 ms !Z
Click to expand...

That is DEFINITELY exchange congestion :-(

You should be getting under 20ms on your second hop, yet you are getting 800ms :/

Youll have to report a line fault.
 
prodigyX said:
So I'm on 10mb business in in Durban, one of the lucky few that have little-to-no issues.

One weird thing that's happening is I am unable to load www.buzzfeed.com. Anybody else?

I'm using UnoTelly's Jhb & Germany DNS servers.

Here's a tracert:

tracert www.buzzfeed.com

Tracing route to e6454.g.akamaiedge.net [23.221.59.115] over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 105-236-0-129-esr-lo.mtnbusiness.co.za [105.236.0.129]
3 17 ms 19 ms 21 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14]
4 17 ms 17 ms 17 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]
5 20 ms 17 ms 20 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]
6 17 ms 17 ms 17 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
7 17 ms 17 ms 16 ms qux--rb-dca-2.za-b.za.mtnbusiness.net [41.181.165.119]
8 39 ms 50 ms 56 ms ct-cr-1.za--ct-cr-2.za-a.mtnns.net [196.44.31.109]
9 197 ms 194 ms 195 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
10 181 ms 181 ms 182 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
11 185 ms 184 ms 184 ms 195.50.122.181
12 * * * Request timed out.
13 185 ms 189 ms 185 ms 196.41.24.122
14 184 ms 219 ms 184 ms 41.193.119.14
15 184 ms 187 ms 184 ms 41.193.160.54
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.

Also, Facebook videos do not load at all.

Besides that, everything seems to be great (full speed browsing & downloads / normal latency).

Anyone have any idea as to whats going on?

Thanks
Click to expand...

Looks like UnoTelly is timing out :/ Could you try using the CPT server?

Z
 
I've already reported it, but I also reported the exact same thing 12 months ago :(
It seems Telkom really doesn't want to bother upgrading their infrastructure...
 
Zertop said:
Looks like UnoTelly is timing out :/ Could you try using the CPT server?

Z
Click to expand...

The Cape Town server is dead, which is why I switched to the new Joburg server. Every other DNS lookup is fine, I just appear to be having routing issues with buzzfeed.com. I will switch to another just to to test though, and post results here

Update: Looks like the CPT UnoTelly server is back up and running.. switched to that and everything is awesome again. Thanks for the advice man :)
 
Last edited:
isabelladol said:
And this is what I get on a 4mb line at midnight on a Friday. It took around 5 minutes just to post this thing.




traceroute to afrihost.co.za (197.242.144.102), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 20.744 ms 0.848 ms 0.713 ms
2 105-236-0-129-esr-lo.mtnbusiness.co.za (105.236.0.129) 799.493 ms 754.173 ms 747.508 ms
3 41.181.222.42 (41.181.222.42) 934.475 ms 778.774 ms 712.183 ms
4 ng-mse-1--ng-cr-1-a.za.mtnns.net (196.44.27.68) 917.276 ms 702.791 ms 821.999 ms
5 jh-cr-1.za--ng-cr-1.za.mtnns.net (196.44.31.176) 740.057 ms 663.488 ms 765.785 ms
6 rb-cr-2.za--jh-cr-1.za.mtnns.net (196.44.0.43) 918.217 ms 1055.426 ms 1245.762 ms
7 qux--rb-dca-2.za-b.za.mtnbusiness.net (41.181.165.119) 1228.954 ms 1117.033 ms 1091.445 ms
8 196.30.1.53 (196.30.1.53) 1274.986 ms
196.30.1.39 (196.30.1.39) 1182.604 ms 702.978 ms
9 196.31.220.21 (196.31.220.21) 875.774 ms
196.31.220.25 (196.31.220.25) 895.946 ms 809.904 ms
10 196.31.63.202 (196.31.63.202) 823.032 ms 808.247 ms
196.31.63.206 (196.31.63.206) 852.106 ms
11 196.30.42.133 (196.30.42.133) 761.337 ms 635.544 ms 917.001 ms
12 cms-gm.afrihost.com (197.242.144.102) 1186.162 ms !Z 1441.727 ms !Z 1387.736 ms !Z
Click to expand...

What happens when you try another ISP?
 
prodigyX said:
The Cape Town server is dead, which is why I switched to the new Joburg server. Every other DNS lookup is fine, I just appear to be having routing issues with buzzfeed.com. I will switch to another just to to test though, and post results here

Update: Looks like the CPT UnoTelly server is back up and running.. switched to that and everything is awesome again. Thanks for the advice man :)
Click to expand...

No probs!
 
isabelladol said:
I get the same results, I have tried using an Axxess account as well as the Telkom guest account.
Click to expand...

Yea, from those trace routes it definitely looks like a line issue :(

OKay, have you tried calling your local telkom shop as opposed to the hotline? That usually gets things done :)
 
Zertop said:
That is DEFINITELY exchange congestion :-(

You should be getting under 20ms on your second hop, yet you are getting 800ms :/

Youll have to report a line fault.
Click to expand...

No matter which ISP you use you will never get good results, Only way is to log faults with Telkom and bug them everyday.
It took 8 months of me complaining to get our exchange fixed.

Good Luck!
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X