Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
AfriMan said:
This is something we've discussed internally and may possibly be something we could offer in the future if we can determine the right business rules.

The problem now is that because the "product" (i.e. data) is delivered immediately, the payment must clear otherwise we could potentially a large amount of data which my not be paid for in time, and possibly never recovered. Our current volume of unpaid transactions is concerning, so we want to do everything possible to reduce these instances before we look at changing our systems - though I can see what a convenient benefit this would be for many clients. I know I have NO cash left in my account by the time it gets to the end of the month when I would most likely need to top up :(
Click to expand...

Understandable, there are many ways for you to reduce your unpaids, NADEO, same day EFT, etc.

Maybe you can work on a rating system, if a client has been paying regularly for a certain period of months they are allowed to purchase top-ups on postpaid.
 
ant_man said:
Understandable, there are many ways for you to reduce your unpaids, NADEO, same day EFT, etc.

Maybe you can work on a rating system, if a client has been paying regularly for a certain period of months they are allowed to purchase top-ups on postpaid.
Click to expand...

I'm sure it's something we can look into, as AfriMan said, we have had a similar discussion internally around this :)
 
As we know I have the 40Mbps badboy, problem is once you go over that 20Mbps barrier you really don't notice anything anymore. Apart from actual downloads, but browsing and streaming is pretty much the same. Especially from mobile devices.

So I noticed lately people complaining about their capped accounts, then I read their posts and think, bahahaha poor souls I have NO problems.


Actually what happened was, My line was close to a 50% reduction the whole weekend running on 20 - 23Mbps max ( Don't worry it is at full pretty 37.8Mbps now), but point is even thou my line was performing at 50% it still didn't hurt me :P


I just wanted to share my story :)
 
Thor187 said:
As we know I have the 40Mbps badboy, problem is once you go over that 20Mbps barrier you really don't notice anything anymore. Apart from actual downloads, but browsing and streaming is pretty much the same. Especially from mobile devices.

So I noticed lately people complaining about their capped accounts, then I read their posts and think, bahahaha poor souls I have NO problems.


Actually what happened was, My line was close to a 50% reduction the whole weekend running on 20 - 23Mbps max ( Don't worry it is at full pretty 37.8Mbps now), but point is even thou my line was performing at 50% it still didn't hurt me :P


I just wanted to share my story :)
Click to expand...

I can see where you're coming from, I think there's a point of speed where things just open up pretty quickly - maybe that's what you're seeing :)
 
AfriGuy said:
I can see where you're coming from, I think there's a point of speed where things just open up pretty quickly - maybe that's what you're seeing :)
Click to expand...

Pretty much. I am in that point of my life where I don't even notice "slight" 50% reductions on my line anymore. #Lavish :P
 
Yes. Basically your internet is downloading web pages faster than your browser can render them. Guess it is time to upgrade your hardware then?
 
Hi again.

Having massive issues here - linespeed and latency is absolute crud - like IOS update ****e :P

Have logged tickets in clientzone with daily updates for past 4 days with no response - clientzone tools don't help and the livechat fails to load because the connection is so poor.

Please assist as I seem to have run out of support through other means.

Thanks

Last Result:
Download Speed: 132 kbps (16.5 KB/sec transfer rate)
Upload Speed: 432 kbps (54 KB/sec transfer rate)
Latency: 41 ms
1/26/2015, 10:02:47 PM

Last Result:
Download Speed: 69 kbps (8.6 KB/sec transfer rate)
Upload Speed: 385 kbps (48.1 KB/sec transfer rate)
Latency: 35 ms
1/24/2015, 12:12:55 AM

