Afrihost Uncapped ADSL Feedback (Pt2)

Status
Not open for further replies.
To be honest I don't mind.

That extra R100 isn't that much extra to be unshaped 24/7.

Still, it's not an ideal solution :( We want everyone to have the best possible use and experience using our Home Uncapped accounts. Just remember that shaping may be applied during peak hours. Naturally, if you specifically need a fully unshaped account to use any time of the day Business Uncapped/ Capped accounts are a better option for you.
 
Have you tried scheduling the downloads for after hours? They should come down quicker when the network is quieter.

The terrible thing is Afrihost's opinion of after hours is 12.30 AM to 8AM and the rest of SA's opinion is 7PM to 8AM.
 
The terrible thing is Afrihost's opinion of after hours is 12.30 AM to 8AM and the rest of SA's opinion is 7PM to 8AM.

We shape according to network pressure. People get home, then log onto the internet. Our busy hours have extended. We begin to ease shaping from about 10pm.
 
The terrible thing is Afrihost's opinion of after hours is 12.30 AM to 8AM and the rest of SA's opinion is 7PM to 8AM.

Again, this can change depending on the usage. This also may not be across the board, our Southern IPC region may see shaping earlier and the Northern IPC see shaping later, or visa versa.
At the end of the day, our clients determine the level of shaping on the Home Uncapped accounts.
 
Ok AfriFamily riddle me this. I just enabled the "turbocharge" option on my 4mb uncapped account as I urgently need to grab something and guess what. Its coming down at 1.2kB/s

What is the point of enabling this then. I made sure my line is in tip top shape, restarted the router to be 100% sure. Normal traffic is fine but my HTTP, HTTPS and P2P is being shaped to hell.
 
Not at all. We aren't pushing any users over to our Business accounts.
Again guys - we don't like the amount of shaping that's being applied but improvements are being seen though.

Shaping Policy: 50% Download/ 25.0% P2P
home product at 19h00...

not going to fork out additional R300+- for business 8mb
 
Ok so there is definitely something going on with my exchange!!

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     *        *        7 ms  105-236-3-1-esr-lo.mtnbusiness.co.za [105.236.3.
1]
  3    10 ms    10 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
  4    11 ms    11 ms    10 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5    11 ms    12 ms    11 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6     9 ms    10 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7     *        *        *     Request timed out.
  8    10 ms    11 ms    11 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

and...

Code:
Tracing route to star.c10r.facebook.com [31.13.72.65]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     *        *        *     Request timed out.
  3    10 ms    10 ms    12 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    11 ms    11 ms    10 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    11 ms    12 ms    11 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6    11 ms     9 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7     *        *        *     Request timed out.
  8     *        *      178 ms  po126.msw01.05.lhr2.tfbnw.net [74.119.77.53]
  9   174 ms   173 ms   174 ms  edge-star-shv-05-lhr2.facebook.com [31.13.72.65]


Trace complete.

** EDIT ** And then a tracert to facebook right after I posted...

Code:
Tracing route to star.c10r.facebook.com [31.13.72.33]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     9 ms     8 ms    31 ms  105-236-3-1-esr-lo.mtnbusiness.co.za [105.236.3.
1]
  3    20 ms    19 ms    20 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    25 ms    24 ms    24 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5    15 ms    15 ms    16 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6    10 ms    10 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   185 ms   186 ms   185 ms  linx.br01.lhr1.tfbnw.net [195.66.225.69]
  8   194 ms   186 ms   180 ms  po126.msw01.01.lhr2.tfbnw.net [31.13.28.225]
  9   182 ms   178 ms   176 ms  edge-star-shv-01-lhr2.facebook.com [31.13.72.33]


Trace complete.
 
Ok AfriFamily riddle me this. I just enabled the "turbocharge" option on my 4mb uncapped account as I urgently need to grab something and guess what. Its coming down at 1.2kB/s

What is the point of enabling this then. I made sure my line is in tip top shape, restarted the router to be 100% sure. Normal traffic is fine but my HTTP, HTTPS and P2P is being shaped to hell.


Turbocharge will unshape you for a set period of time. Can you please PM me your username and I can check on your account.
 
Ok so there is definitely something going on with my exchange!!

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     *        *        7 ms  105-236-3-1-esr-lo.mtnbusiness.co.za [105.236.3.
1]
  3    10 ms    10 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
  4    11 ms    11 ms    10 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5    11 ms    12 ms    11 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6     9 ms    10 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7     *        *        *     Request timed out.
  8    10 ms    11 ms    11 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

and...

