Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Was running fine until 12-10pm. Then just died again....

Line back again after rebooting three times. Did get feedback:

Hi there Ryan Trust you are well After running a test on your line 012******* I saw that the ATUC Attenuation rate on your line was a bit to high which causes the signal to noise on your line to be lower then it should, in a nutshell this is the main cause to random drops. I have re-synced your line to 6 megs which drops your ATUC Attenuation and increases your signal to noise on the line, this makes it more stable and you should not see random drops in the future. Please get back to us if you have any questions as I will be more than happy to assist. Kind regards Sashen




So, it was 10Mb in the beginning, then issues popped up and the line was re-synced to 8Mb, then down to 7Mb.

Now down to 6Mb and the issues are still there.
There is a fault on the line itself, of that I am very sure.
 
Last edited:
Bursty-dude said:
Was running fine until 12-10pm. Then just died again....

Line back again after rebooting three times. Did get feedback:

Hi there Ryan Trust you are well After running a test on your line 012******* I saw that the ATUC Attenuation rate on your line was a bit to high which causes the signal to noise on your line to be lower then it should, in a nutshell this is the main cause to random drops. I have re-synced your line to 6 megs which drops your ATUC Attenuation and increases your signal to noise on the line, this makes it more stable and you should not see random drops in the future. Please get back to us if you have any questions as I will be more than happy to assist. Kind regards Sashen




So, it was 10Mb in the beginning, then issues popped up and the line was re-synced to 8Mb, then down to 7Mb.

Now down to 6Mb and the issues are still there.
There is a fault on the line itself, of that I am very sure.
Click to expand...

If you have issues like that where sometimes your SnR gets too low, and other times it's fine, then you have a line fault. :/
 
That's what I've been thinking from the start.

10Mb in January down to 6Mb now and still these issues remain.

My reply to Sashen:

"Hi Sashen.
Thanks for the feedback.

Today at 12-10pm, the line died for no reason again. I rebooted the router 3 times and finally got a connection. This issue has become worse over the last three weeks.

Last month I actually lost around 25Gb due to the line being so slow, I could not use the data allocation. I went with a lower Capped data plan due to my doubts that I will be able to use it all up and lose it like what happened last month.

In January this year just after we got connected to Afrihost ADSL, the line speed was 10Mb. Then issues crept in and the line speed was synced to 8Mb. Then it was down to 7Mb. Now it is at 6Mb and the problems are still there.

I honestly hope that Afrihost can put pressure on Telkom to fix the lines as I chose Afrihost so that I do not have to deal with them ever again. The SNR fluctuations show that there is a line fault, and I hope I don't end up getting synced at 1Mb at the rate it is going now.

Regards, Ryan."
 
Last edited:
Line synced at 6Mb now.

3045478537.png

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 9 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 13 ms 12 ms 13 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 62 ms 49 ms 40 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 12 ms 13 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 12 ms 12 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 208 ms 205 ms 212 ms core2.ams.net.google.com [195.69.145.100]
8 208 ms 208 ms 208 ms 209.85.254.95
9 382 ms 360 ms 345 ms 209.85.253.247
10 349 ms 351 ms 349 ms 209.85.254.213
11 212 ms 219 ms 216 ms 216.239.49.28
12 * * * Request timed out.
13 206 ms 206 ms 207 ms ea-in-f105.1e100.net [74.125.136.105]

Trace complete.
 
Dead since 7-30pm but back at 9-40pm.

And thanks to the Hellscum tech that lied to Afrihost about contacting me and then resyncing the line to 4Mb....
Afrihost resynced to 8Mb and it seems OK now. Will test tomorrow.
 
Last edited:
Bursty-dude said:
Dead since 7-30pm but back at 9-40pm.

And thanks to the Hellscum tech that lied to Afrihost about contacting me and then resyncing the line to 4Mb....
Afrihost resynced to 8Mb and it seems OK now. Will test tomorrow.
Click to expand...

