Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Just checked - improved but not completely. Tops out at 6mbps.
Typical service - high 8's - consistently.

It'll take a few minutes for the speeds to stabilize completely in the South, you should continue to see an improvement over the next 20 to 30 minutes.
 
Decided to do a tracert too:

C:\Users\Brendan>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 10.0.0.2
2 * * * Request timed out.
3 * 328 ms 396 ms 41.181.51.181
4 * * 197 ms 41.181.51.182
5 * * 370 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 * * * Request timed out.
7 178 ms 111 ms 142 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 * * * Request timed out.
9 * * * Request timed out.
10 * 148 ms 321 ms 196.31.220.10
11 431 ms 188 ms 270 ms 196.31.220.21
12 * 288 ms 508 ms 196.31.63.202
13 178 ms 206 ms 273 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 262 ms 359 ms 71 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Doesn't look good
 
And just tested again:



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

1 1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 * 280 ms 348 ms 41.181.51.181
4 * 264 ms 262 ms 41.181.51.182
5 105 ms 108 ms 58 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 191 ms 200 ms 214 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 308 ms 315 ms 223 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 220 ms 305 ms 329 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

9 187 ms 256 ms 239 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
10 * 168 ms 260 ms 196.31.220.10
11 * 411 ms 93 ms 196.31.220.21
12 264 ms 299 ms 308 ms 196.31.63.202
13 * * * Request timed out.
14 227 ms 225 ms 191 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
And just tested again:



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

1 1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 * 280 ms 348 ms 41.181.51.181
4 * 264 ms 262 ms 41.181.51.182
5 105 ms 108 ms 58 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 191 ms 200 ms 214 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 308 ms 315 ms 223 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 220 ms 305 ms 329 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

9 187 ms 256 ms 239 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
10 * 168 ms 260 ms 196.31.220.10
11 * 411 ms 93 ms 196.31.220.21
12 264 ms 299 ms 308 ms 196.31.63.202
13 * * * Request timed out.
14 227 ms 225 ms 191 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

I've reset your Capped account, would you mind restarting your modem and testing again.

Are you running this test from your 4Mbps or 10Mbps ADSL line?
 
I've reset your Capped account, would you mind restarting your modem and testing again.

Are you running this test from your 4Mbps or 10Mbps ADSL line?

4mb line at the office.

Will test the 10mb when i get home soon. Im out of office now, but will check once im home on both.

Thanks
 

Just did a quick speedtest after resetting router at work (4mb Line)


Tracert below:

C:\Users\Brendan>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 10.0.0.2
2 * * * Request timed out.
3 315 ms 275 ms 138 ms 41.181.53.149
4 326 ms 318 ms 181 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
5 278 ms 245 ms * tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 * * * Request timed out.
7 * * * Request timed out.
8 345 ms 248 ms 167 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

9 * * * Request timed out.
10 * * * Request timed out.
11 * 220 ms 227 ms 196.31.220.21
12 * * * Request timed out.
13 * * * Request timed out.
14 281 ms 186 ms 52 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
Just did a quick speedtest after resetting router at work (4mb Line)


Tracert below:

C:\Users\Brendan>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 10.0.0.2
2 * * * Request timed out.
3 315 ms 275 ms 138 ms 41.181.53.149
4 326 ms 318 ms 181 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
5 278 ms 245 ms * tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 * * * Request timed out.
7 * * * Request timed out.
8 345 ms 248 ms 167 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

9 * * * Request timed out.
10 * * * Request timed out.
11 * 220 ms 227 ms 196.31.220.21
12 * * * Request timed out.
13 * * * Request timed out.
14 281 ms 186 ms 52 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

That latency is a bit high for my liking, are you consistently getting those levels at work?
 
it seems the incorrect throughput limit had been set for our Business Uncapped and Capped accounts so we were under-utilizing the IPC.

Both of those account types are supposed to be Unshaped.
Unshaped = No Throughput limits, therefor, how can they have an incorrect throughput limit, they are meant to run at the sync rate of the line regardless of protocol?

Or is your definition of unshaped different to the internationally accepted definition?
 
Both of those account types are supposed to be Unshaped.
Unshaped = No Throughput limits, therefor, how can they have an incorrect throughput limit, they are meant to run at the sync rate of the line regardless of protocol?

Or is your definition of unshaped different to the internationally accepted definition?

The bandwidth limit was incorrectly set not for the individual accounts, but rather for the entire Unshaped (which include Capped and Business Uncapped) pipeline that all the Unshaped traffic runs through.
 
Sweet. CPT back to normal.
@Afrigenie - do you mind sharing what the issue was? Would be good for future reference.
 
Hooray ... looking much better

4218279450.png


4218282123.png
 
Sweet. CPT back to normal.
@Afrigenie - do you mind sharing what the issue was? Would be good for future reference.

In short, without getting too technical, the limit that our combined Business Uncapped and Capped users had access to in the South - so all of the accounts combined together - was set to the incorrect value after we resolved the weekend's issue, this was not a problem early in the morning, but as the day passed and more users came online, this started to limit the speeds that each User was getting. Simply correcting this value ensured that everyone's speeds went back to normal.
 
FYI. I just received my bandwidth notice for my ADSL. The below was in the email which is weird because 1. I am not on mobile data package. 2. Thought data expired at end of the month.

Do Topups carry over into the new month?

Yes, they do.*All Mobile Data Topups purchased will only expire at the end of the NEXT month. For example, if you buy a data topup on 5 February, your topup data will only expire at midnight on 31 March – giving you even more value.
 
In short, without getting too technical, the limit that our combined Business Uncapped and Capped users had access to in the South - so all of the accounts combined together - was set to the incorrect value after we resolved the weekend's issue, this was not a problem early in the morning, but as the day passed and more users came online, this started to limit the speeds that each User was getting. Simply correcting this value ensured that everyone's speeds went back to normal.

Not everyone. I get 2meg from Afrihost and 5.5meg from Telkom. Usually you guys are rock solid stable and now this happens :(
 
Another day of issues? 4th day on Afrihost, 4th day of up and down speeds. Had 210kbps downloads 2 hours ago on a 2mb line, now between 20 and 30...
 
Hi,

My line is still not running as it should.

Test 1


Test 2



Should be 37+Mbps
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X