MWEB Uncapped ADSL - Official Q & A

[Milano]

Just wish to compliment MWeb on an excellent service and the MWeb rep for making himself available on this forum, keep it up guys!

 

[bradlesliect]

Hi bradlesliect,

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

MWB.

Hi MWEB,

Thanks for YOUR concern- no sarcasm intended - but all I want is for an ISP to deliver on the service they promised, keep in touch with your clients and provide feedback re outages, problems, etc.

Could you finally admit there is a problem and that is not started in the last 24hrs? tell me how I/we can help you in delivering excellent service? This is where I admire WA, the test,test,test and then test again before unleashing to all users.

have a look at the traceroute below...and this is with nothing currently happening on my line. What's up with this? Even connecting to your news server is extremely slow and some times non existent.

tracert www.mybroadband.co.za

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

1 3 ms 3 ms 4 ms www.routerlogin.com [192.168.0.1]
2 * * * Request timed out.
3 838 ms 986 ms 1113 ms 196.22.169.134
4 636 ms 521 ms 530 ms 196.22.189.3
5 238 ms 205 ms 64 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 284 ms 502 ms 117 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.11
0.73]
7 278 ms 471 ms 707 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
8 * 869 ms 552 ms 196.43.25.138
9 1060 ms 393 ms 1291 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
10 * 233 ms 50 ms 196.30.1.21
11 317 ms 465 ms 655 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 544 ms 496 ms 206 ms 196.30.213.108
13 427 ms 44 ms 47 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 480 ms 171 ms 233 ms mybroadband.co.za [41.203.21.136]

Trace complete.

 

[bradlesliect]

ok.... think i'm just going to be quiet from here on... i think that i'm prolly annoying everyone more than anything else.

Before I go let me say this
1. No problem with my router - tried another router(Cisco ADSL Router) and problem still the same
2. No problem with my firewall(smoothwall)
3. No problem with ADSL line ( Telkom tested about 4x in the last few days)
4. No probs when connecting via another ISP - capped account

With that being said, I will now sit back and become an observer on this forum.

 

[SabreWolfy]

<snip>

tracert www.mybroadband.co.za

Tracing route to www.mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:
3 ms 3 ms 4 ms www.routerlogin.com [192.168.0.1]
2 * * * Request timed out.
3 838 ms 986 ms 1113 ms 196.22.169.134
4 636 ms 521 ms 530 ms 196.22.189.3
5 238 ms 205 ms 64 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 284 ms 502 ms 117 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.11
0.73]
7 278 ms 471 ms 707 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
8 * 869 ms 552 ms 196.43.25.138
9 1060 ms 393 ms 1291 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
10 * 233 ms 50 ms 196.30.1.21
11 317 ms 465 ms 655 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 544 ms 496 ms 206 ms 196.30.213.108
13 427 ms 44 ms 47 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 480 ms 171 ms 233 ms mybroadband.co.za [41.203.21.136]

Trace complete.

What's your point? Here's mine:

 2:  192.168.1.254 (192.168.1.254)                          0.540ms pmtu 1492
 2:  41-132-16-1.dsl.mweb.co.za (41.132.16.1)             124.188ms 
 3:  196.22.169.158 (196.22.169.158)                      121.098ms asymm  4 
 4:  vl-92.vic-hscore-2.mweb.co.za (196.22.189.3)         121.874ms asymm  5 
 5:  tengig-0-0-0-0-12.vic-up-1.mweb.co.za (196.22.169.241) 149.982ms asymm  6 
 6:  rndf-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.110.73) 125.782ms asymm  7 
 7:  rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za (196.43.8.198) 120.119ms asymm  9 
 8:  196.43.25.138 (196.43.25.138)                        122.580ms asymm  9 
 9:  ge0-2.br1.jnb6.za.mtnbusiness.net (196.30.16.181)    122.849ms asymm 10 
10:  ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22)   127.864ms asymm 11 
11:  vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136)   131.211ms asymm 12 
12:  196.30.213.108 (196.30.213.108)                      129.965ms asymm 14 
13:  firewall1.jnb2.host-h.net (196.7.216.173)            125.885ms asymm 14 
14:  mybroadband.co.za (41.203.21.136)                    134.845ms reached
     Resume: pmtu 1492 hops 14 back 50

The MWeb rep. discussed in this forum why there are so many local hops.

The "Internet" is a dynamic beast -- packets may be routed differently from one occasion to the next. Run your tracepath 10 times over an hour period and post all the resuts to a paste bin site and then we can determine if there is a problem.

If your equipment is fine and your line is fine and everything else is fine and OTHER MWeb users are fine, then I'm not sure where the problem is. I think it may be premature to "blame" MWeb based on a tracepath output. I'm pretty sure MWeb is not deliberately sabotaging their own users or intentionally disrupting their service

What do you no problem with another capped ISP account? What's the tracepath from that account?

 

