Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
So latency is through the roof tonight, local 470ms minimum, correlates with everyone above.

Would love to know what the exact issue is though?
How is it being fixed and what will stop it from happening again?

I'd like to throw in something positive... the past week my international latency has improved from an average of 230-250ms over the last few months to below 200ms on EU servers.

I'd like to commend Afrihost on improving network performance, but damn I wish Telkom could keep the infrastructure from falling apart when you do so much as shake a stick at it. And why on the start to the weekend...
 
datafreak said:
So latency is through the roof tonight, local 470ms minimum, correlates with everyone above.

Would love to know what the exact issue is though?
How is it being fixed and what will stop it from happening again?

I'd like to throw in something positive... the past week my international latency has improved from an average of 230-250ms over the last few months to below 200ms on EU servers.

I'd like to commend Afrihost on improving network performance, but damn I wish Telkom could keep the infrastructure from falling apart when you do so much as shake a stick at it. And why on the start to the weekend...
Click to expand...
It can only be some sort of hardware failure at telkom side.
What can be done about it-- nothing, it is telkom hardware and the isp is at there mercy to get it fixed.

By the length of the event it must be something major that got broken.
 
UnholyMunk said:
I'm having a weird situation here in Durban, and I'm wondering if anyone else is having the same issue? When I do a speedtest to MTN Joburg, the pings are faster than MTN Durban?!?!? Am I the only one experiencing this? Surely wit the new IPC I should get faster pings to anywhere in Durban than Johannesburg? :/

@Afriman - Are you aware of this?
Click to expand...

I'm in Pietermaritzburg and have the same problem and also being trying to get an answer to why Jhb is better than Dbn. Doesn't make sense if Dbn ipc is live.
Also streaming video last night was impossible and lag on Fifa Xbox live was unplayable. All round disapointment.
 
Does anyone in the Durban area have improved latency since the Durban IPC went live?
 
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
 
Things have improved but still not in the clear, they must have done some sort of temp work around solution.

This was a test moments before the problem started.
Tracing route to webafrica.co.za [196.220.58.66]
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 6 ms 6 ms 6 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 6 ms 5 ms 6 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 7 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 6 ms 6 ms 6 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 7 ms 6 ms 7 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 7 ms 6 ms 6 ms 196.43.25.205
9 8 ms 7 ms 7 ms 196.43.51.26
10 9 ms 8 ms 8 ms wnls-cr1-vl-101.wa.co.za [196.220.59.225]
11 8 ms 8 ms 8 ms wnls-hr2-gi-8-13.wa.co.za [41.185.1.34]
12 9 ms 8 ms 9 ms 196.220.58.66

Trace complete.


This is the test this morning.
Tracing route to webafrica.co.za [196.220.58.66]
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 28 ms 28 ms 27 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 28 ms * * tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 6 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 6 ms 6 ms 6 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 7 ms 6 ms 5 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 32 ms 32 ms 32 ms 196.43.25.205
9 29 ms 29 ms 28 ms 196.43.51.26
10 34 ms 33 ms 34 ms wnls-cr1-vl-102.wa.co.za [196.220.59.229]
11 88 ms 88 ms 88 ms wnls-hr1-gi-8-13.wa.co.za [41.185.1.18]
12 34 ms 34 ms 34 ms 196.220.58.66

Trace complete.

Tracing route to webafrica.co.za [196.220.58.66]
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 38 ms 28 ms 29 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 28 ms 28 ms 27 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 7 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 59 ms 99 ms 185 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 6 ms 6 ms 6 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 33 ms 32 ms 32 ms 196.43.25.205
9 30 ms 29 ms 29 ms 196.43.51.26
10 34 ms 34 ms 34 ms wnls-cr1-vl-102.wa.co.za [196.220.59.229]
11 88 ms 88 ms 88 ms wnls-hr1-gi-8-13.wa.co.za [41.185.1.18]
12 34 ms 34 ms 34 ms 196.220.58.66

Trace complete.
 
Last edited:
it is not good for me, 10meg line, in cape town and test to mweb, speed should be 7-8Mb/s and ping should be 7-10ms



and the problem has escalated again now.

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 6 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 448 ms 449 ms 450 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
4 445 ms 444 ms 444 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 445 ms 447 ms 443 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 449 ms 442 ms 444 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
7 445 ms 446 ms 446 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 * 445 ms 446 ms postfix.wipronet.co.za [196.22.161.133]
9 453 ms 451 ms 456 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]
10 455 ms 452 ms 451 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
11 453 ms 452 ms 488 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
12 437 ms 438 ms 438 ms cte-core-sw2.vwol.net [196.41.144.35]
13 407 ms 34 ms 38 ms www.mweb.co.za [196.2.63.110]

Trace complete.

