Weird Problem on Mweb Uncapped

[TheGuy]

Whenever I use torrents on the 384 Uncapped package it completely kills my browsing. I keep getting page times and pages not loading correctly.

I would understand if the Torrents are maxing my line but during the day they only run at about 2 KBps because of the shaping. Then as soon as I pause all the torrents and reload the web page browsing is fine. It seems that as soon as Mweb detects Torrents it kills my connection completely.


Does anybody else get this?

 

[Gtx Gaming]

think it could be router problem.maxing connections that router can handle

 

[Brenden_E]

Yup, same thing. Annoying as hell.

 

[TheGuy]

think it could be router problem.maxing connections that router can handle

So it doesn't happen to you?

 

[Diesal]

Change the amount of connections allowed in your bit torrent client?

 

[Brenden_E]

No there's something funky with their shaping during the day. When you run a torrent, even at 1kb/s on a 4mb line everything goes to haywire. Suddenly latency increases as well.

 

[havoc]

Do any of you think that throttling of torrents ins't going to happen? Of course they're going to throttle you as long as the Record/Movie companies are threatening them (and their CLIENT's (They're probably too scared to stand up to their CLIENT's rights)). If that is affecting your browsing then look to MWEB. They are probably too lazy to throttle you by bandwidth instead of protocol!

Besides, Uncapped does not == without limitations

 

[Brenden_E]

Havoc what on earth are you talking about. Throttling of torrents during the day is normal, but for some reason it seems to affect the other protocols.
That's the issue.

 

[TheGuy]

Havoc what on earth are you talking about. Throttling of torrents during the day is normal, but for some reason it seems to affect the other protocols.
That's the issue.

That's exactly it.

 

[zeyad 001]

I would Suggest using a alternate protocol Like Http or Nttp.It is much more realible.