MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
Router rebooted and instantly fixed. lol.

testmy.net


speedtest.net


C:\Users\JadeX64>ping www.google.com

Pinging www.l.google.com [74.125.233.17] with 32 bytes of data:
Reply from 74.125.233.17: bytes=32 time=32ms TTL=52
Reply from 74.125.233.17: bytes=32 time=33ms TTL=52
Reply from 74.125.233.17: bytes=32 time=33ms TTL=52
Reply from 74.125.233.17: bytes=32 time=34ms TTL=52

Ping statistics for 74.125.233.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 34ms, Average = 33ms

C:\Users\JadeX64>ping www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=32ms TTL=118
Reply from 196.2.63.110: bytes=32 time=32ms TTL=118
Reply from 196.2.63.110: bytes=32 time=32ms TTL=118
Reply from 196.2.63.110: bytes=32 time=32ms TTL=118

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

C:\Users\JadeX64>ping www.gmail.com

Pinging googlemail.l.google.com [74.125.233.22] with 32 bytes of data:
Reply from 74.125.233.22: bytes=32 time=33ms TTL=53
Reply from 74.125.233.22: bytes=32 time=32ms TTL=53
Reply from 74.125.233.22: bytes=32 time=32ms TTL=53
Reply from 74.125.233.22: bytes=32 time=33ms TTL=53

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

C:\Users\JadeX64>ping www.google.co.za

Pinging www-cctld.l.google.com [74.125.233.24] with 32 bytes of data:
Reply from 74.125.233.24: bytes=32 time=39ms TTL=53
Reply from 74.125.233.24: bytes=32 time=32ms TTL=53
Reply from 74.125.233.24: bytes=32 time=32ms TTL=53
Reply from 74.125.233.24: bytes=32 time=34ms TTL=53

Ping statistics for 74.125.233.24:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 39ms, Average = 34ms

C:\Users\JadeX64>
Click to expand...


C:\Users\JadeX64>tracert www.google.com

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

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 9 ms 8 ms 9 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 15 ms 14 ms 14 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 11 ms 12 ms 11 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 46 ms 46 ms 50 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 34 ms 37 ms 36 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 38 ms 37 ms 34 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 32 ms 32 ms 32 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 33 ms 33 ms 33 ms google.cinx.net.za [196.223.22.41]
10 33 ms 33 ms 32 ms 64.233.174.105
11 33 ms 33 ms 32 ms cpt01s01-in-f17.1e100.net [74.125.233.17]

Trace complete.

C:\Users\JadeX64>tracert www.mweb.co.za

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.10.10.1]
2 9 ms 8 ms 8 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 10 ms 10 ms 10 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 10 ms 11 ms 11 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 35 ms 35 ms 35 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 34 ms 35 ms 36 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 37 ms 34 ms 36 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 33 ms 32 ms 33 ms 196.28.178.115
9 37 ms 32 ms 32 ms 196-28-178-38.adsl.mweb.co.za [196.28.178.38]
10 32 ms 32 ms 32 ms cte-core-sw2.vwol.net [196.41.144.35]
11 32 ms 33 ms 32 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\JadeX64>tracert www.gmail.com

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

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 9 ms 9 ms 9 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 11 ms 11 ms 11 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 11 ms 11 ms 12 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 45 ms 44 ms 44 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 38 ms 37 ms 33 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 37 ms 35 ms 35 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 33 ms 32 ms 32 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 32 ms 35 ms 32 ms google.cinx.net.za [196.223.22.41]
10 33 ms 32 ms 32 ms 64.233.174.105
11 32 ms 32 ms 32 ms cpt01s01-in-f22.1e100.net [74.125.233.22]

Trace complete.

C:\Users\JadeX64>tracert www.google.co.za

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

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 9 ms 9 ms 9 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 11 ms 11 ms 11 ms 41-86-107-18.mweb.co.za [41.86.107.18]
4 11 ms 11 ms 11 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 53 ms 53 ms 48 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 35 ms 35 ms 36 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 35 ms 37 ms 34 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 32 ms 31 ms 32 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 42 ms 33 ms 32 ms google.cinx.net.za [196.223.22.41]
10 32 ms 32 ms 32 ms 64.233.174.105
11 32 ms 33 ms 33 ms www-cctld.l.google.com [74.125.233.24]

Trace complete.
Click to expand...
 