:(
Not ideal, but please get in touch if anything changes.
 
Not happy at all......

Yesterday it was running perfectly fine up until about 11-30pm when the line died for no reason.
I switched the router off and went to bed rather that rebooting constantly.

And now this crap again:
3052113892.png

Yet something says otherwise:
ScreenShot021.jpg

Traceroute:

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 44 ms 45 ms 47 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 47 ms 48 ms 49 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 67 ms 68 ms 66 ms am-cr-2.nl--am-cr-nl-b.mtnns.net [196.44.31.171]

6 50 ms 52 ms 49 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 259 ms 255 ms * core2.ams.net.google.com [195.69.145.100]
8 280 ms 250 ms 258 ms 209.85.254.95
9 404 ms 424 ms 433 ms 209.85.253.247
10 386 ms 397 ms 381 ms 209.85.255.87
11 385 ms 384 ms 402 ms 209.85.254.199
12 254 ms 246 ms 245 ms 72.14.233.30
13 240 ms 240 ms 234 ms 72.14.235.213
14 261 ms 255 ms 261 ms ham02s12-in-f18.1e100.net [173.194.113.178]

Trace complete.





So, who can I go bitchslap at Telkom to get something done about this? There is a line fault, fix the damn thing.....
 
Just to add, it has been crap like this the whole day.

3052151569.png

Like I said, yesterday it was fine with 7Mb and upwards, I used 6.09Gb of data, today just sucked.
 
Meh meh meh.

Code: 
10/23/2013 4:16 PM GMT	105.236.209.125	133.6 kB/s	64.1 kB/s	165 ms	London	~ 6000 mi
10/23/2013 4:13 PM GMT	105.236.209.125	837.6 kB/s	66.8 kB/s	17 ms	Cape Town	< 50 mi
10/23/2013 3:51 PM GMT	105.236.209.125	183.8 kB/s	62.5 kB/s	169 ms	London	~ 6000 mi
10/23/2013 3:50 PM GMT	105.236.209.125	309.0 kB/s	66.6 kB/s	15 ms	Cape Town	< 50 mi
10/23/2013 3:19 PM GMT	105.236.209.125	203.9 kB/s	66.6 kB/s	16 ms	Cape Town	< 50 mi

Inconsistent. International doesnt even top 2Mbps on a 8Mbps line.
Local will do full line speed when it feels like it.
Our DSLAM or Exchange is not congested. It was upgraded recently.
Pings and traceroutes are always fine.

Code: 
Ping has started…

PING webafrica.com (196.220.58.66): 56 data bytes
64 bytes from 196.220.58.66: icmp_seq=0 ttl=116 time=14.698 ms
64 bytes from 196.220.58.66: icmp_seq=1 ttl=116 time=14.004 ms
64 bytes from 196.220.58.66: icmp_seq=2 ttl=116 time=13.965 ms
64 bytes from 196.220.58.66: icmp_seq=3 ttl=116 time=14.748 ms
64 bytes from 196.220.58.66: icmp_seq=4 ttl=116 time=14.196 ms
64 bytes from 196.220.58.66: icmp_seq=5 ttl=116 time=14.187 ms
64 bytes from 196.220.58.66: icmp_seq=6 ttl=116 time=13.702 ms
64 bytes from 196.220.58.66: icmp_seq=7 ttl=116 time=16.582 ms
64 bytes from 196.220.58.66: icmp_seq=8 ttl=116 time=14.160 ms
64 bytes from 196.220.58.66: icmp_seq=9 ttl=116 time=16.308 ms

--- webafrica.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 13.702/14.655/16.582/0.945 ms

Code: 
Traceroute has started…

traceroute to afrihost.com (197.242.144.102), 64 hops max, 72 byte packets
 1  sx762 (10.0.0.2)  1.324 ms  1.106 ms  1.077 ms
 2  105-236-8-193-esr-lo.mtnbusiness.co.za (105.236.8.193)  8.688 ms  8.521 ms  8.360 ms
 3  ipc-send-tb-3a.mtnbusiness.net (41.181.53.214)  67.353 ms  25.637 ms  22.612 ms
 4  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  10.461 ms  10.346 ms  10.051 ms
 5  compj-cpt-1.mtnns.net (196.44.18.2)  21.089 ms  23.843 ms  23.270 ms
 6  ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  21.359 ms  21.586 ms  22.036 ms
 7  ct-cr-2.za--rb-cr-1.za.mtnns.net (196.44.31.69)  34.742 ms  36.853 ms  34.518 ms
 8  196.44.31.97 (196.44.31.97)  33.340 ms
    jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221)  58.785 ms
    196.44.31.97 (196.44.31.97)  32.640 ms
 9  196.30.1.39 (196.30.1.39)  39.899 ms  36.208 ms  35.868 ms
10  tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net (196.31.220.23)  37.078 ms  36.983 ms  38.940 ms
11  tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net (196.31.63.198)  34.000 ms  34.271 ms  34.104 ms
12  cms-gm.afrihost.com (197.242.144.102)  34.904 ms  34.502 ms  34.481 ms

