Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
still going strong here in centurion

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 7 ms 7 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 15 ms 11 ms 12 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 11 ms 11 ms 10 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 12 ms 15 ms 10 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 10 ms 10 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 9 ms 9 ms 10 ms cache.google.com [66.8.14.14]

Trace complete.

tracert www.nvidia.com

Tracing route to a1650.g.akamai.net [41.181.158.75]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 9 ms 7 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 9 ms 10 ms 9 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 10 ms 12 ms 10 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 11 ms 17 ms 17 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 9 ms 9 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 10 ms 9 ms 10 ms 41.181.158.75
 
AfriMan said:
I see there's quite a few people still battling with YouTube and streaming. Am I right in saying this is Cape Town users, or are people experiencing the same issue in other parts of SA?

Please PM me traceroutes so I can see where the issue might be. :(
Click to expand...

Cpt

Traceroute where? I've posted here yesterday, I've sent them to support. Didn't get a single response on why and what's going on. Almost 48 hours that it's been like this.
 
kripstoe said:
Cpt

Traceroute where? I've posted here yesterday, I've sent them to support. Didn't get a single response on why and what's going on. Almost 48 hours that it's been like this.
Click to expand...


Cpt

C:\Windows\system32>tracert youtu.be

Tracing route to youtu.be [74.125.233.34]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.1.90
2 8 ms 8 ms 7 ms ************-esr-lo.mtnbusiness.co.za [***********]
3 30 ms 30 ms 31 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
4 10 ms 9 ms 9 ms 41.181.198.188
5 10 ms 10 ms 9 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 29 ms 28 ms 29 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 31 ms 31 ms 31 ms pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]

8 31 ms 33 ms 31 ms 41.181.139.109
9 32 ms 32 ms 32 ms 72.14.194.74
10 33 ms 32 ms 32 ms 64.233.174.21
11 32 ms 38 ms 79 ms jnb01s01-in-f2.1e100.net [74.125.233.34]

Trace complete.
 
PE

traceroute to youtu.be (74.125.233.40), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.744 ms 0.305 ms 0.281 ms
2 105-236-8-129-esr-lo.mtnbusiness.co.za (105.236.8.129) 6.094 ms 6.257 ms 6.148 ms
3 ipc-send-tb-3a.mtnbusiness.net (41.181.53.214) 24.071 ms 24.097 ms 23.905 ms
4 41.181.198.188 (41.181.198.188) 52.359 ms 52.828 ms 51.764 ms
5 compj-cpt-1.mtnns.net (196.44.18.2) 24.940 ms
unc-cpt-1.mtnns.net (196.44.18.8) 24.563 ms
compj-cpt-1.mtnns.net (196.44.18.2) 25.023 ms
6 196.44.31.106 (196.44.31.106) 25.249 ms
ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134) 45.899 ms 45.779 ms
7 pb-ad-1.za--pb-sla-1-a.mtnns.net (196.44.31.128) 74.171 ms
ct-cr-2.za--rb-cr-2.za-a.mtnns.net (196.44.31.30) 99.758 ms
pb-ad-1.za--pb-sla-1-a.mtnns.net (196.44.31.128) 74.327 ms
8 41.181.139.99 (41.181.139.99) 67.658 ms 67.417 ms
41.181.139.109 (41.181.139.109) 66.760 ms
9 72.14.194.74 (72.14.194.74) 57.203 ms 56.799 ms 56.709 ms
10 64.233.174.21 (64.233.174.21) 75.912 ms 75.549 ms 75.832 ms
11 jnb01s01-in-f8.1e100.net (74.125.233.40) 57.080 ms 54.589 ms 57.699 ms
 
4Mbps Business uncapped, near East London

I've tried playing loads of different youtube videos and they all download from different IPs, but I have noticed something. If the videos download from addresses like these, then there's little to no buffering:

173.194.30.146
173.194.30.38
173.194.30.82
173.194.5.73
74.125.105.51
74.125.216.20
74.125.4.20

However, if the videos download from one of these IPs, then they buffer constantly:

66.8.14.15
66.8.14.14
66.8.14.13

Traceroutes:

C:\Windows\system32>tracert 66.8.14.15

Tracing route to cache.google.com [66.8.14.15]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.23.0.254
2 1 ms 1 ms 1 ms 10.1.1.10
3 23 ms 23 ms 26 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
4 78 ms 38 ms 38 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
5 39 ms 39 ms 38 ms 41.181.198.188
6 44 ms 40 ms 40 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 123 ms 123 ms 121 ms rb-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 158 ms 153 ms 151 ms 41.181.180.11
9 119 ms 119 ms 124 ms cache.google.com [66.8.14.15]