Last edited:
Hi MwebGuy

Why doesnt www.bbc.co.uk load via my mweb account but it does via my afrihost, the traces go through, is port 80 being shaped ?

I know my exchange is congested ever since telscum upgraded it to 10mbps but then why does bbc.co.uk open only via my afrihost ?

via mweb

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

1 <1 ms <1 ms <1 ms 10.10.1.254
2 221 ms 209 ms 213 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 218 ms 197 ms 190 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 199 ms 203 ms 283 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 407 ms 392 ms 385 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 410 ms 362 ms 324 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 395 ms 427 ms 406 ms xe-10-1-3.edge4.london1.level3.net [212.113.14.1
21]
8 367 ms 338 ms 351 ms ae-14-51.car3.london1.level3.net [4.69.139.68]
9 424 ms 407 ms 396 ms 195.50.90.162
10 370 ms 369 ms 399 ms 212.58.238.137
11 370 ms 394 ms 388 ms 132.185.254.141
12 * * * Request timed out.
13 * 395 ms 395 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
14 370 ms 388 ms 389 ms 132.185.255.164
15 391 ms 400 ms 405 ms bbc-vip016.cwwtf.bbc.co.uk [212.58.246.95]

Trace complete.

via afrihost

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

1 <1 ms <1 ms <1 ms 10.10.1.254
2 215 ms 215 ms 207 ms 196-210-146-1.dynamic.isadsl.co.za [196.210.146.
1]
3 204 ms 223 ms * 196.38.73.113
4 211 ms 220 ms 220 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 196 ms 196 ms 213 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

6 403 ms 377 ms 400 ms 168.209.201.73
7 395 ms 396 ms 376 ms bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.10
3]
8 * * * Request timed out.
9 396 ms 394 ms 422 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 365 ms 393 ms 391 ms 132.185.255.164
11 365 ms 380 ms 391 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.
 
nerf said:
Hi MwebGuy

Why doesnt www.bbc.co.uk load via my mweb account but it does via my afrihost, the traces go through, is port 80 being shaped ?

I know my exchange is congested ever since telscum upgraded it to 10mbps but then why does bbc.co.uk open only via my afrihost ?

via mweb

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

1 <1 ms <1 ms <1 ms 10.10.1.254
2 221 ms 209 ms 213 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 218 ms 197 ms 190 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 199 ms 203 ms 283 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 407 ms 392 ms 385 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 410 ms 362 ms 324 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 395 ms 427 ms 406 ms xe-10-1-3.edge4.london1.level3.net [212.113.14.1
21]
8 367 ms 338 ms 351 ms ae-14-51.car3.london1.level3.net [4.69.139.68]
9 424 ms 407 ms 396 ms 195.50.90.162
10 370 ms 369 ms 399 ms 212.58.238.137
11 370 ms 394 ms 388 ms 132.185.254.141
12 * * * Request timed out.
13 * 395 ms 395 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
14 370 ms 388 ms 389 ms 132.185.255.164
15 391 ms 400 ms 405 ms bbc-vip016.cwwtf.bbc.co.uk [212.58.246.95]

Trace complete.

via afrihost

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

1 <1 ms <1 ms <1 ms 10.10.1.254
2 215 ms 215 ms 207 ms 196-210-146-1.dynamic.isadsl.co.za [196.210.146.
1]
3 204 ms 223 ms * 196.38.73.113
4 211 ms 220 ms 220 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 196 ms 196 ms 213 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

6 403 ms 377 ms 400 ms 168.209.201.73
7 395 ms 396 ms 376 ms bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.10
3]
8 * * * Request timed out.
9 396 ms 394 ms 422 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 365 ms 393 ms 391 ms 132.185.255.164
11 365 ms 380 ms 391 ms bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.
Click to expand...

Thats a very good question, we will have to investigate this from our side.
I have escalated this to our specialists who will contact you
Regards
MWEB Guy
 
Hi Mweb guy.

Just to update you - a telkom techie came through over the weekend and gave me a new line. However, the line was clearly not the problem, as I am still getting 200ms ping and 0.40 MB downloads most of the time on a 4MB line.
 
Yarik11 said:
Hi Mweb guy.

Just to update you - a telkom techie came through over the weekend and gave me a new line. However, the line was clearly not the problem, as I am still getting 200ms ping and 0.40 MB downloads most of the time on a 4MB line.
Click to expand...