and 1 minute later, it is is obvious they still sorting out this mess as you can see the route changing at HOP 3

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 5 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 28 ms 28 ms 28 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 28 ms 28 ms 29 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 90 ms 87 ms 86 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 7 ms 7 ms 7 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 34 ms 32 ms 32 ms 196.44.0.74
8 87 ms 87 ms 87 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 90 ms 90 ms 91 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 30 ms 29 ms 29 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 88 ms 87 ms 87 ms 196.28.178.66
12 88 ms 87 ms 87 ms cte-core-sw2.vwol.net [196.41.144.35]
13 88 ms 88 ms 88 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Last edited:
al4bb said:
Does anyone in the Durban area have improved latency since the Durban IPC went live?
Click to expand...

Slight improvement in local latency form 40 to 37ms international much the same 220+ms.
 
Test Date: Mar 9, 2013 11:10:24 AM
Connection Type: Wifi
Server: Cape Town
Download: 3.48 Mbps
Upload: 0.67 Mbps
Ping: 19 ms
 
UnholyMunk said:
I'm having a weird situation here in Durban, and I'm wondering if anyone else is having the same issue? When I do a speedtest to MTN Joburg, the pings are faster than MTN Durban?!?!? Am I the only one experiencing this? Surely wit the new IPC I should get faster pings to anywhere in Durban than Johannesburg? :/

@Afriman - Are you aware of this?
Click to expand...

Same. Speednet ping to MTN Durban 40ms (same as pre IPC) ping to Neotel Jhb 23ms...

Speednet map location defaults to JHB, all Jhb servers yield 20+ms while all Durban server yield 40+ms...
 
Last edited:
And immediately after those good tests, back to horrendous performance...

Test Date: Mar 9, 2013 11:18:09 AM
Connection Type: Wifi
Server: Cape Town
Download: 0.30 Mbps
Upload: 0.64 Mbps
Ping: 301 ms
 
the problem is not resolved it is back, latency increased next trace routing via Johannesburg again.

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 176 ms 178 ms 169 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 186 ms 167 ms 186 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 231 ms 158 ms 157 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 132 ms 131 ms 132 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 131 ms 133 ms 143 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 191 ms 192 ms 164 ms 196.44.0.74
8 187 ms 205 ms 205 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 210 ms 211 ms 216 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 230 ms 221 ms 211 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 170 ms 171 ms 175 ms 196.28.178.66
12 207 ms 200 ms 186 ms cte-core-sw2.vwol.net [196.41.144.35]
13 200 ms 212 ms 220 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 5 ms 5 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 65 ms 65 ms 63 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
4 63 ms * 62 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 64 ms 63 ms 64 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 64 ms 62 ms 63 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
7 * * 64 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 62 ms 63 ms 63 ms postfix.wipronet.co.za [196.22.161.133]
9 66 ms 67 ms 66 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]
10 68 ms * 68 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
11 69 ms 65 ms * TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
12 56 ms 53 ms 53 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
13 55 ms 57 ms 56 ms 196.28.178.66
14 73 ms 73 ms 73 ms cte-core-sw2.vwol.net [196.41.144.35]
15 85 ms 85 ms 85 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
moments later the internet dies and then comes back again

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 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * 53 ms 53 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
7 54 ms 54 ms 53 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 53 ms 53 ms 52 ms postfix.wipronet.co.za [196.22.161.133]
9 67 ms 66 ms 65 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]
10 67 ms 69 ms 66 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
11 68 ms 66 ms 66 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
12 54 ms 53 ms 53 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
13 53 ms 52 ms 52 ms 196.28.178.66
14 55 ms 55 ms 56 ms cte-core-sw2.vwol.net [196.41.144.35]
15 * 65 ms 63 ms www.mweb.co.za [196.2.63.110]

Trace complete.

And Broken again,

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 5 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 439 ms 440 ms 440 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
4 440 ms 487 ms 439 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 444 ms 512 ms * jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 443 ms 442 ms 442 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
7 442 ms 442 ms 443 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 438 ms 438 ms 437 ms postfix.wipronet.co.za [196.22.161.133]
9 443 ms 443 ms 445 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]
10 440 ms 443 ms 444 ms tengig0-7-0-0.vic-p-2.mweb.co.za [197.84.4.36]
11 444 ms 442 ms 443 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
12 430 ms 431 ms 433 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
13 429 ms 428 ms 429 ms 196.28.178.66
14 429 ms 430 ms 432 ms cte-core-sw2.vwol.net [196.41.144.35]
15 441 ms 443 ms 444 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Last edited:
Yep, it's k@k again. And since it's the weekend I have a fear that all the telclowns are sitting at home, braaiing. So another weekend without usable interwebz. My hope ... my very unrealistic hope is that my exchange will come out as brandspanking shiny new 20MB vdsl enabled after this has cleared up. :erm:
 
HermanTheGerman said:
Yep, it's k@k again. And since it's the weekend I have a fear that all the telclowns are sitting at home, braaiing. So another weekend without usable interwebz. My hope ... my very unrealistic hope is that my exchange will come out as brandspanking shiny new 20MB vdsl enabled after this has cleared up. :erm:
Click to expand...

hahahaha you have high hopes, but hey there is nothing wrong to dream, maybe one day that dream becomes reality :)
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X