Last Result:
Download Speed: 269 kbps (33.6 KB/sec transfer rate)
Upload Speed: 424 kbps (53 KB/sec transfer rate)
Latency: 44 ms
1/23/2015, 11:51:00 PM

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=35 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=36 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=35 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=32 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=33 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=158 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=159 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=163 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=166 ms



Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms
2 105.236.5.1 12 ms 7 ms
3 41.181.54.8 13 ms 8 ms
4 41.181.198.1 12 ms 14 ms
5 196.44.18.2 13 ms
196.44.31.1 9 ms
6 196.44.31.1 9 ms
196.44.31.6 31 ms
7 196.44.31.6 31 ms
196.44.0.2 34 ms
8 196.44.0.2 31 ms
196.31.220.1 35 ms
9 196.31.220.2 36 ms
196.31.63.2 36 ms
10 196.31.63.2 36 ms
196.30.42.1 31 ms
11 196.30.42.1 34 ms
197.242.144.1 37 ms
12 197.242.144.1 35 ms


traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms
2 105.236.5.1 13 ms 7 ms
3 41.181.184.2 14 ms
41.181.54.8 12 ms
4 196.44.18.2 10 ms
41.181.184.2 14 ms
5 196.44.31.1 159 ms
209.212.111.1 155 ms
6 209.212.99.1 157 ms
216.239.47.2 159 ms
7 72.14.236.2 160 ms
8.8.8.8 168 ms



DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 66.8.14.24
Name: www.google.com
Address: 66.8.14.57
Name: www.google.com
Address: 66.8.14.35
Name: www.google.com
Address: 66.8.14.48
Name: www.google.com
Address: 66.8.14.27
Name: www.google.com
Address: 66.8.14.38
Name: www.google.com
Address: 66.8.14.59
Name: www.google.com
Address: 66.8.14.31
Name: www.google.com
Address: 66.8.14.49
Name: www.google.com
Address: 66.8.14.42
Name: www.google.com
Address: 66.8.14.20
Name: www.google.com
Address: 66.8.14.16
Name: www.google.com
Address: 66.8.14.37
Name: www.google.com
Address: 66.8.14.53
Name: www.google.com
Address: 66.8.14.46
Name: www.google.com
Address: 66.8.14.26


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
AfriMan said:
Looking at these latency spikes, it seems like it starts at the exchange. You should usually be around 10ms on the second hop and 28ms+ is dangerously close to horrible. I see intermittent jumps in latency throughout the trace and I think this must be related to the exchange or the line :(
Click to expand...

Hi Afriman, as promised below is another tracert to the CS:GO Intoxicated JHB servers. Identical to initial post I made about this, this tracert shows no involvement from the local exchange with a clear problem somewhere between hop 6 and 8 as per my other posts.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XYZ>tracert 41.0.11.164

Tracing route to 41.0.11.164 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 10.0.0.2
2 10 ms 6 ms 7 ms 105-236-249-65-esr-lo.mtnbusiness.co.za [105.236
.249.65]
3 9 ms 8 ms 10 ms 41.181.221.254
4 8 ms 8 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 9 ms 9 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 9 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.14
3]
7 * * * Request timed out.
8 175 ms 166 ms 163 ms 196.43.25.205
9 176 ms 175 ms 174 ms 196.43.39.18
10 178 ms 178 ms 176 ms vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
11 186 ms 212 ms 186 ms 41.0.0.33
12 184 ms 185 ms 178 ms 41.0.0.33
13 176 ms 180 ms 181 ms 41.0.11.164

Trace complete.

Hop 6 is on MTN's network in Cape Town. Hop 8 is Telkom's network in Gauteng. Whatever's happening in between Cape Town and GP clearly isn't correct in this case.

For comparison's sake, below is an additional tracert to the same server at 41.0.11.164 using a competing ISP's product:

C:\Users\XYZ>tracert 41.0.11.164

Tracing route to 41.0.11.164 over a maximum of 30 hops

1 6 ms 7 ms 7 ms 196-210-118-1.dynamic.isadsl.co.za [196.210.118.
1]
2 10 ms 9 ms 8 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
3 8 ms 11 ms 8 ms 196.35.115.136
4 8 ms 8 ms 9 ms 168.209.2.13
5 8 ms 8 ms 9 ms 168.209.6.131
6 30 ms 31 ms 30 ms vodacom.cinx.net.za [196.223.22.73]
7 28 ms 29 ms 28 ms 41.0.0.33
8 28 ms 28 ms 28 ms 41.0.0.33
9 28 ms 28 ms 28 ms 41.0.11.164

