Afrihost Uncapped ADSL Feedback (Pt2)

Status
Not open for further replies.
Hush9300 said:
My theory is that the lack of relief in terms of shaping is causing even more congestion at the IPC link because the downloads just don't finish.
Click to expand...

I do see your point, but the shaping is needed to keep the network running with enough headroom :)
 
Hush9300 said:
People in general are impatient and they want to watch the latest episodes of their favourite series ASAP.

I do all my torrent downloads overnight now, only the odd one during peak.
Click to expand...

Haha, I know. But I have RSS which download my "Linux distros ;)" as soon as they are released, which is always overnight.
 
Type RSA said:
Come on AfriGuys, Offer me the 10mb Business Uncapped account at the home uncapped account price until the shaping is fixed... I will then move over to the home uncapped account once the shaping is gone. Please :) LOL
Click to expand...

From what I can remember you're on a Business account though where there is no shaping...
I'm afraid we can't offer what you're suggesting :(
 
Hush9300 said:
I understand that it is a necessary evil but it seems to be causing congestion.
Click to expand...

Hhhmm, I'm not 100% sure though.
Let's say everyone is downloading OSX Mavericks today, it's 5 odd GB. We obviously can't let everyone max out their lines so we shape, meaning the download will take a bit longer.

Now I see where you're coming from, this means the download time will be extended. When the network has calmed itself down a bit we'll slowly but surely start opening the taps and everyones downloads will start picking up speed.
Remember that IPC networks run off a Gbps model as opposed to how much total traffic is consumed. If that makes sense?
 
Some more congestion on your Gauteng IPC:
Code: 
tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     2 ms     9 ms     5 ms  192.168.0.1
  2    17 ms     8 ms     9 ms  105.236.3.*
  3   120 ms   117 ms   158 ms  41.181.178.77
  4   129 ms   129 ms   124 ms  196.44.0.146
  5   111 ms   111 ms   111 ms  196.44.31.171
  6    91 ms    88 ms    90 ms  41.181.165.115
  7   108 ms   124 ms   125 ms  72.14.194.74
  8   311 ms   296 ms   312 ms  72.14.232.102
  9   419 ms   423 ms   416 ms  216.239.43.42
 10   429 ms   437 ms   437 ms  216.239.43.233
 11   326 ms   272 ms   275 ms  209.85.252.83
 12     *        *        *     Request timed out.
 13   300 ms   312 ms   305 ms  8.8.8.8

Trace complete.

tracert -d www.mybb.co.za

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

  1     1 ms     2 ms     4 ms  192.168.0.1
  2    16 ms    12 ms    44 ms  105.236.3.*
  3   123 ms   125 ms   124 ms  41.181.178.89
  4   132 ms     *      129 ms  196.44.31.120
  5   122 ms   124 ms   133 ms  196.44.0.42
  6   133 ms   144 ms   130 ms  41.181.165.115
  7   316 ms   327 ms   325 ms  195.69.144.210
  8   344 ms   350 ms   345 ms  77.109.140.26
  9   341 ms   342 ms   345 ms  77.109.135.102
 10     *      326 ms   327 ms  213.239.245.25
 11   324 ms   322 ms   313 ms  213.239.245.70
 12   340 ms   333 ms   338 ms  213.239.193.243
 13   320 ms   330 ms   332 ms  213.133.106.183

Trace complete.
 
kripstoe said:
What do you mean saving on their (uncapped?) bandwidth at home? Most companies won't tolerate torrents. Most people have no idea how the underlying technology of p2p works. They just use it 24/7 without knowing the impact. Which then leads to: should they know the impact of it? Or should AH manage it sufficiently so that it doesn't impact other clients.
Click to expand...

Well, this is the debate we have now. We find so many business clients (like companies, not the product) have trouble controlling the usage on their networks, and complain that their business functions are impaired and we have to point to their networks. So I think there would be some value in them being able to ask us to switch torrents off (for example) so that their employees don't crash their networks or eat up bandwidth so that everyone else's skype and mail is affected.

