MWEB Uncapped ADSL Feedback - Part 3

[Fudzy]

Yes. 14 years ago I was running a profitable business. Today I am still busy and still profitable. The management principles are the same as are the business principles. The thing I was doing then, and the thing I do now are coincidental to the fact that I exist to make money. And as Ray Kroc says "look after the customer and the business will look after itself".

So you've never had abusive customers? Also, why weren't you on a business package if you were running a business?

 

[F1ve_Claw]

And still having international issues.

Int:
Does not even finish preparing the download test

Local:
Download Speed: 4207 kbps (525.9 KB/sec transfer rate)
Upload Speed: 411 kbps (51.4 KB/sec transfer rate)
Latency: 49 ms
Thursday, November 07, 2013 1:48:06 PM

So as we can see, there is something wrong with the international.

 

[Fudzy]

And still having international issues.

Int:
Does not even finish preparing the download test

Local:
Download Speed: 4207 kbps (525.9 KB/sec transfer rate)
Upload Speed: 411 kbps (51.4 KB/sec transfer rate)
Latency: 49 ms
Thursday, November 07, 2013 1:48:06 PM

So as we can see, there is something wrong with the international.

Just RDP'd into my machines at home, no issues on my side. Anyone else?

 

[SabreWolfy]

I've never said that.

Perhaps I phrased it badly. You indicated that you had returned to MWEB because all ISPs implement some form of bandwidth management. This was in reply to my question as to why you had returned to MWEB.

 

[MWEBHelp]

And still having international issues.

Int:
Does not even finish preparing the download test

Local:
Download Speed: 4207 kbps (525.9 KB/sec transfer rate)
Upload Speed: 411 kbps (51.4 KB/sec transfer rate)
Latency: 49 ms
Thursday, November 07, 2013 1:48:06 PM

So as we can see, there is something wrong with the international.

We are not having any issues on our side with international traffic. There have been no trends as well regarding this.

 

[Fudzy]

Perhaps I phrased it badly. You indicated that you had returned to MWEB because all ISPs implement some form of bandwidth management. This was in reply to my question as to why you had returned to MWEB.

Perhaps you were trolling? Either that or you seem to have a bad track record of typing before thinking.

 

[F1ve_Claw]

We are not having any issues on our side with international traffic. There have been no trends as well regarding this.

I understand that, but how do you explain this?

Download Speed: 37 kbps (4.6 KB/sec transfer rate)
Upload Speed: 88 kbps (11 KB/sec transfer rate)
Latency: 224 ms
Thursday, November 07, 2013 1:54:29 PM

It's simple. There is something wrong with my international. local is 100% perfect. Everyone else's may be fine, but mine is not sadly

 

[MWEBHelp]

I understand that, but how do you explain this?

Download Speed: 37 kbps (4.6 KB/sec transfer rate)
Upload Speed: 88 kbps (11 KB/sec transfer rate)
Latency: 224 ms
Thursday, November 07, 2013 1:54:29 PM

It's simple. There is something wrong with my international. local is 100% perfect. Everyone else's may be fine, but mine is not sadly

I hear you F1ve_Claw

Please change the realm of the username from @mweb.co.za to @dslmweb.co.za and test again. Please let me know how things are after that.

 

[Fudzy]

I understand that, but how do you explain this?

Download Speed: 37 kbps (4.6 KB/sec transfer rate)
Upload Speed: 88 kbps (11 KB/sec transfer rate)
Latency: 224 ms
Thursday, November 07, 2013 1:54:29 PM

It's simple. There is something wrong with my international. local is 100% perfect. Everyone else's may be fine, but mine is not sadly

Are you using the same test server each time?

 

[F1ve_Claw]

I hear you F1ve_Claw

Please change the realm of the username from @mweb.co.za to @dslmweb.co.za and test again. Please let me know how things are after that.

Done and no change

Are you using the same test server each time?

Yup using the international one on mbb. Can't use the speedtest.net as it just takes too long to load