Trace complete.

C:\Windows\system32>tracert 66.8.14.14

Tracing route to cache.google.com [66.8.14.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.23.0.254
2 1 ms 1 ms 1 ms 10.1.1.10
3 23 ms 23 ms 22 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
4 40 ms 38 ms 38 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
5 38 ms 40 ms 38 ms 41.181.198.188
6 39 ms 41 ms 40 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 124 ms 123 ms 121 ms rb-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 119 ms 118 ms 120 ms 41.181.180.11
9 141 ms 139 ms 143 ms cache.google.com [66.8.14.14]

Trace complete.

C:\Windows\system32>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.23.0.254
2 1 ms 1 ms 1 ms 10.1.1.10
3 23 ms 24 ms 23 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
4 59 ms 57 ms 56 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 39 ms 42 ms 38 ms 41.181.198.188
6 43 ms 41 ms 43 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 40 ms 41 ms 41 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
8 70 ms 67 ms 67 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
9 64 ms 60 ms 65 ms 196.44.31.97
10 62 ms 69 ms 61 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12]
11 66 ms 68 ms 70 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
12 67 ms 67 ms 66 ms tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.net [196.31.63.146]
13 59 ms 59 ms 58 ms core-router1.jnb2.host-h.net [196.30.213.108]
14 67 ms 66 ms 65 ms core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
15 68 ms 68 ms 66 ms mybroadband.co.za [41.203.21.137]

Trace complete.

C:\Windows\system32>tracert afrihost.com

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

1 <1 ms <1 ms <1 ms 172.23.0.254
2 1 ms 1 ms 1 ms 10.1.1.10
3 22 ms 23 ms 23 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
4 40 ms 39 ms 38 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
5 41 ms 38 ms 38 ms 41.181.198.188
6 39 ms 40 ms 41 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 39 ms 41 ms 39 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
8 62 ms 63 ms 65 ms pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]
9 62 ms 62 ms 62 ms 196.44.31.97
10 128 ms * 116 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12]
11 155 ms 113 ms * tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
12 117 ms * 111 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
13 111 ms 112 ms 114 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Windows\system32>



Here are some speedtests. Jo'burg is really slow... I tested it 3 times.

2747544202.png

2747542742.png

2747545974.png

2747558508.png

2747567216.png

2747563193.png
 
Last edited:
I'm in centurion, latency for gaming is terrible, can't play any of the following games . GW2, Neverwinter, Defiance . Lagging in all of them. Downloading is fine, it's the latency. I believe all those servers are most likely in the USA.
 
Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router [172.25.160.1]
2 10 ms 12 ms 10 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
3 11 ms 12 ms 11 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 11 ms 12 ms 11 ms 41.181.198.188
5 13 ms 13 ms 12 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 12 ms 13 ms 13 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 88 ms * 82 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
8 37 ms 33 ms 34 ms 196.44.31.97
9 84 ms 152 ms 33 ms 196.30.1.53
10 85 ms * 152 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
11 84 ms 83 ms 83 ms tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.net [196.31.63.146]
12 107 ms 105 ms * core-router1.jnb2.host-h.net [196.30.213.108]
13 106 ms * 104 ms core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
14 41 ms 39 ms 37 ms mybroadband.co.za [41.203.21.137]

Trace complete.

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

1 1 ms <1 ms 1 ms router [172.25.160.1]
2 10 ms 10 ms 11 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
3 12 ms 11 ms 11 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 12 ms 12 ms 11 ms 41.181.198.188
5 13 ms 12 ms 12 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 14 ms 12 ms 12 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 106 ms 104 ms * pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]
8 34 ms 33 ms 34 ms 196.44.31.97
9 108 ms 53 ms 34 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12]
10 85 ms 85 ms 86 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
11 85 ms 86 ms * tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
12 33 ms 34 ms 34 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Tracing route to youtube.com [74.125.233.40]
over a maximum of 30 hops:

1 <1 ms 3 ms <1 ms router [172.25.160.1]
2 11 ms 11 ms 11 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
3 13 ms 12 ms 11 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 12 ms 12 ms 11 ms 41.181.198.188
5 344 ms 12 ms 11 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 49 ms 13 ms 12 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 53 ms 53 ms 53 ms pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]
8 33 ms 33 ms 34 ms 41.181.139.109
9 35 ms 37 ms 82 ms 72.14.194.74
10 35 ms 35 ms 35 ms 64.233.174.21
11 35 ms 34 ms 34 ms jnb01s01-in-f8.1e100.net [74.125.233.40]

