MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
Anyone else just lose all connectivity for a few minutes?

Glad I am back up now, hope it was just a temporary glitch. And +1 to NNTP running like trash the last week.

This best not interfere with mah Diablo 3 madness! And now the stress test of GW2 on Monday night /drool
 
Been with MWEB for over a year now and I have to say the last few days I've noticed a general slow down. Browsing seems more sluggish, torrents are slower. Not good.....
 
Telkoms National Backhaul starting to feel the pressure of the 30% reduction in IPC pricing, ISP's buying more capacity with the lower price means more data throughput required, maybe? Mweb guy....

Must agree, speeds have been shocking this last week....
 
Good MOrning Everyone

Please refer to the following response to torrents speeds, that was provided to you earlier this month by @Will.

We are aware of your experiance at the moment and we are trying to replicate it on our side.

Hi Everyone

I see there has been a bit of discussion about torrent speeds in the last few days.

Torrent speeds are never guaranteed and will fluctuate through the day and can even differ from day to day depending on the network load. I know the speeds have been excellent for the last few months, but please remember that this is a shaped product and torrent traffic has the lowest priority so you simply can't expect that experience to remain constant.

The good news is that we did add a little bandwidth onto the fire yesterday so there will hopefully be some improvement and we are expecting a substantial upgrade on the 1st of June.

For the torrenters I would however recommend that you don't speed watch - it is a shaped product and you should rather look at what you're downloading over the course of the month to determine if you're getting value for money, rather than how fast it's going right this minute.

Regards
Will
 
Last edited:
I've gotta praise Mweb / Mweb Guy

PMed Mweb guy yesterday re: my line order that had been "in progress" on Telkom's side for 10 working days. Mweb guy Pm'ed me back within an hour. Within 2 huors I had a call from Mweb telling me the matter had been escalated. Within 4 hours, the line installation was complete and my internet was good to go.

Great work guys
 
Sacoys said:
I've gotta praise Mweb / Mweb Guy

PMed Mweb guy yesterday re: my line order that had been "in progress" on Telkom's side for 10 working days. Mweb guy Pm'ed me back within an hour. Within 2 huors I had a call from Mweb telling me the matter had been escalated. Within 4 hours, the line installation was complete and my internet was good to go.

Great work guys
Click to expand...

Thanks for the complement Sacoys :D

Glad you had great service!!
 
venom said:
Everything has been pretty crappy for a few days now. 1 mb line.

Mweb Uncapped 1mb:



On my Web Africa prepaid:
Click to expand...

Good MOrning Venom, please provide me your MWEB email address via direct message.
 
MWEB Guy said:
Good MOrning Everyone

Please refer to the following response to torrents speeds, that was provided to you earlier this month by @Will.

We are aware of your experiance at the moment and we are trying to replicate it on our side.

Hi Everyone

I see there has been a bit of discussion about torrent speeds in the last few days.

Torrent speeds are never guaranteed and will fluctuate through the day and can even differ from day to day depending on the network load. I know the speeds have been excellent for the last few months, but please remember that this is a shaped product and torrent traffic has the lowest priority so you simply can't expect that experience to remain constant.

The good news is that we did add a little bandwidth onto the fire yesterday so there will hopefully be some improvement and we are expecting a substantial upgrade on the 1st of June.

For the torrenters I would however recommend that you don't speed watch - it is a shaped product and you should rather look at what you're downloading over the course of the month to determine if you're getting value for money, rather than how fast it's going right this minute.

Regards
Will
Click to expand...

Just an addon to this I have been monitoring this myself and I have seen torrent speeds of around 60-70kB during the day, in the 150KB region early evening and late night speeds of 350kB+.

This is on a 4mb shaped product, tested both from our test bench at the office and my own line.

So my questions would be:

Is this more, or less in line with what you guys are experiencing?

Does it differ drastically from your expectation of how a shaped 4mb product at this pricepoint should be performing for p2p traffic?


Also just an aside note on the erratic nature of torrent performance that must be taken into account:

On my late night test I initially saw speeds jumping up and down around the 90-100KB mark. I noted that the file in question had in the region of 25 active seeds and 2 active peers.

I monitored this for about 5 minutes with no change until the number of active peers jumped up to 4 and the throughput almost instantly tripled.
 
froot said:
Hi Mweb Guy

Any network issues today?
My Mweb account is maxing out (local and intl and on http/nntp, etc) at about 60KB/s (1mb line). I am unable to complete a speedtest.
My latencies and traceroutes are normal though.
I checked with my Afrihost account and speeds are normal, so it's not my line.
Click to expand...

Good Day froot, we have no reported network issues at the moment. The 60KB/s speeds you are obtaining is not bad for p2p at this time of day.

Which http content have you tested your speeds with, perhaps I can try and replicate at out testing station.
 
MWEB Guy said:
Good Day froot, we have no reported network issues at the moment. The 60KB/s speeds you are obtaining is not bad for p2p at this time of day.

Which http content have you tested your speeds with, perhaps I can try and replicate at out testing station.
Click to expand...

I don't do p2p :sick:

I tested using Windows updates and a Firefox download.
I limit my nntp to 30KB/s during the day but tested at speed, and it maxes out (both news.mweb.co.za and free.xsusenet.com (which always always maxes out)) at 65KB/s.

http://dl.dropbox.com/u/21762292/firefox_down.png : My firefox download

Edit: Testing with Firefox(mirror.ac.za) and it's also ~ 60-65KB/s.
 
froot said:
I don't do p2p :sick:

I tested using Windows updates and a Firefox download.
I limit my nntp to 30KB/s during the day but tested at speed, and it maxes out (both news.mweb.co.za and free.xsusenet.com (which always always maxes out)) at 65KB/s.

http://dl.dropbox.com/u/21762292/firefox_down.png : My firefox download

Edit: Testing with Firefox(mirror.ac.za) and it's also ~ 60-65KB/s.
Click to expand...

Ok, thanks for the feedback. I have changed a setting on your account now and it is not gauranteed to have an effect. However please do a router reboot and let me know if it has any impact.
 
MWEB Guy said:
Ok, thanks for the feedback. I have changed a setting on your account now and it is not gauranteed to have an effect. However please do a router reboot and let me know if it has any impact.
Click to expand...

Nope, no change.
Don't worry about it for now, I will see how it is tonight. I don't "need" the speed now.
 
MWEB Guy ... I'm back! There is definitely a problem somewhere. I have had my port recreated, my exchange checked (its not congested) This is after all the above:

Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=592ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=36ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=108ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Request timed out.
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=42ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=45ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=37ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=57ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
Reply from 196.2.63.110: bytes=32 time=36ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=223ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=34ms TTL=119
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X