Edit: Maybe my exchange is messed. Still weird that local is fine :\


Tracing route to cnn-56m.gslb.vgtf.net [157.166.248.10]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 * 9 ms 11 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 10 ms 12 ms 12 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 82 ms 11 ms 10 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 * 217 ms 206 ms 176.67.177.131
6 200 ms 198 ms * xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
7 379 ms 283 ms 283 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166
.153]
8 289 ms 289 ms 290 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]

9 288 ms 288 ms 288 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

10 295 ms 286 ms * ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
11 * 291 ms * ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
12 * 289 ms 288 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
13 334 ms 288 ms 288 ms ae-1-51.edge2.Atlanta4.Level3.net [4.69.150.17]

14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.

 

[TEXTILE GUY]

Morning Fudzy

As you know, all I can do is pass this along the channels. Whether this suggestion is seen as a good idea, we will have to just hang ten a bit more

Let's hope common sense prevails, because despite what anyone says, the complaints on this throttling policy have been streaming in consistently. And, you can hate me, call me a troll, hate the other contributors to this discussion, and even have a go at Fudzy, albeit his idea IMHO is a good one.

The truth is, we are the ones voicing an opinion, we are or were affected by this policy and are the voice of the customer. And, as I have said before, I would prefer to be with MWEB for various reasons.

I do hope the bosses at MWEB take the dialogue seriously and do some adaptive business planning accordingly. I make this comment sincerely even if I am persona non grata with MWEB. ...or anyone else for that matter.

 

[new_in_za2]

So what's MWEB's game-plan? They are protecting their network and to 97%+ users. How come other ISPs don't have these problems?

I'm not understanding why one of the largest players in the market is enforcing their AUP so much more aggressively than other (smaller?) ISPs.

I really get the feeling that a lot of you have never used any other ADSL ISP in South Africa...

 

[MWEBHelp]

Done and no change



Yup using the international one on mbb. Can't use the speedtest.net as it just takes too long to load

Edit: Maybe my exchange is messed. Still weird that local is fine :\


Tracing route to cnn-56m.gslb.vgtf.net [157.166.248.10]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 * 9 ms 11 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 10 ms 12 ms 12 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 82 ms 11 ms 10 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 * 217 ms 206 ms 176.67.177.131
6 200 ms 198 ms * xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
7 379 ms 283 ms 283 ms vl-3603-ve-227.csw2.London1.Level3.net [4.69.166
.153]
8 289 ms 289 ms 290 ms ae-58-223.ebr2.London1.Level3.net [4.69.153.137]

9 288 ms 288 ms 288 ms ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

10 295 ms 286 ms * ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
11 * 291 ms * ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
12 * 289 ms 288 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
13 334 ms 288 ms 288 ms ae-1-51.edge2.Atlanta4.Level3.net [4.69.150.17]

14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.

Afternoon, rather trace to a more secure website like bbc.co.uk and mweb.co.za

If your exchange is congested the trace route should show high latency on the 2nd or 3rd hop.

 

[new_in_za2]

Just RDP'd into my machines at home, no issues on my side. Anyone else?

I tried the test too, and in fact I'm getting the result of 1087kbps on a 1024kbps account

 

[F1ve_Claw]

Afternoon, rather trace to a more secure website like bbc.co.uk and mweb.co.za

If your exchange is congested the trace route should show high latency on the 2nd or 3rd hop.

Here you go:

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

1 1 ms 1 ms 1 ms 10.0.0.2
2 10 ms 10 ms 10 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 11 ms 11 ms 11 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 11 ms 11 ms 15 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 * * 46 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
6 46 ms 48 ms 49 ms 196.28.178.66
7 47 ms 47 ms 46 ms cte-core-sw2.vwol.net [196.41.144.35]
8 47 ms 46 ms 58 ms www.mweb.co.za [196.2.63.110]

Trace complete.

and