[SabreWolfy]

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...

I can't speak for MWeb, but power failures in India or broken local fibre are problems beyond their control -- they are not excuses if they are fact. I'll agree though that it is frustrating for end-users and I hope that it's not a sign of the kind of reliability we can expect in future. I presume you're aware of the MWeb network status page:

http://www.mweb.co.za/helpcentre/NetworkStatusNotices/tabid/1765/Default.aspx

Can't say exactly what class of problem is reported there or how often it's updated.

 

[MWEB]

1. No problem with my router - tried another router(Cisco ADSL Router) and problem still the same
2. No problem with my firewall(smoothwall)
3. No problem with ADSL line ( Telkom tested about 4x in the last few days)

Hi bradlesliect,

Based on the limited information provided by your traceroute, it would be a fair guess that your performance issues lie somewhere with your local environment/setup by virtue of the very high latency you are experiencing on the 1st few hops.

4. No probs when connecting via another ISP - capped account

Please can you provide a similar traceroute using another provider on the exact same setup. The ADSL access infrastructure used would be common to all IPC providers.

MWB.

 

[Eliphas]

Still have not heard or recieved anything from both the signup and email I sent, and I signed up on the 1st April. >_>

 

[Gatecrasher]

FWIW:

tracert www.mybroadband.co.za

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

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 55 ms 76 ms 55 ms 196.22.169.170
4 66 ms 55 ms 55 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 102 ms 75 ms 60 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 56 ms 59 ms 100 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.110.73]
7 56 ms 75 ms 56 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
8 56 ms 56 ms 55 ms 196.43.25.138
9 59 ms 58 ms 57 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181]
10 60 ms 100 ms 58 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
11 86 ms 63 ms 58 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
12 68 ms 58 ms 101 ms 196.30.213.108
13 56 ms 57 ms 92 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 58 ms 57 ms 57 ms mybroadband.co.za [41.203.21.136]

Trace complete.

 

[SabreWolfy]

Still have not heard or recieved anything from both the signup and email I sent, and I signed up on the 1st April. >_>

Are the accounts / sales / sign-up people working over the long weekend?

 

[SabreWolfy]

<snip>
14 58 ms 57 ms 57 ms mybroadband.co.za [41.203.21.136]

Trace complete.

Quite a difference between your results, bradlesliect's and mine.

I presume physical proximity of your router to the exchange and/or physical proximity of the exchange to the destination has an effect.

 

[AntiThesis]

FWIW as well:

2 * * * Request timed out.
3 70 ms 69 ms 72 ms 196.22.169.170
4 70 ms 69 ms 74 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 107 ms 107 ms 103 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16.241]
6 72 ms 73 ms 72 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.11.73]
7 73 ms 72 ms 72 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.3.8.198]
8 73 ms 72 ms 72 ms 196.43.25.138
9 75 ms 74 ms 72 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
10 80 ms 80 ms 76 ms 196.30.1.21
11 76 ms 75 ms 73 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13]
12 80 ms 74 ms 73 ms 196.30.213.108
13 75 ms 75 ms 75 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 76 ms 76 ms 76 ms mybroadband.co.za [41.203.21.136]

 

[semaphore]

FWIW as well:

traceroute to mybroadband.co.za (41.203.21.136), 30 hops max, 60 byte packets
1 10.0.0.2 (10.0.0.2) 2.070 ms 1.994 ms 2.033 ms
2 41-133-88-1.dsl.mweb.co.za (41.133.88.1) 18.631 ms 18.593 ms 18.649 ms
3 196.22.169.134 (196.22.169.134) 20.087 ms 22.485 ms 24.448 ms
4 vl-92.vic-hscore-2.mweb.co.za (196.22.189.3) 30.392 ms 32.926 ms 35.229 ms
5 tengig-0-0-0-0-12.vic-up-1.mweb.co.za (196.22.169.241) 56.166 ms 64.782 ms 64.748 ms
6 rndf-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.110.73) 46.028 ms 13.476 ms 15.446 ms
7 rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za (196.43.8.198) 18.315 ms 17.583 ms 17.572 ms
8 196.43.25.138 (196.43.25.138) 18.289 ms 20.704 ms 23.504 ms
9 ge0-2.br1.jnb6.za.mtnbusiness.net (196.30.16.181) 27.116 ms 29.015 ms 31.402 ms
10 ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 34.612 ms 38.831 ms 39.607 ms
11 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 41.761 ms 44.123 ms 14.744 ms
12 196.30.213.108 (196.30.213.108) 16.682 ms 18.936 ms 17.703 ms
13 firewall1.jnb2.host-h.net (196.7.216.173) 17.636 ms 19.388 ms 21.417 ms
14 mybroadband.co.za (41.203.21.136) 24.730 ms 27.433 ms 29.366 ms

@Brad - No i dont agree, there was a bit of a hicup this morning but otherwise my line has been running full speed ahead today.

 

