MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
MWEB Guy said:
Hi Sillicur,

Pelase note that I have replicated your pings and tracert results on our test bench. I have sent them to our network team for some assistance.

Kind regards, MWEB Guy
Click to expand...

Mweb Guy, you replicated them yourself, you said so yourself. So there is an issue. Now your telling me your network team cannot replicate it (aka you are completely lying, no other way around it.) It does not happen the whole time but it does happen almost each day for a few hours. Look at the last few pages and you can see a bunch of people also complaining about timeouts.

But just look at your quote, then to your last message right now. All you tell us is that your network team cannot replicate it, nothing about other steps that will be taken. You replicated the timeout issue on your test bench, you said so yourself. You said so a few pages ago. So that is 100% purely lying to us. That is not even something that might be a mistake.

So come on, tell us, everyone reading this how you will explain or just ignore it this time.

I am waiting eagerly for your generic /useless response you will come up with this time.
 
MWEB Guy said:
Hi Sillicur,

Our network team could not replicate the timeouts you getting.

Kind regards,

MWEB Guy
Click to expand...

I am of course talking about this post after like a week of waiting and after the quoted message above.
 
Just a note. If you run torrents on your PC and then try to use Steam, its port somehow gets added to the p2p shaping pool. This I found was often the cause for my slow steam speeds. The only way to fix it is to redial the connection with your torrents turned off.

Perhaps this is something you can look into MWEB Guy?
 
It is getting worse for me:
Code: 
PING google.com (74.125.233.16) 56(84) bytes of data.
64 bytes from 74.125.233.16: icmp_req=2 ttl=53 time=1021 ms
64 bytes from 74.125.233.16: icmp_req=3 ttl=53 time=854 ms
64 bytes from 74.125.233.16: icmp_req=4 ttl=53 time=982 ms
64 bytes from 74.125.233.16: icmp_req=5 ttl=53 time=918 ms
64 bytes from 74.125.233.16: icmp_req=6 ttl=53 time=1104 ms
64 bytes from 74.125.233.16: icmp_req=7 ttl=53 time=1707 ms
64 bytes from 74.125.233.16: icmp_req=8 ttl=53 time=1629 ms
64 bytes from 74.125.233.16: icmp_req=9 ttl=53 time=1387 ms
64 bytes from 74.125.233.16: icmp_req=10 ttl=53 time=1231 ms
64 bytes from 74.125.233.16: icmp_req=11 ttl=53 time=1252 ms
64 bytes from 74.125.233.16: icmp_req=13 ttl=53 time=1722 ms
64 bytes from 74.125.233.16: icmp_req=14 ttl=53 time=1429 ms
--- google.com ping statistics ---
15 packets transmitted, 12 received, 20% packet loss, time 24912ms
rtt min/avg/max/mdev = 854.441/1270.117/1722.255/293.479 ms, pipe 2
20% packet loss and not to speak of the latency... I could cry.
 
MyWorld said:
It is getting worse for me:
Code: 
PING google.com (74.125.233.16) 56(84) bytes of data.
64 bytes from 74.125.233.16: icmp_req=2 ttl=53 time=1021 ms
64 bytes from 74.125.233.16: icmp_req=3 ttl=53 time=854 ms
64 bytes from 74.125.233.16: icmp_req=4 ttl=53 time=982 ms
64 bytes from 74.125.233.16: icmp_req=5 ttl=53 time=918 ms
64 bytes from 74.125.233.16: icmp_req=6 ttl=53 time=1104 ms
64 bytes from 74.125.233.16: icmp_req=7 ttl=53 time=1707 ms
64 bytes from 74.125.233.16: icmp_req=8 ttl=53 time=1629 ms
64 bytes from 74.125.233.16: icmp_req=9 ttl=53 time=1387 ms
64 bytes from 74.125.233.16: icmp_req=10 ttl=53 time=1231 ms
64 bytes from 74.125.233.16: icmp_req=11 ttl=53 time=1252 ms
64 bytes from 74.125.233.16: icmp_req=13 ttl=53 time=1722 ms
64 bytes from 74.125.233.16: icmp_req=14 ttl=53 time=1429 ms
--- google.com ping statistics ---
15 packets transmitted, 12 received, 20% packet loss, time 24912ms
rtt min/avg/max/mdev = 854.441/1270.117/1722.255/293.479 ms, pipe 2
20% packet loss and not to speak of the latency... I could cry.
Click to expand...

Please send me your MWEB details so that I can investigate further.

Regards
MWEB Guy
 
Isengard said:
Just a note. If you run torrents on your PC and then try to use Steam, its port somehow gets added to the p2p shaping pool. This I found was often the cause for my slow steam speeds. The only way to fix it is to redial the connection with your torrents turned off.

Perhaps this is something you can look into MWEB Guy?
Click to expand...

Hmmm... Surely, even if it was shaped it wouldn't be this slow. Also, there are other people in my house using the internet, surely I don't have to ask them all to close their torrent clients and reboot my router every time I want to play a game?
 
My unapped 384k connection also drops randomly then I get kicked off games and can't browse the internet. Anyone else having problems
 
Last edited:
Yes tardomatic, yes you do.

