Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
AfriMan said:
You should see good speeds now before demand increases.
Click to expand...

I did not. Once again, windows 10 updates are still not sorted and it is now another 2 weeks later since I last asked.
I am honestly getting really frustrated as if I had to go fetch the image using http downloads instead of using the update service there is no issue with speed at all.
 
Mike43110 said:
I did not. Once again, windows 10 updates are still not sorted and it is now another 2 weeks later since I last asked.
I am honestly getting really frustrated as if I had to go fetch the image using http downloads instead of using the update service there is no issue with speed at all.
Click to expand...

Really sorry about that, I know how frustrating this can be :(
We are working towards a good solution to have these updates sorted out.
 
Mike43110 said:
I did not. Once again, windows 10 updates are still not sorted and it is now another 2 weeks later since I last asked.
I am honestly getting really frustrated as if I had to go fetch the image using http downloads instead of using the update service there is no issue with speed at all.
Click to expand...

Hi,

I have been reporting the same issues with Windows 10 updates, and we keep on getting the same run around. Yesterday Winnows 10 updates sat at 1% for 3 hours and all it had to download was 346kb. Why is Afrihost the only ISP that continually has these types of issues? Even Windows 7 and 8.x have update issues but not as bad, but I can download ptp at full speed.
 
PurSpyk!! said:
Its been weeks and no improvement?
Click to expand...

I know :( It has been too long, and we know it's far from anything near ideal on our end.
When things are fixed though, they're going to be fixed properly and hopefully we can put this all behind us.
 
electrofreeze said:
this will most properly only be fixed when windows 10 is released as it uses unnecessary bandwidth that ah don't have
Click to expand...

I don't think that's the case at all, MS updates (regardless of version or release) should run as such on our network. Currently they're not, but they will :)
 
AfriGuy said:
I don't think that's the case at all, MS updates (regardless of version or release) should run as such on our network. Currently they're not, but they will :)
Click to expand...

To be a bit blunt - can I at least not get generic response A each time I ask about this? Every time this gets mentioned the 1st thing that is mentioned is contention. Contention is most definitely NOT the issue here as I think has been established? (Contention should affect my other experiences as well) So getting told that every time just seems like it is an instinct response at this point to label any issue under that banner.

Sorry to be a bit rude but the generic response to this issue each time it is mentioned is part of why it has been such a grating issue.
 
Mike43110 said:
To be a bit blunt - can I at least not get generic response A each time I ask about this? Every time this gets mentioned the 1st thing that is mentioned is contention. Contention is most definitely NOT the issue here as I think has been established? (Contention should affect my other experiences as well) So getting told that every time just seems like it is an instinct response at this point to label any issue under that banner.

Sorry to be a bit rude but the generic response to this issue each time it is mentioned is part of why it has been such a grating issue.
Click to expand...

That's not rude at all :)
It is generic, but in all honesty - there is no feedback around this :( It sucks, I know, both in terms of feedback that we post here as well as getting to the bottom of the issue.
 
My ire continues to grow.

Downloading Cygwin packages using the installer from ftp.is.co.za is erratic as windows updates.

Only the ftp mirrors were problematic.
 
Last edited:
How to interpret this? Seems all over the show?

traceroute -n 197.242.144.102

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 194.928 ms 736.339 ms
Request timed out *
4 41.181.221.218 422.052 ms 885.784 ms 667.219 ms
5 41.181.165.118 810.403 ms 826.3 ms 179.636 ms
6 Request timed out *
196.44.31.122 885.792 ms 18.811 ms
7 Request timed out *
196.44.0.221 900.994 ms
196.44.31.97 18.545 ms
8 196.30.1.39 741.579 ms 806.146 ms
Request timed out *
9 196.31.220.27 469.075 ms 636.929 ms 21.015 ms
10 196.31.63.202 316.706 ms 384.034 ms 22.817 ms
11 196.30.42.133 341.126 ms 32.476 ms 20.888 ms
12 197.242.144.102 198.898 ms 18.03 ms 23.278 ms


traceroute -n 8.8.8.8

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 17.747 ms 129.524 ms 62.756 ms
4 41.181.221.218 61.522 ms 17.192 ms 17.475 ms
5 41.181.165.118 39.207 ms 18.155 ms 17.49 ms
6 196.44.31.122 32.253 ms 18.012 ms 18.406 ms
7 41.181.139.99 17.542 ms 18.368 ms
41.181.139.109 36.934 ms
8 72.14.194.74 17.94 ms 18.634 ms 19.311 ms
9 72.14.239.35 18.692 ms
72.14.239.33 18.975 ms
72.14.239.53 19.675 ms
10 8.8.8.8 23.162 ms 18.843 ms 19.023 ms
 
Mike43110 said:
My ire continues to grow.

Downloading Cygwin packages using the installer from ftp.is.co.za is erratic as windows updates.

Only the ftp mirrors were problematic.
Click to expand...

Sorry to hear :( Is there a link that I can check out to see if the speeds are replicated from my end?
 
Gavin107 said:
How to interpret this? Seems all over the show?

traceroute -n 197.242.144.102

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 194.928 ms 736.339 ms
Request timed out *
4 41.181.221.218 422.052 ms 885.784 ms 667.219 ms
5 41.181.165.118 810.403 ms 826.3 ms 179.636 ms
6 Request timed out *
196.44.31.122 885.792 ms 18.811 ms
7 Request timed out *
196.44.0.221 900.994 ms
196.44.31.97 18.545 ms
8 196.30.1.39 741.579 ms 806.146 ms
Request timed out *
9 196.31.220.27 469.075 ms 636.929 ms 21.015 ms
10 196.31.63.202 316.706 ms 384.034 ms 22.817 ms
11 196.30.42.133 341.126 ms 32.476 ms 20.888 ms
12 197.242.144.102 198.898 ms 18.03 ms 23.278 ms


traceroute -n 8.8.8.8

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 17.747 ms 129.524 ms 62.756 ms
4 41.181.221.218 61.522 ms 17.192 ms 17.475 ms
5 41.181.165.118 39.207 ms 18.155 ms 17.49 ms
6 196.44.31.122 32.253 ms 18.012 ms 18.406 ms
7 41.181.139.99 17.542 ms 18.368 ms
41.181.139.109 36.934 ms
8 72.14.194.74 17.94 ms 18.634 ms 19.311 ms
9 72.14.239.35 18.692 ms
72.14.239.33 18.975 ms
72.14.239.53 19.675 ms
10 8.8.8.8 23.162 ms 18.843 ms 19.023 ms
Click to expand...

This isn't looking great at all :(
Have you tested the Telkom guest account or another ISP to see if the high latency is replicated here? IPC in the East looks good from my end.
 
AfriGuy said:
This isn't looking great at all :(
Have you tested the Telkom guest account or another ISP to see if the high latency is replicated here? IPC in the East looks good from my end.
Click to expand...

Have not yet tested another account yet but ran the test again a few minutes later, now looks much better. The variability is strange, from famine to feast in a few minutes; I wish I knew how to diagnose this because there is no real pattern.


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 91.203 ms 36.264 ms 107.589 ms
4 41.181.221.218 18.204 ms 16.813 ms 17.248 ms
5 41.181.165.118 17.844 ms 18.026 ms 18.308 ms
6 196.44.31.122 47.138 ms 18.708 ms 19.239 ms
7 196.44.0.221 19.369 ms 18.651 ms
196.44.31.97 19.179 ms
8 196.31.220.12 19.367 ms 18.511 ms
Request timed out *
9 196.31.220.27 19.203 ms 18.651 ms
196.31.220.21 18.625 ms
10 196.31.63.202 18.954 ms 17.825 ms 18.244 ms
11 196.30.42.133 18.936 ms 18.097 ms 18.717 ms
12 197.242.144.102 19.107 ms 18.84 ms 18.289 ms


traceroute -n 8.8.8.8

1 192.168.0.1 * * *
2 Request timed out * *
undefined NaN ms
3 41.181.221.217 33.573 ms 19.799 ms
Request timed out *
4 41.181.221.218 17.226 ms 17.813 ms
41.181.221.217 37.794 ms
5 41.181.165.118 17.497 ms 18.036 ms
41.181.221.218 16.949 ms
6 196.44.31.122 18.401 ms 17.933 ms
41.181.165.118 61.121 ms
7 41.181.139.99 18.226 ms
196.44.0.155 17.743 ms
41.181.139.109 17.296 ms
8 72.14.194.74 19.006 ms 18.803 ms
41.181.139.109 17.912 ms
9 72.14.239.33 19.577 ms 18.757 ms
72.14.194.74 19.177 ms
10 8.8.8.8 40.698 ms
72.14.239.35 18.996 ms
Request timed out *
11 8.8.8.8 28.32 ms 22.208 ms
 
Gavin107 said:
Have not yet tested another account yet but ran the test again a few minutes later, now looks much better. The variability is strange, from famine to feast in a few minutes; I wish I knew how to diagnose this because there is no real pattern.


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 91.203 ms 36.264 ms 107.589 ms
4 41.181.221.218 18.204 ms 16.813 ms 17.248 ms
5 41.181.165.118 17.844 ms 18.026 ms 18.308 ms
6 196.44.31.122 47.138 ms 18.708 ms 19.239 ms
7 196.44.0.221 19.369 ms 18.651 ms
196.44.31.97 19.179 ms
8 196.31.220.12 19.367 ms 18.511 ms
Request timed out *
9 196.31.220.27 19.203 ms 18.651 ms
196.31.220.21 18.625 ms
10 196.31.63.202 18.954 ms 17.825 ms 18.244 ms
11 196.30.42.133 18.936 ms 18.097 ms 18.717 ms
12 197.242.144.102 19.107 ms 18.84 ms 18.289 ms


traceroute -n 8.8.8.8

1 192.168.0.1 * * *
2 Request timed out * *
undefined NaN ms
3 41.181.221.217 33.573 ms 19.799 ms
Request timed out *
4 41.181.221.218 17.226 ms 17.813 ms
41.181.221.217 37.794 ms
5 41.181.165.118 17.497 ms 18.036 ms
41.181.221.218 16.949 ms
6 196.44.31.122 18.401 ms 17.933 ms
41.181.165.118 61.121 ms
7 41.181.139.99 18.226 ms
196.44.0.155 17.743 ms
41.181.139.109 17.296 ms
8 72.14.194.74 19.006 ms 18.803 ms
41.181.139.109 17.912 ms
9 72.14.239.33 19.577 ms 18.757 ms
72.14.194.74 19.177 ms
10 8.8.8.8 40.698 ms
72.14.239.35 18.996 ms
Request timed out *
11 8.8.8.8 28.32 ms 22.208 ms
Click to expand...

The second set of results looks better, but the first still sees intermittent latency :(
 
AfriGuy said:
The second set of results looks better, but the first still sees intermittent latency :(
Click to expand...

Yes. Really uncool experience this morning, still really slow ... I think a long walk on the beach will be more productive ;)

200994159.png
 
AfriGuy said:
That isn't great at all :( The latency here looks shocking, do you have a traceroute that I can take a look at?
Click to expand...

Here is the latest. To me this looks like a local exchange issue getting worse by the hour?
I have checked line sync etc - all looks good, sync is about 7mbps on a 10mbps line which is what I normally get. No attenuation or noise problems etc.

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=822 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=606 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=500 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=792 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=899 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=55 time=854 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=55 time=899 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=55 time=870 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=55 time=664 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=55 time=691 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 633.428 ms 674.89 ms
Request timed out *
4 41.181.221.218 610.695 ms 839.694 ms
Request timed out *
5 41.181.165.118 564.684 ms 981.898 ms
Request timed out *
6 Request timed out * *
196.44.31.122 648.362 ms
7 196.44.31.97 909.969 ms 879.576 ms
196.44.0.221 858.09 ms
8 196.31.220.12 850.689 ms
196.30.1.53 947.075 ms 707.56 ms
9 196.31.220.27 800.414 ms 965.502 ms
196.31.220.21 851.207 ms
10 196.31.63.202 864.492 ms 786.399 ms
Request timed out *
11 196.30.42.133 840.382 ms 775.212 ms 903.07 ms
12 197.242.144.102 683.276 ms 371.437 ms 834.658 ms


traceroute -n 8.8.8.8

1 192.168.0.1 * * *
2 Request timed out * * *
3 41.181.221.217 987.915 ms 951.328 ms
Request timed out *
4 41.181.221.218 987.461 ms 954.516 ms
Request timed out *
5 41.181.165.118 816.857 ms 897.383 ms 854.586 ms
6 196.44.0.155 824.713 ms
Request timed out * *
7 41.181.139.99 823.59 ms 994.483 ms
Request timed out *
8 72.14.194.74 976.417 ms
Request timed out * *
9 Request timed out *
72.14.239.33 784.428 ms
72.14.239.35 949.87 ms
10 Request timed out *
8.8.8.8 703.621 ms 915.253 ms
11 8.8.8.8 863.565 ms
 
AfriGuy, I have one suggestion for your site and it stems from my personal desires when needing to top up Mobile data.

I move my money around and by this time of the month I've put my last few Rands in my credit card (in an attempt to reduce charges etc) but then I want to top up my mobile data. Unfortunately I use my cheque account for the monthly automatic deduction which means that when I want to buy a top-up bundle I either have to move money to my cheque account or I have to add my credit card to your system.
The latter is the ideal setup but once I've put in the details the system forces me to select one of the products I have on my account which will then be deducted from my credit card. What I want to do is just have my CC on record and then use that to make the adhoc payments/ purchases rather than being forced to decide what debit orders will be coming off which account.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X