Code: 
Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.251.195
traceroute to bbc.co.uk (212.58.251.195), 64 hops max, 72 byte packets
 1  sx762 (10.0.0.2)  1.317 ms  1.107 ms  1.073 ms
 2  105-236-8-193-esr-lo.mtnbusiness.co.za (105.236.8.193)  8.509 ms  8.709 ms  8.623 ms
 3  ipc-send-tb-3a.mtnbusiness.net (41.181.53.214)  20.253 ms  59.465 ms  14.737 ms
 4  tb-dca-2.za--qux-a.za.mtnbusiness.net (41.181.184.28)  11.849 ms  76.182 ms  14.964 ms
 5  compj-cpt-1.mtnns.net (196.44.18.2)  12.115 ms  12.366 ms  12.640 ms
 6  ls-cr-2--tb-cr-1.uk-b.mtnns.net (196.44.31.113)  177.181 ms  178.396 ms  176.161 ms
 7  ls-pr-1.uk--ls-cr-2.uk-a.mtn.net (209.212.111.201)  158.957 ms  161.393 ms  160.337 ms
 8  bbc-linx.pr01.thdow.bbc.co.uk (195.66.224.103)  163.379 ms  235.344 ms  162.388 ms
 9  * * *
10  * * *
11  ae0.er01.telhc.bbc.co.uk (132.185.254.109)  154.342 ms  154.832 ms  154.757 ms
12  132.185.255.140 (132.185.255.140)  154.345 ms  154.340 ms  153.489 ms
13  www-vip.telhc.bbc.co.uk (212.58.251.195)  157.028 ms  155.450 ms  154.454 ms
 
blogbytes said:
Meh meh meh.

Code: 
10/23/2013 4:16 PM GMT	105.236.209.125	133.6 kB/s	64.1 kB/s	165 ms	London	~ 6000 mi
10/23/2013 4:13 PM GMT	105.236.209.125	837.6 kB/s	66.8 kB/s	17 ms	Cape Town	< 50 mi
10/23/2013 3:51 PM GMT	105.236.209.125	183.8 kB/s	62.5 kB/s	169 ms	London	~ 6000 mi
10/23/2013 3:50 PM GMT	105.236.209.125	309.0 kB/s	66.6 kB/s	15 ms	Cape Town	< 50 mi
10/23/2013 3:19 PM GMT	105.236.209.125	203.9 kB/s	66.6 kB/s	16 ms	Cape Town	< 50 mi

Inconsistent. International doesnt even top 2Mbps on a 8Mbps line.
Local will do full line speed when it feels like it.
Our DSLAM or Exchange is not congested. It was upgraded recently.
Pings and traceroutes are always fine.

Code: 
Ping has started…

PING webafrica.com (196.220.58.66): 56 data bytes
64 bytes from 196.220.58.66: icmp_seq=0 ttl=116 time=14.698 ms
64 bytes from 196.220.58.66: icmp_seq=1 ttl=116 time=14.004 ms
64 bytes from 196.220.58.66: icmp_seq=2 ttl=116 time=13.965 ms
64 bytes from 196.220.58.66: icmp_seq=3 ttl=116 time=14.748 ms
64 bytes from 196.220.58.66: icmp_seq=4 ttl=116 time=14.196 ms
64 bytes from 196.220.58.66: icmp_seq=5 ttl=116 time=14.187 ms
64 bytes from 196.220.58.66: icmp_seq=6 ttl=116 time=13.702 ms
64 bytes from 196.220.58.66: icmp_seq=7 ttl=116 time=16.582 ms
64 bytes from 196.220.58.66: icmp_seq=8 ttl=116 time=14.160 ms
64 bytes from 196.220.58.66: icmp_seq=9 ttl=116 time=16.308 ms

--- webafrica.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 13.702/14.655/16.582/0.945 ms

Code: 
Traceroute has started…

traceroute to afrihost.com (197.242.144.102), 64 hops max, 72 byte packets
 1  sx762 (10.0.0.2)  1.324 ms  1.106 ms  1.077 ms
 2  105-236-8-193-esr-lo.mtnbusiness.co.za (105.236.8.193)  8.688 ms  8.521 ms  8.360 ms
 3  ipc-send-tb-3a.mtnbusiness.net (41.181.53.214)  67.353 ms  25.637 ms  22.612 ms
 4  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  10.461 ms  10.346 ms  10.051 ms
 5  compj-cpt-1.mtnns.net (196.44.18.2)  21.089 ms  23.843 ms  23.270 ms
 6  ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  21.359 ms  21.586 ms  22.036 ms
 7  ct-cr-2.za--rb-cr-1.za.mtnns.net (196.44.31.69)  34.742 ms  36.853 ms  34.518 ms
 8  196.44.31.97 (196.44.31.97)  33.340 ms
    jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221)  58.785 ms
    196.44.31.97 (196.44.31.97)  32.640 ms
 9  196.30.1.39 (196.30.1.39)  39.899 ms  36.208 ms  35.868 ms
10  tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net (196.31.220.23)  37.078 ms  36.983 ms  38.940 ms
11  tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net (196.31.63.198)  34.000 ms  34.271 ms  34.104 ms
12  cms-gm.afrihost.com (197.242.144.102)  34.904 ms  34.502 ms  34.481 ms

