MWEB Uncapped ADSL - Official Q & A

Status
Not open for further replies.
@ penguin - apologise for what? speaking my mind....i don't think so. so the fact that others have the same problem as i do, gets ignored?

anyways ...its back to square one this morning again...
 
mika1000 said:
I hear there's new T&C, maybe it's to force you to stay at least 2 months, as there's rumors of a 100Gb cap all of a sudden. We were suckered again!
Click to expand...

I doubt mweb would start capping, it would be a PR nightmare

intl speed this morning is a total joke pages are just timing out the whole time.
 
Last edited:
Valerion said:
That one's easy. MWeb may decide to get out of the business of offering ADSL. If so, they are allowed to.
Click to expand...

Oh, OK , got it -- they can terminate the entire service rather than an individual subscriber's service. So if they decide in a month's time they made a huge mistake and this uncapped idea is utterly unsustainable, they pack up, turn off the lights on the way out and leave us wondering why our routers won't sync :)
 
semaphore said:
I doubt mweb would start capping, it would be a PR nightmare

intl speed this morning is a total joke pages are just timing out the whole time.
Click to expand...

Semaphore - now do you agree there is a problem? Its public holiday and very minimum of business operate today that requires MWEB to use policy-based routing, fair queing and preferred access-lists but yet the connections is like a 64k ISDN connection. Downloads are flatting at 8k download and 6k upload...what's up with that?

I switch over to my AH prepaid and everything flies along. Switch over to WA capped and everything flies along. MWEB is now Tier1 ISP but yet you getting the connectivity you expect from a Tier3 ISP.

I have nothing against MWEB but I think once again, they have taken the user:speed ratio a little bit too far and it just aint working....
 
bradlesliect said:
Semaphore - now do you agree there is a problem? Its public holiday and very minimum of business operate today that requires MWEB to use policy-based routing, fair queing and preferred access-lists but yet the connections is like a 64k ISDN connection. Downloads are flatting at 8k download and 6k upload...what's up with that?

I switch over to my AH prepaid and everything flies along. Switch over to WA capped and everything flies along. MWEB is now Tier1 ISP but yet you getting the connectivity you expect from a Tier3 ISP.

I have nothing against MWEB but I think once again, they have taken the user:speed ratio a little bit too far and it just aint working....
Click to expand...

Telkom managed to screw up my line when I transferred it back to them, reducing it from 4Mbps to 384. Can't get it resolved until tomorrow when they are back. However, I have quickly downloaded a file this morning (utorrent), and it was running for the whole time between 35 and 40kB/s, which is my normal line limits, from 8:00 to 10:30. I can't see them shaping me more than I would be expecting on a 384. I am definitely not seeing ISDN speeds here.
 
This just in ....

ping www.google.com

Pinging www.l.google.com [74.125.79.147] with 32 bytes of data:
Reply from 74.125.79.147: bytes=32 time=534ms TTL=47
Reply from 74.125.79.147: bytes=32 time=951ms TTL=47
Reply from 74.125.79.147: bytes=32 time=853ms TTL=47
Reply from 74.125.79.147: bytes=32 time=477ms TTL=47

Ping statistics for 74.125.79.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 477ms, Maximum = 951ms, Average = 703ms

tracert www.google.com

Tracing route to www.l.google.com [74.125.79.147]
over a maximum of 30 hops:

1 19 ms 4 ms 6 ms www.routerlogin.com [192.168.0.1]
2 * * * Request timed out.
3 1216 ms 1087 ms 914 ms 196.22.169.146
4 98 ms 158 ms 1067 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 1044 ms 1227 ms 871 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.1
9.241]
6 171 ms 305 ms 83 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219

7 464 ms 329 ms 682 ms ap2522-1-s7-smg.mweb.net [196.22.163.230]
8 1018 ms 328 ms 1277 ms 130.117.136.33
9 517 ms 538 ms 387 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.5
.117]
10 405 ms 355 ms 488 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.4
.153]
11 478 ms 644 ms 383 ms google.lon01.atlas.cogentco.com [130.117.14.90]

12 587 ms 494 ms 518 ms 64.233.175.27
13 782 ms 295 ms 274 ms 72.14.232.149
14 1489 ms 575 ms 880 ms 209.85.255.143
15 282 ms 1098 ms 1183 ms 209.85.255.118
16 357 ms 337 ms 310 ms ey-in-f147.1e100.net [74.125.79.147]

Trace complete.
 
This is pretty much how its been the last few days... absolutely shocking! anyone else have the same prob?
 
bradlesliect said:
This is pretty much how its been the last few days... absolutely shocking! anyone else have the same prob?
Click to expand...

My pings to 74.125.79.147 average around 250ms. The tracepath repeats "no reply" from hop 8 onwards, but I can browse to the IP fine. No idea if it makes a difference, but specifying "www.google.com" does not always result in the same actual IP lookup. I manually specified the IP from your post for my tests.
 
SabreWolfy said:
My pings to 74.125.79.147 average around 250ms. The tracepath repeats "no reply" from hop 8 onwards, but I can browse to the IP fine. No idea if it makes a difference, but specifying "www.google.com" does not always result in the same actual IP lookup. I manually specified the IP from your post for my tests.
Click to expand...

Agreed. The jitter is remarkably low if I have no traffic on my line. Only 10ms between the low and high values.

