MWEB Uncapped ADSL Feedback - Part 3

Hi Convex, the throttling on our premium accounts will only take place from September.

Tell me what sorts of downloads are you doing when you get these speeds.

I'm confused. So please be so kind as to clarify this for me.

I've been with Mweb for a couple of months now. I'm not 1meg premium and my downloads have ranged from 90GB a month down to about 40-50GB a month.

I did NOT receive a letter.

So here's my question. Would I still be able to proceed with my current usage patterns (as per the previous months history) without any throttling taking place. Or are the usual levels being dropped.

That whole 3% nonsense means nothing to me. I need real world clear answers.
 
Hi Convex, the throttling on our premium accounts will only take place from September.

Tell me what sorts of downloads are you doing when you get these speeds.

Stop lying you have been throttling us for months while you tested the new throttling software there are no other real reason for the poor performance up to Monday last week. All the excuses you made up was a farce and it's now clear what "refreshing your account" means Suddenly since Monday last week, just after your dubious throttling announcement, everything went much better even torrents and gaming apart from the lag spikes still coming through. Nothing changed on my side at all.

Alas it's to late I canceled and cannot wait for my Mweb experience to expire after many years of pumping money in Mweb.

FSCK Mweb and their useless CEO.
 
Last edited:
@MWebGuy - another day gone by (10 in total) since my cancellation and your staff has still been incapable of migrating my line back to Telkom (which does not take more than 72 hours). To pass the buck to Telkom and now having me do the run-a-round is absolutely unacceptable. Mweb says it's Telkom's responsibility and Telkom says that they are waiting for Mweb - so now what?

Once again - get someone to sort out migration back to Telkom and take responsibility and accountability of such a simple task. This goes beyond incompetence.
 
@MWebGuy - another day gone by (10 in total) since my cancellation and your staff has still been incapable of migrating my line back to Telkom (which does not take more than 72 hours). To pass the buck to Telkom and now having me do the run-a-round is absolutely unacceptable. Mweb says it's Telkom's responsibility and Telkom says that they are waiting for Mweb - so now what?

Once again - get someone to sort out migration back to Telkom and take responsibility and accountability of such a simple task. This goes beyond incompetence.

Hi MagicDude4Eva

Thanks for the feedback, I'll follow up on this and provide you with feedback as soon as I receive it.
 
Hey Mweb Guy.

No melodramatics here but Mweb's service and attitude to customers is now unacceptable.

Could you please inform me of the procedure to drop my account to a 1gig capped for next month (Sep) and then how to cancel at the end of next month.
 
Last edited:
Hey Mweb Guy.

No melodramatics here but Mweb's service and attitude to customers is now unacceptable.

Could you please inform me of the procedure to drop my account to a 1gig capped for next month (Sep) and then how to cancel at the end of next month.

Hi,

Please let me know if you still require assistance with downgrading your account.


EDIT: I managed to find your account and see that you have already contacted us to process the downgrade.
 
So if I change my account to 1GB does that mean I don't have to pay the usual fee at the end of this month and just pay for the 1GB package?
 
Hi, your account is not throttled, send me a trace route to a local and international site.

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

1 2 ms 2 ms 2 ms READYSHARE [10.0.0.1]
2 3 ms 2 ms 2 ms 192.xxx.x.x
3 147 ms 146 ms 120 ms 41-133-120-1.dsl.mweb.co.za [41.xxx.xxx.1]
4 753 ms 314 ms 339 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
5 148 ms * 72 ms vl-92.vic-hscore-2.mweb.co.za [197.80.2.2]
6 154 ms 121 ms 96 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [197.80.5.24
2]
7 * 120 ms 67 ms tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

8 261 ms 582 ms 840 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
9 853 ms 710 ms 305 ms 196.28.178.66
10 84 ms 83 ms 85 ms cte-core-sw2.vwol.net [196.41.144.35]
11 118 ms 112 ms 138 ms www.mweb.co.za [196.2.63.110]

Tracing route to google.co [74.125.233.64]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms READYSHARE [10.0.0.1]
2 3 ms 2 ms 2 ms 192.xxx.x.x
3 793 ms 715 ms 1209 ms 41-133-120-1.dsl.mweb.co.za [41.xxx.xxx.1]
4 1205 ms 811 ms 795 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
5 688 ms 655 ms 1407 ms vl-92.vic-hscore-1.mweb.co.za [197.80.2.1]
6 1187 ms 1140 ms 1075 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za [197.80.5.22
5]
7 724 ms 888 ms 793 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
8 884 ms 1058 ms 1039 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 1105 ms 1095 ms * 64.233.174.57
10 1016 ms 1021 ms 1294 ms jnb01s02-in-f0.1e100.net [74.125.233.64]

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

1 2 ms 2 ms 2 ms READYSHARE [10.0.0.1]
2 3 ms 2 ms 2 ms 192.xxx.x.x
3 147 ms 146 ms 120 ms 41-133-120-1.dsl.mweb.co.za [41.xxx.xxx.1]
4 753 ms 314 ms 339 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
5 148 ms * 72 ms vl-92.vic-hscore-2.mweb.co.za [197.80.2.2]
6 154 ms 121 ms 96 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [197.80.5.24
2]
7 * 120 ms 67 ms tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]

8 261 ms 582 ms 840 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
9 853 ms 710 ms 305 ms 196.28.178.66
10 84 ms 83 ms 85 ms cte-core-sw2.vwol.net [196.41.144.35]
11 118 ms 112 ms 138 ms www.mweb.co.za [196.2.63.110]

Tracing route to google.co [74.125.233.64]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms READYSHARE [10.0.0.1]
2 3 ms 2 ms 2 ms 192.xxx.x.x
3 793 ms 715 ms 1209 ms 41-133-120-1.dsl.mweb.co.za [41.xxx.xxx.1]
4 1205 ms 811 ms 795 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
5 688 ms 655 ms 1407 ms vl-92.vic-hscore-1.mweb.co.za [197.80.2.1]
6 1187 ms 1140 ms 1075 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za [197.80.5.22
5]
7 724 ms 888 ms 793 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
8 884 ms 1058 ms 1039 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 1105 ms 1095 ms * 64.233.174.57
10 1016 ms 1021 ms 1294 ms jnb01s02-in-f0.1e100.net [74.125.233.64]

Trace complete.

Looking at these traces, I see it spiking as early as the 3rd hop.

This usually points to a congested exchange.
 
Looking at these traces, I see it spiking as early as the 3rd hop.

This usually points to a congested exchange.

The latest defacto excuse. Funny that this only occurred today again since last week Monday. I was actually considering to cancel my cancelation. A horror thought.

Maybe you are right after all I will see when my new ISP activates and I will let you know.
 
Hi,

Please let me know if you still require assistance with downgrading your account.


EDIT: I managed to find your account and see that you have already contacted us to process the downgrade.

Yes thanks for the effort anyway, just gave the call center a ring and was sorted in 5min...
 
Top
Sign up to the MyBroadband newsletter
X