Thank you for the update, I will add this to the open escalation.

Regards
MWEB Guy
 
Must be a network problem, my 4mb back to max 40 kb/s; hope mweb solves this soon.
 
Is there a problem with the network atm? I have got really slow browsing tonight, especially with international...

traceroute to www.bmw.co.uk (80.69.8.110), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 2.633 ms 1.515 ms 1.779 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 8.507 ms 7.679 ms 7.502 ms
3 te1-1-0.502.cpt-ipc-1.mweb.co.za (196.28.178.166) 8.532 ms 9.827 ms 8.711 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 11.182 ms 8.372 ms 7.928 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 10.707 ms 11.179 ms 12.183 ms
6 197-80-4-136.jhb.mweb.co.za (197.80.4.136) 185.498 ms 187.435 ms 183.598 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 159.261 ms 158.482 ms 158.704 ms
8 linx-226.bg1.ld2.eu.equinix.net (195.66.226.187) 159.557 ms
linx-224.bg2.ld2.eu.equinix.net (195.66.224.187) 162.802 ms
linx-226.bg1.ld2.eu.equinix.net (195.66.226.187) 158.702 ms
9 fa47.sw1.lhr.grg.com (80.69.0.90) 159.087 ms 161.756 ms 162.131 ms
10 * * *
11 * * *
12 * * *

MWEB Guy, why does that keep on having timeouts?? Any international site I try it gets to a point then all I see are asterisks!

I tried to do a speed on the MWEB website but all I keep getting is "server is too busy"... Me thinks something is up. Anyway, I'm going to bed now, hopefully it'll be sorted "tomorrow".
 
After few days of International speeds down to 40KB rebooting the router solved the problem, back up to 500KB now
 
Dames said:
Is there a problem with the network atm? I have got really slow browsing tonight, especially with international...

traceroute to www.bmw.co.uk (80.69.8.110), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 2.633 ms 1.515 ms 1.779 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 8.507 ms 7.679 ms 7.502 ms
3 te1-1-0.502.cpt-ipc-1.mweb.co.za (196.28.178.166) 8.532 ms 9.827 ms 8.711 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 11.182 ms 8.372 ms 7.928 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 10.707 ms 11.179 ms 12.183 ms
6 197-80-4-136.jhb.mweb.co.za (197.80.4.136) 185.498 ms 187.435 ms 183.598 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 159.261 ms 158.482 ms 158.704 ms
8 linx-226.bg1.ld2.eu.equinix.net (195.66.226.187) 159.557 ms
linx-224.bg2.ld2.eu.equinix.net (195.66.224.187) 162.802 ms
linx-226.bg1.ld2.eu.equinix.net (195.66.226.187) 158.702 ms
9 fa47.sw1.lhr.grg.com (80.69.0.90) 159.087 ms 161.756 ms 162.131 ms
10 * * *
11 * * *
12 * * *

MWEB Guy, why does that keep on having timeouts?? Any international site I try it gets to a point then all I see are asterisks!

I tried to do a speed on the MWEB website but all I keep getting is "server is too busy"... Me thinks something is up. Anyway, I'm going to bed now, hopefully it'll be sorted "tomorrow".
Click to expand...

Hi Dames,

Please let me know if you are still experiencing connectivity issues.

MWEB Guy
 
to reiterate my post in the proper thread:


Pr⊕phet said:
Will@MWEB said:
Quite an interesting thread people, please allow me to jump in and say a few words :)

