Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
ClintonExsteen said:
PURE INTERNET JOY - this is a much better reflection of a 4mb line after the telkom issues yesterday... lets hope it stays...

Test conducted on 09 March 2013 12:59:59 AM SAST
Download Speed: 3386 kbps (423.3 KB/sec transfer rate)
Upload Speed: 398 kbps (49.8 KB/sec transfer rate)
Latency: 168 ms

Test conducted on 09 March 2013 7:07:22 AM SAST
Download Speed: 3372 kbps (421.5 KB/sec transfer rate)
Upload Speed: 397 kbps (49.6 KB/sec transfer rate)
Latency: 171 ms
Click to expand...

oh hell, broken all over again...
Test conducted on 09 March 2013 13:22
Download Speed: 92 kbps (11.5 KB/sec transfer rate)
Upload Speed: 406 kbps (50.8 KB/sec transfer rate)
Latency: 620 ms
 
I duno what the problem is though. My router is showing its connected, but then when im watching a live stream or even a youtube video, it just disconnects. PINGs are through the roof so gaming is not going to happen, cant do work as im unable to hold a stable connection, so what now afrihost? where to from here.
 
Lostears said:
I duno what the problem is though. My router is showing its connected, but then when im watching a live stream or even a youtube video, it just disconnects. PINGs are through the roof so gaming is not going to happen, cant do work as im unable to hold a stable connection, so what now afrihost? where to from here.
Click to expand...

Well the latency shoots up every few minutes, then it is either automatic or manual switching and we get re-routed, then few minutes later it switches again and we re-routed back via cape town IPC, and this is on going the whole time.

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 4 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 448 ms 450 ms 448 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
4 490 ms 446 ms 469 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 455 ms 448 ms 446 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 * 446 ms 447 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
7 449 ms 449 ms 445 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 444 ms 441 ms 441 ms postfix.wipronet.co.za [196.22.161.133]
9 451 ms 449 ms 447 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]
10 445 ms 448 ms 449 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
11 451 ms 447 ms 450 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
12 435 ms 436 ms 437 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
13 437 ms 434 ms 432 ms 196.28.178.66
14 436 ms 433 ms 432 ms cte-core-sw2.vwol.net [196.41.144.35]
15 * 444 ms * www.mweb.co.za [196.2.63.110]
16 444 ms 445 ms * www.mweb.co.za [196.2.63.110]
17 442 ms 443 ms 442 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 235 ms 234 ms 227 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 262 ms 230 ms 216 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 164 ms 163 ms 158 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 241 ms 192 ms 187 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 218 ms 251 ms 270 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 226 ms 205 ms 196 ms 196.44.0.74
8 170 ms 162 ms 165 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 190 ms 205 ms 201 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 169 ms 159 ms 184 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 * * 15 ms 196.28.178.66
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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 * 53 ms 53 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 8 ms 7 ms 8 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 62 ms 57 ms 55 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 12 ms 10 ms 15 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 7 ms 6 ms 6 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 9 ms 7 ms 7 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 33 ms 33 ms 41 ms 196.44.0.74
8 19 ms 17 ms 14 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 43 ms 38 ms 39 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 74 ms 76 ms 70 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 20 ms 16 ms 15 ms 196.28.178.66
12 8 ms 7 ms 7 ms cte-core-sw2.vwol.net [196.41.144.35]
13 8 ms 8 ms 8 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Last edited:
So not even two weeks of the new Afrihost IPC in Cape Town and we haven't managed three straight days without some kind of major service degradation, and now, for all intents and purposes it would appear that not only is there no IPC again, but we're all routing via JHB and stuck at virtually dial up speeds and this has now been going on for almost 24hrs. Think it's time to call it a day on Afrihost.
 
Seems to be OK at the moment. Thinking of creating a website to show "days without internet issues". Should be interesting. :)
 
Oh wait... broken again... :banghead:

2561450239.png


Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms router [172.25.160.1]
2 10 ms 11 ms 10 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
3 105 ms 120 ms 106 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 107 ms 113 ms 110 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 137 ms 113 ms 115 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 120 ms 119 ms 121 ms 41.181.139.109
7 * 139 ms 141 ms 72.14.194.74
8 300 ms 308 ms 313 ms 72.14.232.102
9 326 ms 328 ms 326 ms 209.85.253.10
10 340 ms 340 ms * 72.14.232.76
11 363 ms 363 ms 363 ms 209.85.254.116
12 * * * Request timed out.
13 408 ms 409 ms 409 ms google-public-dns-a.google.com [8.8.8.8]
Click to expand...
 