Trace complete.

Cpt
2747598427.png

Jhb (slow)
2747600003.png

Same results for two days now.
 
I see this thing is only going to get resolved tomorrow ...mid day...somewhere something or someone went faulty ...really good i have a account at mweb even though the isps make turns to go faulty over weekends.
 
Can't open speedtest.....

My PPPoE session keeps dropping but my line stays synced.

I am in Richmond KZN, so I am guessing there is a problem with DBN IPC???
 
Just talking on the phone to MTN's engineers and they are trying to find the cause of the issue. They did confirm yesterday that they have not found any problems on the CTP-JHB link, but they will continue to test and troubleshoot until they find the issue.

We are taking this very seriously. We know that media streaming is a big part of the internet, and we're treating this as very high priority. Please continue to be patient, I promise we're doing everything possible to find the cause :(
 
traceroute to capetown server from centurion, gauteng

notice latency higher than normal and is very erratic, but local JHB pings are great

Tracing route to www.scoopdistribution.com [197.221.2.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 7 ms 7 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 9 ms 10 ms 9 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 81 ms 120 ms 81 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 10 ms 11 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 66 ms 124 ms 73 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 38 ms 39 ms 39 ms core-router1.cpt2.host-h.net [196.40.104.66]
8 41 ms 43 ms 39 ms core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70]
9 39 ms 38 ms 38 ms dedi34.cpt1.host-h.net [197.221.2.134]

Trace complete.
 
AfriMan said:
I see there's quite a few people still battling with YouTube and streaming. Am I right in saying this is Cape Town users, or are people experiencing the same issue in other parts of SA?

Please PM me traceroutes so I can see where the issue might be. :(
Click to expand...

It seems that AH expects their clients to do their work for them - traceroutes here and traceroutes there. Whats the point - surely you believe the complaint. Why keep asking for proof? I have on a couple of occasions been asked for traceroutes from support - just seems like a delaying tactic because there is seldom any follow-up though things do eventually improve only to fail again shortly thereafter. I am near Cape Town and it seems that down here we are getting the 'short end of the stick'!
 
Traceroutes arnt meant for proof, They are meant for finding out on which area of the network there is a problem.

For EG: #11075 by nerf

1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 7 ms 7 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 9 ms 10 ms 9 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 81 ms 120 ms 81 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146] --------- Here we see that there are high pings
5 10 ms 11 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 66 ms 124 ms 73 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 38 ms 39 ms 39 ms core-router1.cpt2.host-h.net [196.40.104.66]
8 41 ms 43 ms 39 ms core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70]
9 39 ms 38 ms 38 ms dedi34.cpt1.host-h.net [197.221.2.134]

That means that between the nodes "ipc-recieve-rb-4a.za.mtnbusiness.net" and "rb-cr-1.za--rb-dca-1.za-a.mtnns.net", there is an issue. It allows the tech dept to see where the issue is and hopefully fix it. By us helping them, it allows them to get a broader idea of where the problem is.

We dont need to help them, but if we dont, it might take longer to fix.
 
Yeah its to find out were the bad spot is....i even went through the ips and pinged them and picked up that there was packet loss on the one ip...this was yesterday...still nothing ...im sure if you guys try that you will find the same ...thats what causes latency...packet loss. So please is it possible that afrihost could please tell us if we give you the ips with packet loss then you should know were the segment is thats faulty???or isnt it that easy???
 
Raysmith said:
It seems that AH expects their clients to do their work for them - traceroutes here and traceroutes there. Whats the point - surely you believe the complaint. Why keep asking for proof? I have on a couple of occasions been asked for traceroutes from support - just seems like a delaying tactic because there is seldom any follow-up though things do eventually improve only to fail again shortly thereafter. I am near Cape Town and it seems that down here we are getting the 'short end of the stick'!
Click to expand...

It's not that we ever disbelieve your complaint. We need to verify what results you are seeing, from your particular line and exchange in order to alleviate the problem. It's impossible to reverse test your connection, so the quickest and best route is to troubleshoot with you, and analyse your test results. Your trace routes and speedtests are invaluable in helping us find the cause of issues. Even when there is a general problem, we still need testing information from individual affected users to know where to start looking.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X