If there are torrents downloading on your network, YOUR LINE WILL GET SHAPED. This will then affect ANY other internet based connections you are using (youtube/games etc etc)

I have a habit now of stopping torrents whenever I want to jam online games. This is the main area for me where I encounter issues with latency/bandwidth/speed. I don't care to stop a torrent, if I am browsing the net though.

EDIT: Just to clarify, I don't restart my router. I just stop the torrents from downloading. After a short interval (the time it takes to click stop, then run the game/application), my internet usually goes back to normal.
 
Last edited:
smokemaryjane said:
Yes tardomatic, yes you do.

If there are torrents downloading on your network, YOUR LINE WILL GET SHAPED. This will then affect ANY other internet based connections you are using (youtube/games etc etc)

I have a habit now of stopping torrents whenever I want to jam online games. This is the main area for me where I encounter issues with latency/bandwidth/speed. I don't care to stop a torrent, if I am browsing the net though.

EDIT: Just to clarify, I don't restart my router. I just stop the torrents from downloading. After a short interval (the time it takes to click stop, then run the game/application), my internet usually goes back to normal.
Click to expand...
You are confusing shaping with throttling.

Your line is always shaped, in the case of Mweb, on certain protocols. The ISP might on some occasions (like over week-ends or at night) relax their shaping policy. What shaping does is give priority to certain protocols while taking priority away from others. Your http traffic should almost always be around full line speed while your torrents will be a hit and miss depending on the ISP shaping policy.

Throttling is when you have a 4 meg line that should in theory give you 420kbps, but the ISP set a "speed limit" on your account for whatever reason and now you get for instance only 100kbps. Hence you are throttled.

Having torrents open while gaming reduces your bandwidth (it is shared between the torrents and the game client) and you WILL experience incredible lag and latency.
 
MyWorld said:
You are confusing shaping with throttling.

Your line is always shaped, in the case of Mweb, on certain protocols. The ISP might on some occasions (like over week-ends or at night) relax their shaping policy. What shaping does is give priority to certain protocols while taking priority away from others. Your http traffic should almost always be around full line speed while your torrents will be a hit and miss depending on the ISP shaping policy.

Throttling is when you have a 4 meg line that should in theory give you 420kbps, but the ISP set a "speed limit" on your account for whatever reason and now you get for instance only 100kbps. Hence you are throttled.

Having torrents open while gaming reduces your bandwidth (it is shared between the torrents and the game client) and you WILL experience incredible lag and latency.
Click to expand...

Ah ok, let me rephrase: If you run torrents, while trying to do any other online activity, YOU WILL GET THROTTLED. :)
Basically, if I run a torrent in the background, and then try to play WoW. I will get anywhere between 2.5k ms and 20k ms lag. Stopping the torrents takes me back to sub 200ms ping in WoW. Same for other games.
 
smokemaryjane said:
Ah ok, let me rephrase: If you run torrents, while trying to do any other online activity, YOU WILL GET THROTTLED. :)
Basically, if I run a torrent in the background, and then try to play WoW. I will get anywhere between 2.5k ms and 20k ms lag. Stopping the torrents takes me back to sub 200ms ping in WoW. Same for other games.
Click to expand...

Not in my case. I stop my torrent (note: close uTorrent completely). Somehow the Steam port is still flagged as p2p after this and can only be fixed by redialing the connection, I usually just do a PPPoE connection in windows.

After this Steam goes back up to full speed.

Note that this only happens on Steam and some MMO games, any other HTTP download runs as normal.
 
Hi i am looking at getting my self the 4mb line uncaped with the first 3 months free... now i was wondering how much will i be able to download cause on my currunt 384 line i am downloading about 60gig a month :/ and how bad will shaping be cause i also do alot of gaming :) ???????


also sent a email from the mweb site but stil no-reply will call today :/
 
My line was upgraded to 1Mb yesterday and my account was upgraded to 1Mb this morning. Yet I am still receiving the same speeds as if I am on 384k. With another ISP account I get the full 1Mb speed. Could you maybe reset my account or something please? I have tried turning my router off for a while with no improvement.

http://www.speedtest.net/result/1415350320.png

Edit: My line is syncing at 1024k and the MWEB site does confirm I have a 1Mb account.
 
Sillicur said:
Mweb Guy, you replicated them yourself, you said so yourself. So there is an issue. Now your telling me your network team cannot replicate it (aka you are completely lying, no other way around it.) It does not happen the whole time but it does happen almost each day for a few hours. Look at the last few pages and you can see a bunch of people also complaining about timeouts.

But just look at your quote, then to your last message right now. All you tell us is that your network team cannot replicate it, nothing about other steps that will be taken. You replicated the timeout issue on your test bench, you said so yourself. You said so a few pages ago. So that is 100% purely lying to us. That is not even something that might be a mistake.

So come on, tell us, everyone reading this how you will explain or just ignore it this time.

I am waiting eagerly for your generic /useless response you will come up with this time.
Click to expand...

Sillicur said:
I am of course talking about this post after like a week of waiting and after the quoted message above.
Click to expand...

So, obviously you ignored the post Mweb Guy. This should be clear to everyone because you replied to a bunch of other posts just below it. To see the quotes i am referring too, see middle of page 1002. I will re-post this every day till it is addressed.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X