Code:
Tracing route to star.c10r.facebook.com [31.13.72.65]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     *        *        *     Request timed out.
  3    10 ms    10 ms    12 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    11 ms    11 ms    10 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    11 ms    12 ms    11 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6    11 ms     9 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7     *        *        *     Request timed out.
  8     *        *      178 ms  po126.msw01.05.lhr2.tfbnw.net [74.119.77.53]
  9   174 ms   173 ms   174 ms  edge-star-shv-05-lhr2.facebook.com [31.13.72.65]


Trace complete.

** EDIT ** And then a tracert to facebook right after I posted...

Code:
Tracing route to star.c10r.facebook.com [31.13.72.33]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     9 ms     8 ms    31 ms  105-236-3-1-esr-lo.mtnbusiness.co.za [105.236.3.
1]
  3    20 ms    19 ms    20 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    25 ms    24 ms    24 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5    15 ms    15 ms    16 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6    10 ms    10 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   185 ms   186 ms   185 ms  linx.br01.lhr1.tfbnw.net [195.66.225.69]
  8   194 ms   186 ms   180 ms  po126.msw01.01.lhr2.tfbnw.net [31.13.28.225]
  9   182 ms   178 ms   176 ms  edge-star-shv-01-lhr2.facebook.com [31.13.72.33]


Trace complete.

I know that our team is looking into this for you. Hopefully we can help get this resolved.
 
I would like to highlight my problem. I went onto the BF3 server browser. Now normally my ping result would return a constant ping all the time for a specific server. Below is 8 screenies. They were taken one after the other. So click refresh, take screenie, refresh, screenie... Now please bear in mind that this used to be a constant 11ms!!!!!

1_zpsd6db9604.jpg


2_zps1db7664d.jpg


5_zps433baf3a.jpg


6_zps2e699f3f.jpg


4_zpse376bf66.jpg


7_zps83f680e9.jpg


3_zps54c824f5.jpg


9_zps0d5d8648.jpg


So this is what is making me furious at the moment!! My gaming used to be fine on the home uncapped package!! But now it is buggered!!
 
I would like to highlight my problem. I went onto the BF3 server browser. Now normally my ping result would return a constant ping all the time for a specific server. Below is 8 screenies. They were taken one after the other. So click refresh, take screenie, refresh, screenie... Now please bear in mind that this used to be a constant 11ms!!!!!

