Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Bryn said:
No. Youtube and browsing is fine. Latency is probably higher due to torrents running. Things might be fine. I think I'm just having bad luck with my downloads.
Click to expand...

If the connection does act up at any point, please let me know!
 
So I have a Telkom guest account which I am trying out for the day - wow. Difference is night and day when comparing youtube performance.
Stats for nerds:
Connection speed around 1600 kbps on the Telkom test account and around 600 kbps on my AH account.
Same video set to 720p on both occasions.
The video also does not buffer on the Telkom test account where it does on the AH account.
 
Dianysis said:
So I have a Telkom guest account which I am trying out for the day - wow. Difference is night and day when comparing youtube performance.
Stats for nerds:
Connection speed around 1600 kbps on the Telkom test account and around 600 kbps on my AH account.
Same video set to 720p on both occasions.
The video also does not buffer on the Telkom test account where it does on the AH account.
Click to expand...

That is interesting... I just checked and the network issue on your Exchange is definitely still in affect.

Would be able to post a traceroute to Afrihost.com with both accounts? I want to see if it goes through the same cards on the Exchange.
 
AfriGenie said:
That is interesting... I just checked and the network issue on your Exchange is definitely still in affect.

Would be able to post a traceroute to Afrihost.com with both accounts? I want to see if it goes through the same cards on the Exchange.
Click to expand...

AH:

tracert www.afrihost.com

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.0.1
2 21 ms 20 ms 22 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 59 ms 30 ms 31 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 51 ms 37 ms 39 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 50 ms 29 ms 31 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 28 ms 76 ms 41 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 30 ms 23 ms 30 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Telkom:

tracert www.afrihost.com

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 20 ms 20 ms 21 ms dsl-165-145-72-01.telkomadsl.co.za [165.145.72.1]
3 23 ms 23 ms 24 ms 196.43.31.226
4 22 ms 22 ms 36 ms 196.43.31.229
5 24 ms 24 ms * rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
6 22 ms 22 ms 22 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [196.43.25.138]
7 24 ms 25 ms 28 ms mtn-gw.telkom-ipnet.co.za [196.25.58.18]
8 25 ms 31 ms 36 ms 41.181.139.108
9 25 ms 25 ms 25 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
10 24 ms 23 ms 24 ms jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
11 28 ms 27 ms 29 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
Dianysis said:
AH:

tracert www.afrihost.com

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.0.1
2 21 ms 20 ms 22 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.1]
3 59 ms 30 ms 31 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 51 ms 37 ms 39 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 50 ms 29 ms 31 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 28 ms 76 ms 41 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 30 ms 23 ms 30 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Telkom:

tracert www.afrihost.com

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 20 ms 20 ms 21 ms dsl-165-145-72-01.telkomadsl.co.za [165.145.72.1]
3 23 ms 23 ms 24 ms 196.43.31.226
4 22 ms 22 ms 36 ms 196.43.31.229
5 24 ms 24 ms * rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
6 22 ms 22 ms 22 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [196.43.25.138]
7 24 ms 25 ms 28 ms mtn-gw.telkom-ipnet.co.za [196.25.58.18]
8 25 ms 31 ms 36 ms 41.181.139.108
9 25 ms 25 ms 25 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
10 24 ms 23 ms 24 ms jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
11 28 ms 27 ms 29 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
Click to expand...

Thanks! So it does use different network cards on the Exchange itself.
 
Dianysis said:
Will be doing tests tonight to compare - speeds always down between 6 and 11 every night. Hopefully can shed some light.
Click to expand...

SAIX-based, IS-based and MTN-based ADSL connections generally each have a different network card on the Exchange, so it is possible for congestion to affect some of those worse than others.

Testing during peak-times will actually be perfect as we'll be able to isolate the affected area by comparing the two differen traceroutes.
 
AfriGenie said:
SAIX-based, IS-based and MTN-based ADSL connections generally each have a different network card on the Exchange, so it is possible for congestion to affect some of those worse than others.

Testing during peak-times will actually be perfect as we'll be able to isolate the affected area by comparing the two differen traceroutes.
Click to expand...

Ok cool.
Will post results tonight.
 