Last edited:
Afrihost update High Impact
Opened: 13:52 Sat, March 09, 2013

We are receiving multiple reports of slow throughput on ADSL and increased latency and packet loss for Cape Town clients, and some clients routing via Cape Town in the Southern Region. We have not confirmed if this is related to yesterday’s Telkom issue, we are investigating in conjunction with Telkom and MTN. We will update clients as soon as we have more information. We sincerely apologise for the inconvenience and poor internet experienced by affected clients.

ADSL clients in other regions should not be affected by the issues in the Southern region.
 
I don't have an uncapped package with Afrihost, but have received a SMS stating that the Cape Town Issue has been resolved, but has resurfaced again and the fault has been escalated to Telkom/SAIX.
 
Spamhater said:
Afrihost update High Impact
Opened: 13:52 Sat, March 09, 2013

We are receiving multiple reports of slow throughput on ADSL and increased latency and packet loss for Cape Town clients, and some clients routing via Cape Town in the Southern Region. We have not confirmed if this is related to yesterday’s Telkom issue, we are investigating in conjunction with Telkom and MTN. We will update clients as soon as we have more information. We sincerely apologise for the inconvenience and poor internet experienced by affected clients.

ADSL clients in other regions should not be affected by the issues in the Southern region.
Click to expand...

Saw that. It's a bit of an understatement...

2561479502.png


Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router [172.25.160.1]
2 10 ms 10 ms 10 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * 190 ms 196.25.191.146
6 * 73 ms 73 ms 41.181.139.109
7 72 ms 86 ms 74 ms 72.14.194.74
8 259 ms * 219 ms 72.14.232.102
9 * * * Request timed out.
10 237 ms 223 ms 222 ms 72.14.232.76
11 224 ms 223 ms 257 ms 209.85.254.114
12 * * * Request timed out.
13 280 ms 280 ms 281 ms google-public-dns-a.google.com [8.8.8.8]
Click to expand...
 
And the Internet is almost completely unusable. Most pages won't even open. I remember dial up being more effective
 
Hi Guys

It looks as though there is something similar to yesterday's issue happening. It seems to be on Telkom's side of the IPC and their people are working on this.

Performance may feel worse than yesterday, as we have not used alternate routing at this stage. The problem is intermittent so we're still hopeful it can be fixed in good time. If we don't see reasonable progress soon, then we will have to consider alternatives.

I'll let everyone know as soon as I have more information on this :(
 
RoMark said:
I don't have an uncapped package with Afrihost, but have received a SMS stating that the Cape Town Issue has been resolved, but has resurfaced again and the fault has been escalated to Telkom/SAIX.
Click to expand...

The issue is not limited to Uncapped, but it seems to affect clients intermittently
 
basically dead for me, webafrica is working, strange that it is also going through cape town and is unaffected :wtf:
 
garp said:
So not even two weeks of the new Afrihost IPC in Cape Town and we haven't managed three straight days without some kind of major service degradation, and now, for all intents and purposes it would appear that not only is there no IPC again, but we're all routing via JHB and stuck at virtually dial up speeds and this has now been going on for almost 24hrs. Think it's time to call it a day on Afrihost.
Click to expand...

I think that a little unfair though. We had a few issues in Feb when the IPC went live, and since then performance reports have been great up until yesterday. That's definitely more than 3 days. While we've had some hosting issues, ADSL was not any time affected, as far as I recall :(
 
Pretoria:

Had full line speed over torrent traffic the last week up until three days ago then it went belly up, very slow 1-10kB/s with intermittent spikes of 80kB/s or so.

AfriMan, is this to do with the relaxed week-long shaping policies or something, has that now been reset, or has it only now been running.

When I first got connected torrents ran slow until midnight hours, then a week or two ago i started seeing full line speed on torrent traffic any time of day, now I seem to be getting the absolute minimum speeds on torrent traffic irrespective of time of day.

Other traffic is still normal, youtube plays smooth, steam downloading is fullspeed, direct download as well
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X