MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Oh
My
Word.............

News server is terrible. WTF!!!!!!!!!!!!!!!!!!!!!!!!!

I can't go on like this, if it isn't worted out by tomorrow evening, goodbye MWEB. The end. I will go to Openweb Gold for the extra dosh per month.

Edit : Torrents going fine again now. News server is chugging along. Wow... first time i have seen 40kb on a torrent in like a month!
 
Last edited:
Why move to another service, i pay them so they must give me what i am paying them. it like buying a car,what will you do if you buy a car like a ferrari and thinking that you will get 300km/h only get 160 because they have a problem with the fuel comany so you must now be satisfied with that and not top speeds. I am not trying to incite some sort of "coo", but users need to stand up against companies that only cares about the monthly debit order and nothing else.

This is old, trodden over territory, while I understand your frustration, this is not really the place to talk about threatening MWEB.That will definitely not get you the results you are looking for.
 
Connection is up to crap again tonight. Blizzard updater is downloading a 1.4 gig patch at TEN K A SECOND... on a four meg line! RIDICULOUS!
 
Damnit! Why not me?!

My line syncs at 3 Mbps and I used to get excellent speed.

Try this test - download this file - its from a local mirror and via HTTP (30mb). Use a download manager with 4 or 5 threads - you should get full line speed. If not then its a problem with your line as Mweb do not shape this.

http://opensuse.mirror.ac.za/opensuse/distribution/11.3/repo/oss/ARCHIVES.gz

If you get full speed and then you get poor speed on NNTP - then its simple. They're shaping your nntp.
 
Try this test - download this file - its from a local mirror and via HTTP (30mb). Use a download manager with 4 or 5 threads - you should get full line speed. If not then its a problem with your line as Mweb do not shape this.

http://opensuse.mirror.ac.za/opensuse/distribution/11.3/repo/oss/ARCHIVES.gz

If you get full speed and then you get poor speed on NNTP - then its simple. They're shaping your nntp.

more than likely, but why then do some people get good NNTP speed, and others bad. I cannot fothom it, unless they on the "unshaped" business deal.
 
Semaphore, legal costs will never get to 600m+, that i can tell you now. the bad publicity will be enough to harm mweb. And besides if someone does not take on them, Mweb users will just be milked even further by Mweb. Also i dont own Big Companies for nothing. I have enough money to take mweb on and have money left over to enjoy life.

Wow I have never heard such a giant pile of BS in my life. I wouldn't be surprised if this is a stunt by one of the other ISP's or a marketing company, "send us your details and we will sue the big bad company for you", next week you get a phonecall from Jan Hendrik's ISP " sir we got your number from a company and heard you wanted interwebz".

I kinda forgot rule 1 though, don't feed the trolls!
 
Mweb needs to be sued and taken to Court for giving a false service, i believe they call it Fraud when you pretend to give something and then not deliver that service but still take the money.

You are kidding right??!! You haven't read the t&c's I guess
 
Maybe they put users/locations in different shaping groups?

I was thinking the same, but why would that be useful?
I did another little experiment, but maybe it's just pure chance. I tested Astraweb, which ran quite well, about 45 to 50 kBps, nothing to complain about for a 512 package. Then using Supernews I get 20 to 30 kBps, dropping as low as 10 kBps, both tests running 15 connections.

I then did both tests using my WA account, and they ran at more or less the same speed. Is it possible that on the MWEB network Astraweb is given priority over Supernews? I don't even know if that is possible or even dooable, but would be nice to find an answer.
 
Don't take them on. Just cancel the service and move to another provider. While you are paying them, lol, why should they care.
 
It's physically possible but I seriously doubt they would do that.

No idea, like I said, might have just been chance.
I guess I'm just getting frustrated with the inconsistancy. Maybe give it a few more days to see how it pans out, then consider other alternatives if need be.
 
Hi Everyone

I thought this might be useful in terms of dispeling any doubts about the fact that there are definitely ADSL infrastructure issues which need to be addressed. The following three tracerts were taken immediately after each other in an area which has been problematic since around the time the 10mb upgrades started, the line itself shows solid readings and has been cleared as not faulty.

2010/10/13 10:06pm Trace to www.telkom.co.za using Internet Solutions

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

1 143 ms 66 ms 121 ms 196-209-24-1.dynamic.isadsl.co.za [196.209.24.1]

2 207 ms 203 ms 195 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
3 177 ms 185 ms 175 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
4 224 ms 212 ms 189 ms 196.26.0.61
5 213 ms 212 ms 209 ms 168.209.1.179
6 220 ms 204 ms 191 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.46.8
9]
7 195 ms 192 ms 200 ms 196.43.25.137
8 209 ms 208 ms 201 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.166]
9 181 ms 179 ms 183 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
10 208 ms 196 ms 193 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
11 188 ms 194 ms 203 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

2010/10/13 10:08pm Trace to www.telkom.co.za using WebAfrica

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

1 28 ms 28 ms 29 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
2 68 ms 25 ms 27 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
3 20 ms 28 ms 28 ms vl35.er.gw.cpt.za.wa.co.za [41.185.0.38]
4 177 ms 183 ms * upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.23
0]
5 203 ms 201 ms 208 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.4
3.11.166]
6 193 ms 266 ms 483 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]

2010/10/13 10:10pm Trace to www.telkom.co.za using MWEB

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

1 27 ms 19 ms 19 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
2 167 ms 174 ms 180 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202]

3 196 ms 194 ms 201 ms 196.22.169.41
4 213 ms 225 ms 259 ms 196.22.169.61
5 213 ms 221 ms 212 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 195 ms 201 ms 191 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 267 ms 269 ms 267 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.
43.8.146]
8 201 ms 187 ms 191 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
9 218 ms 221 ms 231 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
10 187 ms 182 ms 181 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
7 187 ms 189 ms 195 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
8 197 ms 202 ms 204 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

The same experience is being reported by users on at least 4 exchanges in the affected area and I now (finally) have confirmation indicating that there is a faulty link which has been cleared of traffic so that it can be repaired without disruption. ETA unknown at this time.

Kind Regards
Will
 
yes acidrain I recieved a response very late this afternoon.

**EDIT**

Please could you post your current readings in the latency thread to add to my response
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X