MWEB Uncapped ADSL Feedback - Part 3

Dubes said:
MWeb, I read, or perhaps dreamt, that soft caps were being reviewed on the uncapped standard accounts. Is this so?

Either way, what is the soft cap on the 2Mbps and 4Mbps uncapped standard accounts at the moment? I've got them at 70Gb and 110Gb.
Click to expand...

MWEB Guy said:
Hi Dubes, those amounts are accurate.
Click to expand...

Dubes said:
Thanks.

Next question if I may. I am running close to the 70Gb 30 day rolling amount on my 2Mbps uncapped. I am considering upgrading to the 4Mbps service not for the line speed (my 2Mbps line is with Telkom but I may consider a move to you) but the higher cap. If I did when would it take effect and when would I enjoy the higher cap from?
Click to expand...

MWEB Guy said:
As you have a data only account with us the upgrade will be quick within an hour to be activated
Click to expand...

@MWEB Guy, all this singing of MWeb's praises and I've just been a tad annoyed with my interaction on the phone now. The conversation quoted above refers.

As suspected I did hit my soft cap and was throttled. I phoned MWEB to ask that just my package be upgraded to 4Mbps, as discussed above, to benefit from the 110GB softcap as opposed to the 70GB. My line, once again as discussed, would stay with Telkom at 2Mbps.

The call centre agent stated they cannot do this. He then said they can but my line will be erratic and possibly unusable. He suggested I upgrade to premium or upgrade my line which will take 5 to 10 days to complete.

This obviously left me annoyed. Prior to being throttled I was proactive and still confirmed my options with you and whether it was possible and whether I'd instantly benefit. You confirmed I would.

Please advise?


The call centre agent did try and argue that you may have been referring to a line upgrade too but I clearly state my line is with Telkom and I am happy with this. The immediate benefit seems to support the argument that we were on the same page as the line upgrade would not be immediate.




To the other technical fundis on here: Does it make sense that a 4Mbps package from your ISP being used on a 2Mbps Telkom provided line will result in connectivity issues?
 
Last edited:
Dubes said:
To the other technical fundis on here: Does it make sense that a 4Mbps package from your ISP being used on a 2Mbps Telkom provided line will result in connectivity issues?
Click to expand...

Nope, but you should just PM MWEB Guy to kindly upgrade you, no phone call needed - at least for me. ;)
 
PostmanPot said:
Nope, but you should just PM MWEB Guy to kindly upgrade you, no phone call needed - at least for me. ;)
Click to expand...

While I was on hold I did wonder what the hell I was doing! :D

I failed to see how it would cause an issue myself but the call centre agent said he can provide me with a list of clients who experience problems.
 
Dubes said:
@MWEB Guy, all this singing of MWeb's praises and I've just been a tad annoyed with my interaction on the phone now. The conversation quoted above refers.

As suspected I did hit my soft cap and was throttled. I phoned MWEB to ask that just my package be upgraded to 4Mbps, as discussed above, to benefit from the 110GB softcap as opposed to the 70GB. My line, once again as discussed, would stay with Telkom at 2Mbps.

The call centre agent stated they cannot do this. He then said they can but my line will be erratic and possibly unusable. He suggested I upgrade to premium or upgrade my line which will take 5 to 10 days to complete.

This obviously left me annoyed. Prior to being throttled I was proactive and still confirmed my options with you and whether it was possible and whether I'd instantly benefit. You confirmed I would.

Please advise?


The call centre agent did try and argue that you may have been referring to a line upgrade too but I clearly state my line is with Telkom and I am happy with this. The immediate benefit seems to support the argument that we were on the same page as the line upgrade would not be immediate.




To the other technical fundis on here: Does it make sense that a 4Mbps package from your ISP being used on a 2Mbps Telkom provided line will result in connectivity issues?
Click to expand...

Hi Dubes

I'm really sorry about the misunderstanding, I will arrange for a consultant to call you and assist with the upgrade.
The account should be unthrottled and the connection should be fine.
 
MWEB Guy said:
Hi Dubes

I'm really sorry about the misunderstanding, I will arrange for a consultant to call you and assist with the upgrade.
The account should be unthrottled and the connection should be fine.
Click to expand...

Thanks.

I'm willing to test it. If it doesn't work I'll then look at the line speed upgrade but I'm keen to get unthrottled for the weekend.


But the way, just for the record and benefit of others, the throttle is still usable, just not able to stream but can still keep working.
 
Dubes said:
Thanks.

I'm willing to test it. If it doesn't work I'll then look at the line speed upgrade but I'm keen to get unthrottled for the weekend.


But the way, just for the record and benefit of others, the throttle is still usable, just not able to stream but can still keep working.
Click to expand...

Thanks, your feedback is noted and similar comments have been passed to the relevant persons.
For now the account will remain as is but if any changes are made to the product we'll be sure to let our clients know.
 
Jeez, the amount of international packet loss since about 12:30am is massive. I hope MWEB is on to this.

The below tracert only tells half the story. On PingPlotter, the amount of packet loss shows around 40 - 70%, effectively slowing down international connectivity, with the added irritation of having to continuously refresh web pages until they load properly. Not to mention using latency sensitive applications.

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 29 ms 32 ms 20 ms 41-135-192-1.dsl.mweb.co.za [41.135.192.1]
3 32 ms 23 ms 21 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 25 ms 19 ms 27 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 41 ms 39 ms 33 ms tengig-0-0-0-2-11-cpt-p-1.mweb.co.za [197.84.5.2
25]
6 43 ms 36 ms 61 ms tengig-0-0-0-0-vic-p-2.mweb.co.za [197.84.4.35]