[SabreWolfy]

MWeb is further away (in time) than MyBroadBand Or maybe MWeb is busier

--- www.mweb.co.za ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 46.233/49.744/56.101/3.343 ms

--- www.mybroadband.co.za ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 23.283/29.400/32.545/2.778 ms

 

[cavedog]

IS ACCOUNT:


C:\Users\Eugene>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:

1 22 ms 18 ms 19 ms 196-209-2-1-ndn-esr-3.dynamic.isadsl.co.za [196.
209.2.1]
2 30 ms 31 ms 31 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
3 31 ms 31 ms 32 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
4 32 ms 31 ms 31 ms core5a-rba-gi0-0-0.ip.isnet.net [196.26.0.42]
5 31 ms 31 ms 31 ms 168.209.1.179
6 31 ms 31 ms 32 ms ge0-1.br1.jnb7.za.mtnbusiness.net [196.30.228.24
1]
7 31 ms 38 ms 33 ms ge0-1.cr1.jnb7.za.mtnbusiness.net [196.30.228.12
2]
8 35 ms 33 ms 33 ms 196.30.1.21
9 33 ms 32 ms 33 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
10 33 ms 32 ms 32 ms 196.30.213.108
11 33 ms 32 ms 39 ms firewall1.jnb2.host-h.net [196.7.216.173]
12 36 ms 33 ms 32 ms mybroadband.co.za [41.203.21.136]

Trace complete.

MWEB ACCOUNT:

C:\Users\Eugene>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:

1 18 ms 18 ms 19 ms 41-133-68-1.dsl.mweb.co.za [41.133.68.1]
2 31 ms 31 ms 30 ms 196.22.169.170
3 32 ms 31 ms 31 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 42 ms 39 ms 35 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
5 32 ms 31 ms 32 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.11
0.73]
6 32 ms 31 ms 32 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
7 32 ms 31 ms 32 ms 196.43.25.138
8 33 ms 33 ms 33 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
9 34 ms 36 ms 34 ms 196.30.1.21
10 33 ms 33 ms 33 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
11 33 ms 33 ms 33 ms 196.30.213.108
12 32 ms 33 ms 33 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 33 ms 33 ms 33 ms mybroadband.co.za [41.203.21.136]

Trace complete.



I can see anything wrong with Mweb uncapped account??

 

[sand_man]

Yeah what's the problem???

Tracing route to mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 41-132-16-1.dsl.mweb.co.za [41.132.16.1]
3 8 ms 7 ms 9 ms 196.22.169.158
4 7 ms 8 ms 8 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 29 ms 41 ms 27 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 8 ms 8 ms 13 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.11
0.73]
7 8 ms 9 ms 9 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
8 9 ms 9 ms 10 ms 196.43.25.138
9 12 ms 10 ms 11 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
10 10 ms 10 ms 10 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.2
2]
11 19 ms 20 ms 15 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 10 ms 10 ms 10 ms 196.30.213.108
13 9 ms 10 ms 9 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 11 ms 10 ms 10 ms mybroadband.co.za [41.203.21.136]

 

[Schwartz]

Youtube is loading slowly... have to let if buffer

 

[bradlesliect]

How many of the posters to this thread are from the Western Cape region and are having the same problem as me and some others down here in CT?

MWEB Rep - How does MWEB route international traffic from CTN? Via Victory Park(VIC) / New Doornfontein(NDF) and then out or do you have network blocks being routed differently depending on the source block? It appears routing goes via VIC/NDF and then back to CTN if I trace to www.iol.co.za which is a local site right here in CTN. Does this not cause unecessary latency and duplicate routes? I can see this if I use visual route to trace, ping and plot the route as well.

I think this is/may be the cause of some of the problems I am experiencing ...but...as said before, it may only be me. Any other Western Cape users having same problem?

 

[ponder]

It appears routing goes via VIC/NDF and then back to CTN if I trace to www.iol.co.za which is a local site right here in CTN. Does this not cause unecessary latency and duplicate routes?

That's probably due to the physical location of their IPC.

 

[PeterCH]

I'm just wondering about this:

Because these business packages are uncapped, there is no limit whatsoever on the amount of data you upload or download in a month. However, contracts are governed by an Acceptable Use Policy (AUP), and contravention will lead to warnings and, if necessary, suspension. This policy is specifically designed to ensure that the activities of any one user do not have a detrimental impact on theuser base as a whole. In the unlikely event that this does happen, MWEB Business will contact the user directly to discuss their usage and how to reduce the impact thereof.

http://www.mweb.co.za/adsl/?p=glossary#q1

Is that the new AUP? Surely if downloads are causing a problem, they should be throttled appropriately and the user not harassed by phone calls?

 

[mika1000]

I hear that the new T&C would be published soon (tomorrow?). We know that people complained about the T&C. Hopefully everything would be clarified?