Trace complete.
 
Last edited:
DeathStrike said:
Yes. Basically your internet is downloading web pages faster than your browser can render them. Guess it is time to upgrade your hardware then?
Click to expand...

I highly doubt 16Gb 2133Mhz Ram and a 4.7Ghz 8 core FX-9590 CPU is the problem here....
 
Akurei said:
Hi again.

Having massive issues here - linespeed and latency is absolute crud - like IOS update ****e :P

Have logged tickets in clientzone with daily updates for past 4 days with no response - clientzone tools don't help and the livechat fails to load because the connection is so poor.

Please assist as I seem to have run out of support through other means.

Thanks

Last Result:
Download Speed: 132 kbps (16.5 KB/sec transfer rate)
Upload Speed: 432 kbps (54 KB/sec transfer rate)
Latency: 41 ms
1/26/2015, 10:02:47 PM

Last Result:
Download Speed: 69 kbps (8.6 KB/sec transfer rate)
Upload Speed: 385 kbps (48.1 KB/sec transfer rate)
Latency: 35 ms
1/24/2015, 12:12:55 AM

Last Result:
Download Speed: 269 kbps (33.6 KB/sec transfer rate)
Upload Speed: 424 kbps (53 KB/sec transfer rate)
Latency: 44 ms
1/23/2015, 11:51:00 PM

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=35 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=36 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=35 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=32 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=33 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=158 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=159 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=163 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=166 ms



Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms
2 105.236.5.1 12 ms 7 ms
3 41.181.54.8 13 ms 8 ms
4 41.181.198.1 12 ms 14 ms
5 196.44.18.2 13 ms
196.44.31.1 9 ms
6 196.44.31.1 9 ms
196.44.31.6 31 ms
7 196.44.31.6 31 ms
196.44.0.2 34 ms
8 196.44.0.2 31 ms
196.31.220.1 35 ms
9 196.31.220.2 36 ms
196.31.63.2 36 ms
10 196.31.63.2 36 ms
196.30.42.1 31 ms
11 196.30.42.1 34 ms
197.242.144.1 37 ms
12 197.242.144.1 35 ms


traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms
2 105.236.5.1 13 ms 7 ms
3 41.181.184.2 14 ms
41.181.54.8 12 ms
4 196.44.18.2 10 ms
41.181.184.2 14 ms
5 196.44.31.1 159 ms
209.212.111.1 155 ms
6 209.212.99.1 157 ms
216.239.47.2 159 ms
7 72.14.236.2 160 ms
8.8.8.8 168 ms



DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 66.8.14.24
Name: www.google.com
Address: 66.8.14.57
Name: www.google.com
Address: 66.8.14.35
Name: www.google.com
Address: 66.8.14.48
Name: www.google.com
Address: 66.8.14.27
Name: www.google.com
Address: 66.8.14.38
Name: www.google.com
Address: 66.8.14.59
Name: www.google.com
Address: 66.8.14.31
Name: www.google.com
Address: 66.8.14.49
Name: www.google.com
Address: 66.8.14.42
Name: www.google.com
Address: 66.8.14.20
Name: www.google.com
Address: 66.8.14.16
Name: www.google.com
Address: 66.8.14.37
Name: www.google.com
Address: 66.8.14.53
Name: www.google.com
Address: 66.8.14.46
Name: www.google.com
Address: 66.8.14.26


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

Everything seems normal in the tests but I can definitely see the throughput on the line is very poor. We'll need to do some more specific troubleshooting to see why you may be having these problems like swopping accounts, etc.

Please PM me and let's see what we can do :(
 
FuLL_MeT4L said:
Hi Afriman, as promised below is another tracert to the CS:GO Intoxicated JHB servers. Identical to initial post I made about this, this tracert shows no involvement from the local exchange with a clear problem somewhere between hop 6 and 8 as per my other posts.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XYZ>tracert 41.0.11.164