Seeing some high latency in Cape Town

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

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 10 ms 6 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 121 ms 121 ms 116 ms 41.181.221.254
4 98 ms 98 ms 100 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 106 ms 107 ms 104 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 120 ms 92 ms 96 ms 196.44.31.106
7 127 ms 131 ms 130 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 90 ms 91 ms 93 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
9 104 ms 105 ms 107 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 115 ms 113 ms 114 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 135 ms 130 ms 137 ms 196.28.178.66
12 126 ms 121 ms 120 ms cte-core-sw2.vwol.net [196.41.144.35]
13 123 ms 123 ms 124 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
On Telkom all seems normal

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

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms wblv-ip-bng-1.south.dsl.telkomsa.net [105.224.220.1]
3 8 ms 7 ms 7 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 8 ms 7 ms 7 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 7 ms 8 ms 8 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 8 ms 7 ms 8 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 8 ms 8 ms 7 ms mweb.ct1.napafrica.net [196.10.140.15]
8 32 ms 31 ms 31 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
9 31 ms 34 ms 28 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 32 ms 28 ms 28 ms 196.28.178.66
11 29 ms 29 ms 29 ms cte-core-sw2.vwol.net [196.41.144.35]
12 28 ms 28 ms 28 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
I have the same latency issue (CT) Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 11 ms 11 ms 105-236-5-193-esr-lo.mtnbusiness.co.za [105.236.
5.193]
3 95 ms 91 ms 92 ms 41.181.51.182
4 88 ms 108 ms 83 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 98 ms 104 ms 97 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 99 ms 96 ms 94 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

7 122 ms 80 ms 81 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
8 64 ms 66 ms 67 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.

Been doing this for over a month now.
 
standerr said:
Seeing some high latency in Cape Town

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

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 10 ms 6 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 121 ms 121 ms 116 ms 41.181.221.254
4 98 ms 98 ms 100 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 106 ms 107 ms 104 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 120 ms 92 ms 96 ms 196.44.31.106
7 127 ms 131 ms 130 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 90 ms 91 ms 93 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
9 104 ms 105 ms 107 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
10 115 ms 113 ms 114 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 135 ms 130 ms 137 ms 196.28.178.66
12 126 ms 121 ms 120 ms cte-core-sw2.vwol.net [196.41.144.35]
13 123 ms 123 ms 124 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

standerr said:
On Telkom all seems normal

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

1 <1 ms <1 ms <1 ms wall.exa [10.0.0.254]
2 6 ms 6 ms 6 ms wblv-ip-bng-1.south.dsl.telkomsa.net [105.224.220.1]
3 8 ms 7 ms 7 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 8 ms 7 ms 7 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 7 ms 8 ms 8 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 8 ms 7 ms 8 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 8 ms 8 ms 7 ms mweb.ct1.napafrica.net [196.10.140.15]
8 32 ms 31 ms 31 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
9 31 ms 34 ms 28 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 32 ms 28 ms 28 ms 196.28.178.66
11 29 ms 29 ms 29 ms cte-core-sw2.vwol.net [196.41.144.35]
12 28 ms 28 ms 28 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Definitely off with that traceroute, I'm assuming you are in the South? Our Team is still checking why there appears to be a latency spike, should know why this is happening shortly.
 
AfriGenie said:
Definitely off with that traceroute, I'm assuming you are in the South? Our Team is still checking why there appears to be a latency spike, should know why this is happening shortly.
Click to expand...

Could someone give me feedback? This has been going on for 7 freaking months now!
 
Hummercellc said:
Could someone give me feedback? This has been going on for 7 freaking months now!
Click to expand...

At the moment there isn't any new information on your Exchange, the network card that the MTN-based network connects to still needs to be replaced, Telkom and MTN are unable to lock your routing at the Exchange to use the alternate working network card on the Exchange. :(
 
AfriGenie said:
At the moment there isn't any new information on your Exchange, the network card that the MTN-based network connects to still needs to be replaced, Telkom and MTN are unable to lock your routing at the Exchange to use the alternate working network card on the Exchange. :(
Click to expand...

I can not believe it takes so long to fix something so simple, poor poor show from everyone involved. This is just utter horse *
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X