Tracing route to www.bbc.net.uk [212.58.244.69]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 9 ms 9 ms 9 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 12 ms 11 ms 10 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 12 ms 11 ms 11 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 * * * Request timed out.
6 199 ms * 198 ms ldn-b5-link.telia.net [62.115.13.13]
7 220 ms 202 ms 215 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
8 * * * Request timed out.
9 203 ms 203 ms 203 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 * * * Request timed out.
11 199 ms 199 ms 198 ms www.bbc.co.uk [212.58.244.69]

Trace complete.

 

[MWEBHelp]

Here you go:

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

1 1 ms 1 ms 1 ms 10.0.0.2
2 10 ms 10 ms 10 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 11 ms 11 ms 11 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 11 ms 11 ms 15 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 * * 46 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
6 46 ms 48 ms 49 ms 196.28.178.66
7 47 ms 47 ms 46 ms cte-core-sw2.vwol.net [196.41.144.35]
8 47 ms 46 ms 58 ms www.mweb.co.za [196.2.63.110]

Trace complete.

and


Tracing route to www.bbc.net.uk [212.58.244.69]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 9 ms 9 ms 9 ms 41-133-72-1.dsl.mweb.co.za [41.133.72.1]
3 12 ms 11 ms 10 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 12 ms 11 ms 11 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 * * * Request timed out.
6 199 ms * 198 ms ldn-b5-link.telia.net [62.115.13.13]
7 220 ms 202 ms 215 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
8 * * * Request timed out.
9 203 ms 203 ms 203 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 * * * Request timed out.
11 199 ms 199 ms 198 ms www.bbc.co.uk [212.58.244.69]

Trace complete.

These trace routes don't seem that bad.

Provide me speed test results using saix.net please. I will also private message you the Telkom guest account details for comparative results.

 

[TEXTILE GUY]

So you've never had abusive customers? Also, why weren't you on a business package if you were running a business?

There's a lot of assumptions in that comment..... None the less, I will give you something to chat about seeing as you had the decency to answer me.
1. Yes I have had and still do have abusive customers. Where the abuse makes business sense, I would address the issues, after all without customers, there is no business. It's one of those basic things one learns in business 101. Depends on how you define abuse ....
2. My business account is with WA, not MWEB, always has been. MWEB was my home account, always was. I choose not to mix the two as one was convenient for the IT guy, the other convenient for me.

 

[F1ve_Claw]

These trace routes don't seem that bad.

Provide me speed test results using saix.net please. I will also private message you the Telkom guest account details for comparative results.

Seems I'm having the same issue with a telkom account as well as an afrihost one. spdtst.saix.net tests take forever to do the download test, regardless of location,but latency is fine - sub 50's for all

 

[Seriously]

If constructive criticism is considered fanboyism then what you guys are doing is considered emotionally immature trolling.

That's a new one!

 

[Seriously]

So, if someone uses more than half of available bandwidth, you call him an abuser? Because you throttled me without any warning (I have received your letter of abuse exactly the week after you started throttling me) just as I crossed half of theoretically-practically possible amount of data that I could download. Not even half! my total usage was about 125GB, and that includes both upload and download, while if I would be downloading at full speed 24/7 the whole month, I could pull 250GB only on downoads. What is the exact definition of abuser in the eyes of MWEB? Please answer to this Mweb Guy?

I can help you there!

Definition of a Mweb Abuser:

Any Mweb Customer that uses his Internet facility the way Mweb advertised their product to snag you as a victim to their services for a minimum of a two month period. Once enrolled and you use the Internet normally as anyone in the world would you are immediately branded an abuser and you will be throttled down do 56K dialup speeds on all protocols even e-mails and speedtests.

Whether you get the 1M,4M or 10M standard package you are only allowed to browse, check emails and do some small things. YOU ARE NOT ALLOWED TO DOWNLOAD or change your pattern of use! The ONLY differences in those packages are the speed for doing the same. YOU are not allowed to do GAMING!

There you have it. Very clear. Better to do the best thing and that is to talk with your wallet and let your fingers do the walking through the yellow pages to another ISP.