Code: 
Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.251.195
traceroute to bbc.co.uk (212.58.251.195), 64 hops max, 72 byte packets
 1  sx762 (10.0.0.2)  1.317 ms  1.107 ms  1.073 ms
 2  105-236-8-193-esr-lo.mtnbusiness.co.za (105.236.8.193)  8.509 ms  8.709 ms  8.623 ms
 3  ipc-send-tb-3a.mtnbusiness.net (41.181.53.214)  20.253 ms  59.465 ms  14.737 ms
 4  tb-dca-2.za--qux-a.za.mtnbusiness.net (41.181.184.28)  11.849 ms  76.182 ms  14.964 ms
 5  compj-cpt-1.mtnns.net (196.44.18.2)  12.115 ms  12.366 ms  12.640 ms
 6  ls-cr-2--tb-cr-1.uk-b.mtnns.net (196.44.31.113)  177.181 ms  178.396 ms  176.161 ms
 7  ls-pr-1.uk--ls-cr-2.uk-a.mtn.net (209.212.111.201)  158.957 ms  161.393 ms  160.337 ms
 8  bbc-linx.pr01.thdow.bbc.co.uk (195.66.224.103)  163.379 ms  235.344 ms  162.388 ms
 9  * * *
10  * * *
11  ae0.er01.telhc.bbc.co.uk (132.185.254.109)  154.342 ms  154.832 ms  154.757 ms
12  132.185.255.140 (132.185.255.140)  154.345 ms  154.340 ms  153.489 ms
13  www-vip.telhc.bbc.co.uk (212.58.251.195)  157.028 ms  155.450 ms  154.454 ms
Click to expand...

These traces look pretty normal to me, and not too bad, unless I've missed something in my glance over them.
 
Demand is currently high? But I am on a capped package and according to all the bragging, capped accounts do not get throttled or shaped in any way. How does the demand explain why the speeds have been sitting at 2Mb the entire day on a 10Mb capped account?

I did tests around every half hour throughout the day, but did not put them up here so as to clutter up this thread.
For the last 3+ weeks this has gotten worse by the day, literally.



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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 12 ms 12 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 15 ms 22 ms 21 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 13 ms 12 ms 11 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 272 ms 353 ms 99 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 158 ms 23 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 * * 205 ms core2.ams.net.google.com [195.69.145.100]
8 204 ms 203 ms 203 ms 209.85.254.90
9 381 ms 392 ms 402 ms 72.14.238.153
10 351 ms 375 ms 376 ms 209.85.254.227
11 375 ms 354 ms 356 ms 209.85.254.207
12 211 ms 210 ms 211 ms 72.14.233.217
13 231 ms 229 ms 229 ms 72.14.235.213
14 211 ms 210 ms 210 ms ham02s12-in-f17.1e100.net [173.194.113.177]

Trace complete.
 
Bursty-dude said:
Demand is currently high? But I am on a capped package and according to all the bragging, capped accounts do not get throttled or shaped in any way. How does the demand explain why the speeds have been sitting at 2Mb the entire day on a 10Mb capped account?

I did tests around every half hour throughout the day, but did not put them up here so as to clutter up this thread.
For the last 3+ weeks this has gotten worse by the day, literally.



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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 12 ms 12 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 15 ms 22 ms 21 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 13 ms 12 ms 11 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 272 ms 353 ms 99 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 158 ms 23 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 * * 205 ms core2.ams.net.google.com [195.69.145.100]
8 204 ms 203 ms 203 ms 209.85.254.90
9 381 ms 392 ms 402 ms 72.14.238.153
10 351 ms 375 ms 376 ms 209.85.254.227
11 375 ms 354 ms 356 ms 209.85.254.207
12 211 ms 210 ms 211 ms 72.14.233.217
13 231 ms 229 ms 229 ms 72.14.235.213
14 211 ms 210 ms 210 ms ham02s12-in-f17.1e100.net [173.194.113.177]

Trace complete.
Click to expand...

You could be affected if demand is so excessive that we actually reach a physical max on the network, which is why we need to shape Uncapped accounts to bring demand down to within limits. Today has been exceptionally difficult as the demand for bandwidth, especially for Apple Services, has been almost 10% of our available capacity.

I think we'll see more normal results when the demand for Apple Services calms down (hopefully even tonight) and we can run the network as normal again :(
 
AfriMan said:
I think we'll see more normal results when the demand for Apple Services calms down (hopefully even tonight) and we can run the network as normal again :(
Click to expand...

If it is not the one thing it is something else. First GTA5 then windows now apple. every-time someone brings out an update you will get s**t performance from afrihost.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X