Tracing route to 41.0.11.164 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 10.0.0.2
2 10 ms 6 ms 7 ms 105-236-249-65-esr-lo.mtnbusiness.co.za [105.236
.249.65]
3 9 ms 8 ms 10 ms 41.181.221.254
4 8 ms 8 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 9 ms 9 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 9 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.14
3]
7 * * * Request timed out.
8 175 ms 166 ms 163 ms 196.43.25.205
9 176 ms 175 ms 174 ms 196.43.39.18
10 178 ms 178 ms 176 ms vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
11 186 ms 212 ms 186 ms 41.0.0.33
12 184 ms 185 ms 178 ms 41.0.0.33
13 176 ms 180 ms 181 ms 41.0.11.164

Trace complete.

Hop 6 is on MTN's network in Cape Town. Hop 8 is Telkom's network in Gauteng. Whatever's happening in between Cape Town and GP clearly isn't correct in this case.

For comparison's sake, below is an additional tracert to the same server at 41.0.11.164 using a competing ISP's product:

C:\Users\XYZ>tracert 41.0.11.164

Tracing route to 41.0.11.164 over a maximum of 30 hops

1 6 ms 7 ms 7 ms 196-210-118-1.dynamic.isadsl.co.za [196.210.118.
1]
2 10 ms 9 ms 8 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
3 8 ms 11 ms 8 ms 196.35.115.136
4 8 ms 8 ms 9 ms 168.209.2.13
5 8 ms 8 ms 9 ms 168.209.6.131
6 30 ms 31 ms 30 ms vodacom.cinx.net.za [196.223.22.73]
7 28 ms 29 ms 28 ms 41.0.0.33
8 28 ms 28 ms 28 ms 41.0.0.33
9 28 ms 28 ms 28 ms 41.0.11.164

Trace complete.
Click to expand...

Can you see what DNS settings are pushed to your router when you connect to our DSL?
 
ScottulusMaximus said:
From this thread my line is too kark for 10meg, can you guys do options for something in between 4 and 10?
Click to expand...

We're not looking at introducing middle packages for regular Uncapped products, since there is not much of a jump to go from 4Mbps to 10Mbps. But we do have them on Business due to the higher cost of the Business packages.
 
AfriMan said:
Can you see what DNS settings are pushed to your router when you connect to our DSL?
Click to expand...

Will see what's what with DNS this evening and let you know! Can't remote in as I turned my PC off for load-shedding, hehe.
 
FuLL_MeT4L said:
Will see what's what with DNS this evening and let you know! Can't remote in as I turned my PC off for load-shedding, hehe.
Click to expand...

I hate Eskom. I also turn my pc off due to load shedding, but sometimes whilst at work I desperately needs something then I remember Eskom is in charge of my life.
 
Thor187 said:
I hate Eskom. I also turn my pc off due to load shedding, but sometimes whilst at work I desperately needs something then I remember Eskom is in charge of my life.
Click to expand...

I shut down at 09:50 as the schedule showed Hout Bay as 10AM.

At 10:20 the power was still on and the Eskom web Page said, "Not Load Shedding" so I powered everything back up, all 5 machines.

10:35 Blackout. AAARG, if they are not publishing the correct info can they be held responsible for blown equipment?

2 hours after it came back I was still waiting for the Local exchange to stabilize and getting intermittent ADSL.
 
epic torrents running at 48kb/s

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\L3vi>tracert google.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 46 ms 32 ms 105-236-240-129-esr-lo.mtnbusiness.co.za [105.23
6.240.129]
3 24 ms 37 ms 24 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
4 21 ms 45 ms 64 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
5 9 ms 8 ms 8 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 152 ms 156 ms 153 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]

7 161 ms 169 ms 165 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
8 251 ms 164 ms 163 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
9 153 ms 151 ms 166 ms 209.85.255.78
10 163 ms 153 ms 151 ms 209.85.245.2
11 170 ms 205 ms 194 ms 64.233.174.82
12 199 ms 165 ms 234 ms 216.239.51.119
13 * * * Request timed out.
14 160 ms 165 ms 180 ms 74.125.133.102

Trace complete.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X