It's just an idea, but it's something that has been mentioned before :)
 
Type RSA said:
Come on AfriGuys, Offer me the 10mb Business Uncapped account at the home uncapped account price until the shaping is fixed... I will then move over to the home uncapped account once the shaping is gone. Please :) LOL
Click to expand...

I would love to, if it were up to me :)

In fact, if it were up to me no-one would pay for bandwidth - this may be why my management status is still pending :(
 
Guys, we know that there is a latency issue in the Northern region.

Our team are working on this and we're hoping to see results very soon. I'll keep you updated from my own monitoring. For now we're not looking great :(
 
grim said:
Some more congestion on your Gauteng IPC:
Code: 
tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     2 ms     9 ms     5 ms  192.168.0.1
  2    17 ms     8 ms     9 ms  105.236.3.*
  3   120 ms   117 ms   158 ms  41.181.178.77
  4   129 ms   129 ms   124 ms  196.44.0.146
  5   111 ms   111 ms   111 ms  196.44.31.171
  6    91 ms    88 ms    90 ms  41.181.165.115
  7   108 ms   124 ms   125 ms  72.14.194.74
  8   311 ms   296 ms   312 ms  72.14.232.102
  9   419 ms   423 ms   416 ms  216.239.43.42
 10   429 ms   437 ms   437 ms  216.239.43.233
 11   326 ms   272 ms   275 ms  209.85.252.83
 12     *        *        *     Request timed out.
 13   300 ms   312 ms   305 ms  8.8.8.8

Trace complete.

tracert -d www.mybb.co.za

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

  1     1 ms     2 ms     4 ms  192.168.0.1
  2    16 ms    12 ms    44 ms  105.236.3.*
  3   123 ms   125 ms   124 ms  41.181.178.89
  4   132 ms     *      129 ms  196.44.31.120
  5   122 ms   124 ms   133 ms  196.44.0.42
  6   133 ms   144 ms   130 ms  41.181.165.115
  7   316 ms   327 ms   325 ms  195.69.144.210
  8   344 ms   350 ms   345 ms  77.109.140.26
  9   341 ms   342 ms   345 ms  77.109.135.102
 10     *      326 ms   327 ms  213.239.245.25
 11   324 ms   322 ms   313 ms  213.239.245.70
 12   340 ms   333 ms   338 ms  213.239.193.243
 13   320 ms   330 ms   332 ms  213.133.106.183

Trace complete.
Click to expand...

I'm really sorry about this :(
Latency should have normalised by now. Did you run the traceroute at the time of posting?
 
AfriGuy said:
I'm really sorry about this :(
Latency should have normalised by now. Did you run the traceroute at the time of posting?
Click to expand...

Yep, stil seeing excessive latency now.

Code: 
tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     8 ms     6 ms     3 ms  192.168.0.1
  2     8 ms    10 ms     8 ms  105.236.3.*
  3   133 ms   135 ms   138 ms  41.181.178.77
  4   130 ms   128 ms   132 ms  196.44.0.146
  5   130 ms   143 ms   136 ms  196.44.31.171
  6   167 ms   166 ms   163 ms  41.181.165.115
  7   133 ms   141 ms   159 ms  72.14.194.74
  8   306 ms   314 ms   312 ms  72.14.232.102
  9   463 ms   454 ms   454 ms  216.239.43.42
 10   446 ms   465 ms   458 ms  216.239.43.233
 11   334 ms   320 ms   327 ms  72.14.238.215
 12     *        *        *     Request timed out.
 13   327 ms   323 ms   327 ms  8.8.8.8

Trace complete.

tracert -d www.mybb.co.za

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

  1     2 ms     1 ms     2 ms  192.168.0.1
  2    10 ms     8 ms     8 ms  105.236.3.*
  3   168 ms   161 ms     *     41.181.178.89
  4   124 ms     *      122 ms  196.44.31.120
  5   153 ms   139 ms   138 ms  196.44.0.42
  6   155 ms   154 ms   159 ms  41.181.165.115
  7   346 ms   359 ms   347 ms  195.69.144.210
  8   348 ms   326 ms   326 ms  77.109.140.26
  9   341 ms   347 ms   336 ms  77.109.135.102
 10   326 ms   324 ms   324 ms  213.239.245.25
 11   334 ms   331 ms   329 ms  213.239.245.70
 12   332 ms   323 ms   334 ms  213.239.193.243
 13   301 ms   299 ms   599 ms  213.133.106.183

Trace complete.
 
grim said:
Yep, stil seeing excessive latency now.

Code: 
tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     8 ms     6 ms     3 ms  192.168.0.1
  2     8 ms    10 ms     8 ms  105.236.3.*
  3   133 ms   135 ms   138 ms  41.181.178.77
  4   130 ms   128 ms   132 ms  196.44.0.146
  5   130 ms   143 ms   136 ms  196.44.31.171
  6   167 ms   166 ms   163 ms  41.181.165.115
  7   133 ms   141 ms   159 ms  72.14.194.74
  8   306 ms   314 ms   312 ms  72.14.232.102
  9   463 ms   454 ms   454 ms  216.239.43.42
 10   446 ms   465 ms   458 ms  216.239.43.233
 11   334 ms   320 ms   327 ms  72.14.238.215
 12     *        *        *     Request timed out.
 13   327 ms   323 ms   327 ms  8.8.8.8

Trace complete.

tracert -d www.mybb.co.za

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

  1     2 ms     1 ms     2 ms  192.168.0.1
  2    10 ms     8 ms     8 ms  105.236.3.*
  3   168 ms   161 ms     *     41.181.178.89
  4   124 ms     *      122 ms  196.44.31.120
  5   153 ms   139 ms   138 ms  196.44.0.42
  6   155 ms   154 ms   159 ms  41.181.165.115
  7   346 ms   359 ms   347 ms  195.69.144.210
  8   348 ms   326 ms   326 ms  77.109.140.26
  9   341 ms   347 ms   336 ms  77.109.135.102
 10   326 ms   324 ms   324 ms  213.239.245.25
 11   334 ms   331 ms   329 ms  213.239.245.70
 12   332 ms   323 ms   334 ms  213.239.193.243
 13   301 ms   299 ms   599 ms  213.133.106.183

Trace complete.
Click to expand...

It looks like it's spiked up again, our team are doing everything they can to have this sorted :(
 
So the time has come for us too decide: Stay or leave?

Tomorrow is the 25th. So make your decision quickly.

I'm waiting a bit. Moving into a house in January that is less than 500m away from the exchange. Currently over 5km away.
 
I'm considering moving down to a lower speed, but changing to the business package, for november
 
pjjdp said:
So the time has come for us too decide: Stay or leave?

Tomorrow is the 25th. So make your decision quickly.

I'm waiting a bit. Moving into a house in January that is less than 500m away from the exchange. Currently over 5km away.
Click to expand...

I know it's hard, but I hope you guys decide to stick it out. I mentioned earlier, I'm confident that we'll bounce back from this :)
And for your sake, I hope you move 500m away from an MSAN and get no less than 39.99Mbps VDSL :D
 
AfriGuy said:
I know it's hard, but I hope you guys decide to stick it out. I mentioned earlier, I'm confident that we'll bounce back from this :)
And for your sake, I hope you move 500m away from an MSAN and get no less than 39.99Mbps VDSL :D
Click to expand...

unfortunately even on a 50mb line he will only get 36 with your account
 
I found this ironic on the AH site
Does Afrihost have enough capacity to satisfy it's client's needs?
When we changed networks, we ordered over 30% additional network capacity to ensure we had sufficient bandwidth available. However when it became clear that our client's bandwidth needs had grown (possibly due to Telkom upgrades over the October/November period) we immediately ordered additional capacity from Telkom. We are waiting for this to be installed by them, and we have made all the necessary upgrades on our side to ensure we can make full use of the additional capacity as soon as it arrives end of February 2013.
Click to expand...
Time for some more capacity. Let's hope by December I can switch back to a Home package
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X