Afrihost New Network Feedback

Status
Not open for further replies.
Now just to wait for Telkom to show up...and soon....SOON I'll have Afrihost as my isp. :D Dat sweet 4mb line wil be a massive upgrade from iBurst rofl ;_;
 
My 20Mbps VDSL line was unusable today, even though the line seemed fine.

So I ran "Fix my line", and that immediately killed the line stone dead by setting UL and DL to 65kbps. Which idiot set this up ?

And zero support, no phone, no online text, no e-mail, no Twitter, no FB.

Time for a new ISP, it seems.
 
My 20Mbps VDSL line was unusable today, even though the line seemed fine.

So I ran "Fix my line", and that immediately killed the line stone dead by setting UL and DL to 65kbps. Which idiot set this up ?

And zero support, no phone, no online text, no e-mail, no Twitter, no FB.

Time for a new ISP, it seems.

Phone telkom and tell them to do a port reset.
 
OK, so someone from AH came in this morning and reset the line, so all is fine again.

But this leaves a few questions :

1) Why do AH lines often die on Saturday afternoons ? This also happened a few weeks ago.

2) Why is there no support to resolve this ? Yesterday there was absolutely nothing, no phone support, no chat support, no e-mail support.

3) Why does the "Fix my line" function just set the line to 65kbps and effectively kill it stone dead. This used to be a valuable tool in the past, AFAIK it used to perform a port reset and often fixed the line, now it just kills it, so one should under no circumstances run this tool.

Is it just "all fall down" at AH ?
 
OK, so someone from AH came in this morning and reset the line, so all is fine again.
But this leaves a few questions :

1) Why do AH lines often die on Saturday afternoons ? This also happened a few weeks ago.

2) Why is there no support to resolve this ? Yesterday there was absolutely nothing, no phone support, no chat support, no e-mail support.

3) Why does the "Fix my line" function just set the line to 65kbps and effectively kill it stone dead. This used to be a valuable tool in the past, AFAIK it used to perform a port reset and often fixed the line, now it just kills it, so one should under no circumstances run this tool.

Is it just "all fall down" at AH ?

1) Afrihost line = Telkom line, Afrihost just manages it for you (as in billing, if you need support, etc)
2) Call them?
011 612 7200
Mon-Fri 07:00-20:00 / Sat-Sun 09:00-15:00
www.afrihost.com
3) Telkom changed the system to ASSIA which is supposed to do it all automatically but so far it just seems to degrade the lines more than it fixes them.
 
Did international traffic just take a hit?

Tracing route to bbc.co.uk [212.58.246.79]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 99 ms 108 ms 123 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 94 ms 83 ms 71 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 80 ms 81 ms 83 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 123 ms 186 ms 140 ms 41.162.84.192
7 59 ms 85 ms 105 ms 172.18.1.162
8 * * * Request timed out.
9 280 ms * 300 ms if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net [216.6.55.85]
10 302 ms 298 ms 299 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 419 ms * * if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
15 399 ms * * if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
16 * * * Request timed out.
17 413 ms 397 ms 355 ms 195.219.83.102
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * 419 ms * ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
23 305 ms * * 132.185.255.165
24 * * 313 ms 212.58.246.79

Trace complete.
 
Last edited:
Did international traffic just take a hit?

Definately super bad for me

Flickr via Afrihost
tracert www.flickr.com

Tracing route to flickr-panda-police.a00.yahoodns.net [217.12.1.155]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 46 ms 49 ms 54 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 19 ms 22 ms 19 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 65 ms 61 ms 64 ms 41.162.84.192
6 84 ms 87 ms 87 ms 172.18.1.162
7 * * * Request timed out.
8 * 201 ms * if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
9 196 ms 195 ms 194 ms if-ae-5-90.tcore2.pv9-lisbon.as6453.net [80.231.159.109]
10 241 ms * * if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
11 * * 259 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
12 249 ms 248 ms * if-ae-2-2.tcore2.sv8-highbridge.as6453.net [80.231.139.1]
13 187 ms 187 ms 188 ms if-ae-11-2.tcore1.l78-london.as6453.net [80.231.139.42]
14 * * * Request timed out.
15 * 253 ms * 195.219.83.102
16 * * * Request timed out.
17 * * * Request timed out.
18 * * 194 ms yahoo-inc.ear2.london15.level3.net [212.187.173.178]
19 * * * Request timed out.
20 * 199 ms * r1.ycpi.vip.loa.yahoo.net [217.12.1.155]
21 * * * Request timed out.
22 * 197 ms 197 ms r1.ycpi.vip.loa.yahoo.net [217.12.1.155]

Trace complete.

Flickr Via XDSL

tracert www.flickr.com

Tracing route to flickr-panda-police.a00.yahoodns.net [217.12.1.155]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 19 ms 21 ms 19 ms 41.193.73.213
4 19 ms 19 ms 18 ms 41.193.73.214
5 19 ms 19 ms 19 ms 41.193.73.220
6 20 ms 20 ms 20 ms 41.193.72.5
7 29 ms 30 ms 43 ms 41.193.119.114
8 30 ms 31 ms 30 ms 41.221.235.134
9 30 ms 29 ms 29 ms 41.221.235.129
10 32 ms 30 ms 30 ms core-01-tjb1-gig-1-1-0-106-xdsl.co.za [41.223.61.49]
11 32 ms 32 ms 33 ms 41.170.19.162
12 35 ms 35 ms 34 ms 41.170.19.161
13 34 ms 33 ms 33 ms 172.18.1.162
14 34 ms 34 ms 34 ms if-ae-7-0.tcore1.jso-johannesburg.as6453.net [41.206.178.29]
15 207 ms 207 ms 206 ms if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
16 206 ms 204 ms 216 ms if-ae-5-90.tcore2.pv9-lisbon.as6453.net [80.231.159.109]
17 208 ms 208 ms 207 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
18 208 ms 206 ms 206 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
19 217 ms 211 ms 207 ms if-ae-2-2.tcore2.sv8-highbridge.as6453.net [80.231.139.1]
20 209 ms 208 ms 207 ms if-ae-11-2.tcore1.l78-london.as6453.net [80.231.139.42]
21 201 ms 200 ms 201 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
22 195 ms 194 ms 200 ms 195.219.83.102
23 * * 513 ms ae-12-3510.ear2.london15.level3.net [4.69.167.142]
24 * * * Request timed out.
25 195 ms 195 ms 196 ms yahoo-inc.ear2.london15.level3.net [212.187.173.178]
26 196 ms 195 ms 195 ms eth1-2.bas1-1-edg.loa.yahoo.com [66.196.68.145]
27 195 ms 196 ms 195 ms r1.ycpi.vip.loa.yahoo.net [217.12.1.155]

Trace complete.

Durban here
 
Afrihost's network status show's green lights across the board. Isolated to DBN, perhaps?
 
My sister moved in to a new place and I helped her with the ADSL setup. Currently a 2 MB line but waiting for Telkom to change it to 4 MB and capped Afrihost account.
What does it mean if the router reports error packets and how can it be fixed?
The router reports something like 40 upstream and 7 downstream error packets.

Also, if a router gives a certain upstream and downstream speed in this case 508 and 2508, why can't I get close to that speeds doing a speed test through a browser?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X