What happens when you do a
Code:
pathping <server>
? (make sure your internet is idling for those 5 or 6 minutes.
 
Huge packet loss in CT on an Afrihost uncapped 4mbps account.

--- google.com ping statistics --- (173.194.69.100)
1109 packets transmitted, 857 packets received, 22.7% packet loss
round-trip min/avg/max/stddev = 193.098/271.302/513.336/62.033 ms

Seems to be both local / intl. Tested with mweb / google.

Anyone else?
 
What happens when you do a
Code:
pathping <server>
? (make sure your internet is idling for those 5 or 6 minutes.

I have absolutely no idea what this does but here you go..

Code:
Tracing route to 196.28.69.66 over a maximum of 30 hops

  0  Creature-i7 [192.168.0.##]
  1  192.168.0.254
  2  105-236-#-#-esr-lo.mtnbusiness.co.za [105.236.#.#]
  3  ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
  4  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
  5  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7  jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
  8  postfix.wipronet.co.za [196.22.161.133]
  9  tengig0-0-0-3.vic-p-1.mweb.co.za [197.80.7.1]
 10  tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]
 11  tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]
 12  197-80-96-30.jhb.mweb.co.za [197.80.96.30]
 13  197.80.198.66
 14  196.28.69.66

Computing statistics for 350 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Creature-i7 [192.168.0.##]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.254
                                0/ 100 =  0%   |
  2   11ms     0/ 100 =  0%     0/ 100 =  0%  105-236-3-1-esr-lo.mtnbusiness.co.
za [105.236.3.1]
                                0/ 100 =  0%   |
  3   19ms     0/ 100 =  0%     0/ 100 =  0%  ipc-recieve-rb-2a.za.mtnbusiness.n
et [41.181.178.65]
                                0/ 100 =  0%   |
  4   13ms     0/ 100 =  0%     0/ 100 =  0%  rb-dca-2.za--rb-cr-1.za-a.mtnns.ne
t [196.44.31.120]
                                0/ 100 =  0%   |
  5   13ms     2/ 100 =  2%     2/ 100 =  2%  jh-cr-1.za--rb-cr-2.za.mtnns.net [
196.44.0.42]
                                0/ 100 =  0%   |
  6   15ms     0/ 100 =  0%     0/ 100 =  0%  qux-jh-dca-2.za-b.za.mtnbusiness.n
et [41.181.165.115]
                                0/ 100 =  0%   |
  7   13ms     1/ 100 =  1%     1/ 100 =  1%  jh-pr-1.za--jh-cr-2.za.mtnns.net [
196.44.0.222]
                                0/ 100 =  0%   |
  8   11ms     0/ 100 =  0%     0/ 100 =  0%  postfix.wipronet.co.za [196.22.161
.133]
                                0/ 100 =  0%   |
  9   16ms     1/ 100 =  1%     1/ 100 =  1%  tengig0-0-0-3.vic-p-1.mweb.co.za [
197.80.7.1]
                                0/ 100 =  0%   |
 10   13ms     0/ 100 =  0%     0/ 100 =  0%  tengig0-0-0-0.vic-pe-1.mweb.co.za
[197.80.4.243]
                                0/ 100 =  0%   |
 11   15ms     1/ 100 =  1%     1/ 100 =  1%  tengig0-0-0-0.mca-pe-1.mweb.co.za
[197.80.4.37]
                                0/ 100 =  0%   |
 12   12ms     0/ 100 =  0%     0/ 100 =  0%  197-80-96-30.jhb.mweb.co.za [197.8
0.96.30]
                                0/ 100 =  0%   |
 13   15ms     2/ 100 =  2%     2/ 100 =  2%  197.80.198.66
                                0/ 100 =  0%   |
 14   12ms     0/ 100 =  0%     0/ 100 =  0%  196.28.69.66

Trace complete.
 
Last edited:
Shaping Policy: 50% Download/ 25.0% P2P
home product at 19h00...

not going to fork out additional R300+- for business 8mb

Shaping depends on demand. There continues to be pressure on the network and we have to shape until network demand drops. We can ease shaping as pressure decreases.
 
Huge packet loss in CT on an Afrihost uncapped 4mbps account.

--- google.com ping statistics --- (173.194.69.100)
1109 packets transmitted, 857 packets received, 22.7% packet loss
round-trip min/avg/max/stddev = 193.098/271.302/513.336/62.033 ms

Seems to be both local / intl. Tested with mweb / google.

Anyone else?

Could you post a traceroute?
 
I have absolutely no idea what this does but here you go..

Code:
Tracing route to 196.28.69.66 over a maximum of 30 hops

  0  Creature-i7 [192.168.0.##]
  1  192.168.0.254
  2  105-236--esr-lo.mtnbusiness.co.za [105.236.]
  3  ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
  4  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
  5  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7  jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
  8  postfix.wipronet.co.za [196.22.161.133]
  9  tengig0-0-0-3.vic-p-1.mweb.co.za [197.80.7.1]
 10  tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]
 11  tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]
 12  197-80-96-30.jhb.mweb.co.za [197.80.96.30]
 13  197.80.198.66
 14  196.28.69.66

Computing statistics for 350 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Creature-i7 [192.168.0.##]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.254
                                0/ 100 =  0%   |
  2   11ms     0/ 100 =  0%     0/ 100 =  0%  105-236--esr-lo.mtnbusiness.co.
za [105.236.]
                                0/ 100 =  0%   |
  3   19ms     0/ 100 =  0%     0/ 100 =  0%  ipc-recieve-rb-2a.za.mtnbusiness.n
et [41.181.178.65]
                                0/ 100 =  0%   |
  4   13ms     0/ 100 =  0%     0/ 100 =  0%  rb-dca-2.za--rb-cr-1.za-a.mtnns.ne
t [196.44.31.120]
                                0/ 100 =  0%   |
  5   13ms     2/ 100 =  2%     2/ 100 =  2%  jh-cr-1.za--rb-cr-2.za.mtnns.net [
196.44.0.42]
                                0/ 100 =  0%   |
  6   15ms     0/ 100 =  0%     0/ 100 =  0%  qux-jh-dca-2.za-b.za.mtnbusiness.n
et [41.181.165.115]
                                0/ 100 =  0%   |
  7   13ms     1/ 100 =  1%     1/ 100 =  1%  jh-pr-1.za--jh-cr-2.za.mtnns.net [
196.44.0.222]
                                0/ 100 =  0%   |
  8   11ms     0/ 100 =  0%     0/ 100 =  0%  postfix.wipronet.co.za [196.22.161
.133]
                                0/ 100 =  0%   |
  9   16ms     1/ 100 =  1%     1/ 100 =  1%  tengig0-0-0-3.vic-p-1.mweb.co.za [
197.80.7.1]
                                0/ 100 =  0%   |
 10   13ms     0/ 100 =  0%     0/ 100 =  0%  tengig0-0-0-0.vic-pe-1.mweb.co.za
[197.80.4.243]
                                0/ 100 =  0%   |
 11   15ms     1/ 100 =  1%     1/ 100 =  1%  tengig0-0-0-0.mca-pe-1.mweb.co.za
[197.80.4.37]
                                0/ 100 =  0%   |
 12   12ms     0/ 100 =  0%     0/ 100 =  0%  197-80-96-30.jhb.mweb.co.za [197.8
0.96.30]
                                0/ 100 =  0%   |
 13   15ms     2/ 100 =  2%     2/ 100 =  2%  197.80.198.66
                                0/ 100 =  0%   |
 14   12ms     0/ 100 =  0%     0/ 100 =  0%  196.28.69.66

Trace complete.

Thanks.
A path ping monitors each node or hop in the ping list and checks it for packet loss. As you'll see you've got 1/2% at most, which is not 100%, but acceptable though.

Oh and btw,
Code:
0  Creature-i7 [192.168.0.##]
  1  192.168.0.254
  2  105-236-#-#-esr-lo.mtnbusiness.co.za [105.236.#.#]
Ideally you want to mask the last two subnets of the second hop, not your private IP :p
 
Thanks.
A path ping monitors each node or hop in the ping list and checks it for packet loss. As you'll see you've got 1/2% at most, which is not 100%, but acceptable though.

Oh and btw,
Code:
0  Creature-i7 [192.168.0.##]
  1  192.168.0.254
  2  105-236-#-#-esr-lo.mtnbusiness.co.za [105.236.#.#]
Ideally you want to mask the last two subnets of the second hop, not your private IP :p

Yeah thanks :)
 
Could you post a traceroute?

traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 173.194.69.102
traceroute to google.com (173.194.69.102), 64 hops max, 52 byte packets
1 router.lan (192.168.1.1) 25.188 ms 0.951 ms 0.808 ms
2 105-236-5-129-esr-lo.mtnbusiness.co.za (105.236.5.129) 13.768 ms 12.362 ms 9.099 ms
3 ipc-send-tb-3a.mtnbusiness.net (41.181.53.214) 24.691 ms 8.433 ms 8.353 ms
4 tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 8.417 ms 45.196 ms 48.298 ms
5 unc-cpt-1.mtnns.net (196.44.18.8) 52.534 ms 67.070 ms *
6 196.44.31.106 (196.44.31.106) 93.478 ms 88.848 ms 66.548 ms
7 am-cr-1.am--lt-cr-1.uk-a.mtnns.net (196.44.31.221) 191.268 ms 200.993 ms 210.376 ms
8 ls-pr-1.uk--ls-cr-1.uk-a.mtn.net (209.212.111.83) 272.953 ms 184.278 ms 192.205 ms
9 195.66.224.125 (195.66.224.125) 230.912 ms 194.653 ms 175.192 ms
10 * 209.85.240.61 (209.85.240.61) 265.447 ms 248.500 ms
11 * * 209.85.253.92 (209.85.253.92) 344.081 ms
12 72.14.242.166 (72.14.242.166) 326.264 ms
72.14.232.134 (72.14.232.134) 330.613 ms *
13 209.85.244.210 (209.85.244.210) 397.905 ms 372.969 ms
209.85.244.208 (209.85.244.208) 357.445 ms
14 216.239.48.53 (216.239.48.53) 209.807 ms 234.604 ms *
15 * * *
16 bk-in-f102.1e100.net (173.194.69.102) 283.028 ms 212.254 ms *

traceroute mweb.co.za
traceroute to mweb.co.za (196.2.63.110), 64 hops max, 52 byte packets
1 router.lan (192.168.1.1) 1.672 ms 1.027 ms 0.858 ms
2 105-236-5-129-esr-lo.mtnbusiness.co.za (105.236.5.129) 60.241 ms 38.398 ms 10.364 ms
3 ipc-send-tb-3a.mtnbusiness.net (41.181.53.214) 16.475 ms 10.453 ms 8.237 ms
4 tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 8.352 ms 8.448 ms 49.246 ms
5 unc-cpt-1.mtnns.net (196.44.18.8) 44.424 ms * 113.512 ms
6 196.44.31.106 (196.44.31.106) 71.752 ms 52.200 ms 29.913 ms
7 nl-ha-2.za--rb-cr-1.za-a.mtnns.net (196.44.0.121) 79.929 ms 130.014 ms
196.44.0.74 (196.44.0.74) 82.184 ms
8 196-28-178-141.adsl.mweb.co.za (196.28.178.141) 10.027 ms 25.070 ms 19.467 ms
9 197-84-7-2.cpt.mweb.co.za (197.84.7.2) 139.003 ms 63.829 ms
197-84-7-1.cpt.mweb.co.za (197.84.7.1) 22.030 ms
10 197-84-5-238.cpt.mweb.co.za (197.84.5.238) 55.347 ms 31.990 ms 36.611 ms
11 196.28.178.66 (196.28.178.66) 19.877 ms 15.082 ms 11.507 ms
12 cte-core-sw2.vwol.net (196.41.144.35) 12.456 ms 11.770 ms 14.699 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
 
Something's happened! Performance during the day today, and this evening, is much better than I've seen in the last 2 weeks. Getting reasonable speeds (Jhb area).
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X