PING 74.125.79.147 (74.125.79.147) 56(84) bytes of data.
64 bytes from 74.125.79.147: icmp_seq=1 ttl=47 time=251 ms
64 bytes from 74.125.79.147: icmp_seq=2 ttl=47 time=251 ms
64 bytes from 74.125.79.147: icmp_seq=3 ttl=47 time=252 ms
64 bytes from 74.125.79.147: icmp_seq=4 ttl=47 time=252 ms
64 bytes from 74.125.79.147: icmp_seq=5 ttl=47 time=252 ms
64 bytes from 74.125.79.147: icmp_seq=6 ttl=47 time=253 ms
64 bytes from 74.125.79.147: icmp_seq=7 ttl=47 time=251 ms
64 bytes from 74.125.79.147: icmp_seq=8 ttl=47 time=261 ms
64 bytes from 74.125.79.147: icmp_seq=9 ttl=47 time=259 ms
64 bytes from 74.125.79.147: icmp_seq=10 ttl=47 time=251 ms

--- 74.125.79.147 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8998ms
rtt min/avg/max/mdev = 251.297/253.801/261.393/3.455 ms

traceroute to 74.125.79.147 (74.125.79.147), 30 hops max, 40 byte packets
2 * * *
3 196.22.169.158 (196.22.169.158) 51.403 ms 61.023 ms 70.699 ms
4 vl-92.vic-hscore-2.mweb.co.za (196.22.189.3) 80.980 ms 90.633 ms 100.316 ms
5 tengig-0-0-0-0-12.vic-up-1.mweb.co.za (196.22.169.241) 117.470 ms 127.522 ms 137.190 ms
6 tengig-0-2-0-0.mid-1.mweb.co.za (196.22.169.219) 140.721 ms 156.492 ms 160.065 ms
7 ap2522-1-s7-smg.mweb.net (196.22.163.230) 388.643 ms 351.993 ms 357.311 ms
8 130.117.136.33 (130.117.136.33) 351.653 ms 351.012 ms 351.080 ms
9 te1-2.ccr02.lon02.atlas.cogentco.com (130.117.50.117) 351.124 ms 343.505 ms 343.251 ms
10 te7-2.mpd02.lon01.atlas.cogentco.com (130.117.0.97) 343.840 ms 349.459 ms 343.325 ms
11 google.lon01.atlas.cogentco.com (130.117.14.90) 356.201 ms 251.324 ms 245.897 ms
12 64.233.175.27 (64.233.175.27) 242.482 ms 249.575 ms 256.392 ms
13 72.14.232.149 (72.14.232.149) 268.018 ms 267.907 ms 269.873 ms
14 209.85.255.166 (209.85.255.166) 269.647 ms 275.764 ms 209.85.255.143 (209.85.255.143) 278.516 ms
15 209.85.255.130 (209.85.255.130) 279.100 ms 209.85.255.122 (209.85.255.122) 271.235 ms 209.85.255.130 (209.85.255.130) 266.950 ms
16 ey-in-f147.1e100.net (74.125.79.147) 263.580 ms 267.848 ms 268.625 ms
 
Last edited:
i dunno hey...these results appear to sporadic....The MWEB rep doesnt appear to be online anymore either? wonder where he/she went? using speedtest.net to do some tests and each time the result is different for local and int....

....guess, i'm just going to leave it...will check forums and change ISP to one where I am going to get value for buck...
 
bradlesliect said:
i dunno hey...these results appear to sporadic....The MWEB rep doesnt appear to be online anymore either? wonder where he/she went? using speedtest.net to do some tests and each time the result is different for local and int....

....guess, i'm just going to leave it...will check forums and change ISP to one where I am going to get value for buck...
Click to expand...

Give him (her?) a break -- s/he's been online quite a lot over this long weekend already :)

Results will vary depending on many factors between source and destination. ADSL is a "best effort" service and many factors are out of MWeb's control. It's unlikely speed and ping test results will always be the same; depends on what variance in results you are talking about though.

MWeb is a tier 1 operator with access via the SeaCom cable. I'm not sure how much better you could do, but I'm sure everyone here would be interested in your results from other ISPs on the same physical ADSL.
 
Last edited:
bradlesliect said:
i dunno hey...these results appear to sporadic....The MWEB rep doesnt appear to be online anymore either? wonder where he/she went? using speedtest.net to do some tests and each time the result is different for local and int....

....guess, i'm just going to leave it...will check forums and change ISP to one where I am going to get value for buck...
Click to expand...

This is a public holiday, of course? I wouldn't expect the MWeb rep to do work stuff today. And he'll be catching up once he gets back, as I am sure this is not his only job. For me this is bang for my buck, so for the moment I am staying.
 
In Pta and it's flying the whole weekend. Happy, very happy with Mweb's uncapped.
 
SabreWolfy said:
Results will vary depending on many factors between source and destination. ADSL is a "best effort" service and many factors are out of MWeb's control. It's unlikely speed and ping test results will always be the same; depends on what variance in results you are talking about though.

MWeb is a tier 1 operator with access via the SeaCom cable. I'm not sure how much better you could do, but I'm sure everyone here would be interested in your results from other ISPs on the same physical ADSL.
Click to expand...
Hi SabreWolfy,

Thanks, couldn't have said it better myself.

Only additional info I can add is, we experienced another local fibre break this morning, traffic is being re-routed via the diverse path.

MWB.
 
no offense to anyone here ...but all i've been seeing from MWEB over the last 24hrs or so are excuses... blaming it on one problem then the next...why have none of these been posted on a notices page anywhere for everyone to see? surely you value your clients that to much to at least post something for them to look at or at least be aware of?

just my 2c worth...
 
Hi bradlesliect,

Is there something specific I can assist you with on YOUR service?

MWB.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X