7 58 ms 51 ms 61 ms 197-80-7-37.jhb.mweb.co.za [197.80.7.37]
8 58 ms 65 ms 39 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 * 266 ms 281 ms 66.249.95.8
10 * 224 ms 246 ms 209.85.244.240
11 * 260 ms 268 ms 209.85.249.209
12 270 ms 255 ms 258 ms 72.14.239.98
13 * * * Request timed out.
14 281 ms * 248 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
 
FraserBlade said:
Jeez, the amount of international packet loss since about 12:30am is massive. I hope MWEB is on to this.

The below tracert only tells half the story. On PingPlotter, the amount of packet loss shows around 40 - 70%, effectively slowing down international connectivity, with the added irritation of having to continuously refresh web pages until they load properly. Not to mention using latency sensitive applications.

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 29 ms 32 ms 20 ms 41-135-192-1.dsl.mweb.co.za [41.135.192.1]
3 32 ms 23 ms 21 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 25 ms 19 ms 27 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 41 ms 39 ms 33 ms tengig-0-0-0-2-11-cpt-p-1.mweb.co.za [197.84.5.2
25]
6 43 ms 36 ms 61 ms tengig-0-0-0-0-vic-p-2.mweb.co.za [197.84.4.35]

7 58 ms 51 ms 61 ms 197-80-7-37.jhb.mweb.co.za [197.80.7.37]
8 58 ms 65 ms 39 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 * 266 ms 281 ms 66.249.95.8
10 * 224 ms 246 ms 209.85.244.240
11 * 260 ms 268 ms 209.85.249.209
12 270 ms 255 ms 258 ms 72.14.239.98
13 * * * Request timed out.
14 281 ms * 248 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
Click to expand...

Hi FraserBlade, send me a PM with your MWEB details and I will look into this for you
 
The after hours service offered by MWeb must be applauded. I'm sure other ISPs might provide similar service but my experience is with them.

It has become expected in the ISP market but what other industry would assist your after 6pm on a Friday. I had an issue. Sent a PM on here and received a call to resolve the issue shortly thereafter at 6.25pm last night.

I am now able to stream the rugby this afternoon! Any other industry, and possibly other ISPs, and I would've been waiting until the offices opened on Monday.

Thanks.
 
FraserBlade said:
Jeez, the amount of international packet loss since about 12:30am is massive. I hope MWEB is on to this.

The below tracert only tells half the story. On PingPlotter, the amount of packet loss shows around 40 - 70%, effectively slowing down international connectivity, with the added irritation of having to continuously refresh web pages until they load properly. Not to mention using latency sensitive applications.

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 29 ms 32 ms 20 ms 41-135-192-1.dsl.mweb.co.za [41.135.192.1]
3 32 ms 23 ms 21 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 25 ms 19 ms 27 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 41 ms 39 ms 33 ms tengig-0-0-0-2-11-cpt-p-1.mweb.co.za [197.84.5.2
25]
6 43 ms 36 ms 61 ms tengig-0-0-0-0-vic-p-2.mweb.co.za [197.84.4.35]

7 58 ms 51 ms 61 ms 197-80-7-37.jhb.mweb.co.za [197.80.7.37]
8 58 ms 65 ms 39 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 * 266 ms 281 ms 66.249.95.8
10 * 224 ms 246 ms 209.85.244.240
11 * 260 ms 268 ms 209.85.249.209
12 270 ms 255 ms 258 ms 72.14.239.98
13 * * * Request timed out.
14 281 ms * 248 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
Click to expand...

Having the exact same issue's FraserBlade, packet loss all over the show and also using pingplotter to monitor it, I'm in the Gordons bay region not to far from you
 
rpdblu said:
Having the exact same issue's FraserBlade, packet loss all over the show and also using pingplotter to monitor it, I'm in the Gordons bay region not to far from you
Click to expand...

Hi

Please see my reply to your PM.
 
SYNERGY said:
Also experiencing alot of packet loss... Durban.
Click to expand...

Hi SYNERGY

Could you please PM me your account info and I will look into this from my side.
There aren't any reported network issues at the moment that I'm aware of.
 
Morning

Something horrible broken on mweb this morning... Everything is slow and international is virtually non existent..

as shown by the traceroute below.

C:\WINDOWS\System32>tracert google.com

Tracing route to google.com [197.80.128.45]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 8 ms 8 ms 7 ms 197-87-143-1.cpt.mweb.co.za [197.87.143.1]
3 9 ms 9 ms 8 ms 197-84-96-210.cpt.mweb.co.za [197.84.96.210]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
Yeah, I'm having the exact same problem as fbman. Woke up this morning, and my international (and local, to a lesser extent) is screwed up; slow connectivity, if at all. Most services (Like Dropbox, for instance) cannot connect at all.
 
another tracert

C:\WINDOWS\System32>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 7 ms 7 ms 7 ms 197-87-143-1.cpt.mweb.co.za [197.87.143.1]
3 10 ms 9 ms 8 ms 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
4 9 ms 9 ms 9 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 155 ms 153 ms 154 ms tengig-0-0-0-2-11-cpt-p-1.mweb.co.za [197.84.5.2
25]
6 155 ms 158 ms 153 ms w1-pos0-3-1-0-pos-0-3-5-0-thd-p-2.mweb.co.za [19
7.84.4.227]
7 190 ms 185 ms 188 ms be-3-779-thd-up-1.mweb.co.za [176.67.177.227]
8 153 ms 153 ms 156 ms ldn-b5-link.telia.net [62.115.13.13]
9 153 ms 153 ms 162 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
10 * * * Request timed out.
11 * * * Request timed out.
12 155 ms 153 ms 154 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
13 156 ms 155 ms 156 ms 132.185.255.165
14 154 ms 154 ms 154 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

Trace complete.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X