roomtemp firstly I'm really sorry to hear that you're having a frustrating experience with us. Filesharing site are classified as p2p and thus moved down the list in terms of traffic priority (I'll explain our approach to traffic prioritization shortly), however You should not be having a problem like the one you're describing with video streaming.

Please do pass your details on to MWEB Guy so that we can see what product you're on and investigate properly. Given your technical ability I'm sure you will find it very easy to provide us with all the data we need (latency and packet loss checks and so forth) to try and isolate the cause of any problem you might be having.

Now in terms of the discussion around Shaping and FUPs I'd like to explain how we do things, for those who may not be 100% familiar with our setup:

Firstly MWEB is a Tier 1 ISP with IPC links in JHB, Durban and Cape Town with a 10gb fibre ring linking the 3 sites. In addition to this we have over 20gb of international capacity via Seacom and SAT-3 which lands in London at our own point of presence where we link up with our European peering partners.

This means that, with the exception of the Telkom backhaul linking you to our network, MWEB is in full control of the user experience from end to end and we are not reliant on the FUP, or other shaping policies employed by local backbone providers.

On our own network we have chosen not to implement any FUP type policy which means that an individual user will not have his experience altered, or his speed reduced (throttled) based on the amount of bandwidth they have used over a fixed period of time, or where they find themselves on a usage curve compared to the rest of the subscriber base.

When it comes to traffic prioritization we have a very simple and direct approach, which is to place latency sensitive, high performance traffic at the top of the pile, which equates to voice video and gaming, and to place high network load traffic which is not performance sensitive (Filesharing sites, NNTP and traffic generally classed as p2p) at the bottom.

We also have an extensive caching infrastructure deployed on our network, which includes state of the art web caching solutions, Google caches and Steam caches (for our gaming customers) and we are establishing relationships with content distribution networks (such as Limelight) with the aim of doing everything possible to provide our customers with a superb Internet experience.

In terms of our acceptable usage policy, which was touched on briefly in one of the posts in this thread :

Yes our abuse team does actively monitor certain reports which identify a very small group of users who are really excessive in their use of our shaped products and we do issue warnings to these users asking them to curb their behavior. I must stress though that most of these users find it very easy to comply with our requests and there are very few cases where we are forced to take further steps.

Kind Regards
Will
Click to expand...

Any ETA on our 40KB problem from day to day ?

To sum up what happens is:

A)
1) switch on my router when I get home
2) all traffic is limited to 0-40KB
3) reboot router 1 or more times
4) magically it's fixed.


B)
1) router has been on for a while
2) traffic is going max then all of a sudden it goes solid 0-40KB
3) reboot router 1 or more times
4) magically it's fixed.

This is now ongoing from Sunday and each day exactly the same thing happens.

Already logged as

12-02-2012 10:54 AM
http://mybroadband.co.za/vb/showthr...DSL-Feedback?p=7720215&viewfull=1#post7720215

13-02-2012 06:00 PM
http://mybroadband.co.za/vb/showthr...DSL-Feedback?p=7727661&viewfull=1#post7727661

14-02-2012 05:17 PM
http://mybroadband.co.za/vb/showthr...DSL-Feedback?p=7733995&viewfull=1#post7733995

Now before you jump the gun and blow the FS excuse, all those test I've done is plain vanilla HTTP/FTP as per all posts. Also when it happens it's only mweb that is broken and not other ISPs as clearly demonstrated by my WebAfrica tests. You guys seems to have broken something after fondling with the DCs/IPs.
Click to expand...

Now, ETA and Feedback please.

:edit
On going threads on this issue

MWEB ADSL downloads & browsing extremely slow in PTA in Feb 2012

The great 40Kilobyte per sec Wall and the MWEB Uncapped deception

International slow ?
 
Last edited:
Last edited:
MWEB Guy said:
Hi cybershark,

Do you feel that your speedtest is slow?

If I understand you correctly, you saying that you done the speedtest while running a 40kb DL?

MWEB Guy
Click to expand...

http://www.speedtest.net/result/1774263012.png

Speed test is fine. We all know there's a massive difference between a theoretical speed test(which is optimised on the MWEB network) and real world use that is subject to shaping.

I've shown you 2 specific examples of downloads being limited to just over 40Kb/s(I can post at least a dozen more), and another getting full line speed from tenet mirror. Something is wrong on the network, normal http traffic is getting treated the same way as file sharing, with a few exceptions namely tenet and youtube.
 
Hi cybershark,

Thank you for the feedback, I have now added your details to the current issue that is being investigated by our engineers.
 
cybershark said:
http://www.speedtest.net/result/1774263012.png

Speed test is fine. We all know there's a massive difference between a theoretical speed test(which is optimised on the MWEB network) and real world use that is subject to shaping.

I've shown you 2 specific examples of downloads being limited to just over 40Kb/s(I can post at least a dozen more), and another getting full line speed from tenet mirror. Something is wrong on the network, normal http traffic is getting treated the same way as file sharing, with a few exceptions namely tenet and youtube.
Click to expand...

Hi cybershark & Pr⊕phet

We have made some changes on our side, please test your connection again and feedback me.

MWEB Guy
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X