MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
Hummercellc said:
The strange part is, when running the two adsl line independently

Telkom Line > Router > Laptop
Telkom Line 2 > Router > Desktop

The second line disconnects when line one is maxed out! (still synced but PPPoE auth Failed), But only with Mweb accounts! Can't seem to replicate this with any other ISP.
So the problem points to Mweb and Telkom confirmed this.

I have spent almost two months of testing and back and fourth emails with your Tech's still no joy....

But thanks...
Click to expand...

From a technical point of view I simply can't see how that could be the case. I have a very clear picture of how our systems are put together and the 'customer journey' from router to our network. when you have 2 physical lines with 2 separate accounts side by side how can you possibly point to the ISP as being the cause of one line dropping? Unless the MWEB accounts are getting a different treatment on the Telkom backhaul which as far as I'm aware is not possible.

The scenario could just as well be you and your next door neighbor both being MWEB users, the fact that both lines are in the same residence is invisible to us.
 
Meh.... speeds (or lack thereof) is back.

(1Mb line)
http://www.speedtest.net/result/1971028989.png

JHB Mweb said:
Download Speed: 325 kbps (40.6 KB/sec transfer rate)
Upload Speed: 230 kbps (28.8 KB/sec transfer rate)
Click to expand...

Londom Mweb said:
Download Speed: 257 kbps (32.1 KB/sec transfer rate)
Upload Speed: 277 kbps (34.6 KB/sec transfer rate)
Latency: 509 ms
Jitter: 3 ms
Click to expand...

C:\Users\Frizzle>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=524ms TTL=240
Reply from 212.58.241.131: bytes=32 time=517ms TTL=240
Reply from 212.58.241.131: bytes=32 time=534ms TTL=240
Reply from 212.58.241.131: bytes=32 time=529ms TTL=240

Ping statistics for 212.58.241.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 517ms, Maximum = 534ms, Average = 526ms
Click to expand...

I'm assuming the high latency is due to the Seacom break though?
Weird, because it's been intermittent today. It's on-off-on-off. Already restarted my router.
 
froot said:
Meh.... speeds (or lack thereof) is back.

(1Mb line)
http://www.speedtest.net/result/1971028989.png







I'm assuming the high latency is due to the Seacom break though?
Weird, because it's been intermittent today. It's on-off-on-off. Already restarted my router.
Click to expand...
Hi froot

Could you please show us the full trace route, the ping doesn't really give us much to work with.
 
Will@MWEB said:
Hi froot

Could you please show us the full trace route, the ping doesn't really give us much to work with.
Click to expand...
Sure. There you go.
C:\Users\Frizzle>tracert www.bbc.co.uk

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

1 1 ms 1 ms 1 ms 192.168.0.1
2 13 ms 12 ms 12 ms 41-132-*.dsl.mweb.co.za [41.132.*]
3 15 ms 14 ms 14 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
4 271 ms 276 ms 272 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 440 ms 442 ms 448 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.
226]
6 202 ms 199 ms 202 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 199 ms 198 ms 199 ms 176.67.177.131
8 200 ms 194 ms 239 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
9 199 ms 194 ms 194 ms ae-14-51.car3.London1.Level3.net [4.69.139.68]
10 495 ms 494 ms 495 ms 195.50.90.162
11 * * * Request timed out.
12 201 ms 195 ms 195 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
13 433 ms 440 ms 443 ms 132.185.255.148
14 196 ms 195 ms 194 ms bbc-vip112.telhc.bbc.co.uk [212.58.244.67]

Trace complete.
Click to expand...

C:\Users\Frizzle>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 192.168.0.1
2 13 ms 12 ms 12 ms 41-132-*.dsl.mweb.co.za [41.132.*]
3 14 ms 15 ms 14 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
4 14 ms 15 ms 14 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 301 ms 300 ms 300 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 40 ms 40 ms 39 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 37 ms 35 ms 35 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 35 ms 35 ms 35 ms 196.28.178.66
9 37 ms 37 ms 36 ms cte-core-sw2.vwol.net [196.41.144.35]
10 36 ms 37 ms 37 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Is it just me, or is that a local problem? hscore-1 and tengig at Victory Park ?
 
Last edited:
Tracing route to www.myadsl.co.za [41.203.21.137]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.16.174
2 <1 ms <1 ms <1 ms 192.168.1.1
3 7 ms 6 ms 6 ms 41-135-115-1.dsl.mweb.co.za [41.135.115.1]
4 10 ms 9 ms 10 ms 41-86-107-18.mweb.co.za [41.86.107.18]
5 217 ms 215 ms 210 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 10 ms 11 ms 11 ms tengig0-7-0-2.12.vic-p-1.mweb.co.za [196.22.169.
241]
7 298 ms 291 ms 288 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
8 275 ms 270 ms 269 ms static161-134.netactive.co.za [196.22.161.134]
9 11 ms 12 ms 11 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

10 11 ms 11 ms 13 ms 196.44.31.99
11 277 ms 276 ms 275 ms ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.3
7]
12 11 ms 11 ms 11 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
13 11 ms 10 ms 10 ms core-router1.jnb2.host-h.net [196.30.213.108]
14 12 ms 12 ms 12 ms 41.72.136.53
15 277 ms 279 ms 276 ms mybroadband.co.za [41.203.21.137]

Trace complete.

I already checked that nothing is downloading and I restarted router and pc
 
Some more:

C:\Users\Frizzle>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 192.168.0.1
2 12 ms 12 ms 12 ms 41-132-26-1.dsl.mweb.co.za [41.132.26.1]
3 77 ms 73 ms 72 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.16
3.218]
4 246 ms 249 ms 247 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 501 ms 505 ms 504 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 122 ms 122 ms 129 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 246 ms 238 ms 237 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 120 ms 125 ms 120 ms 196.28.178.66
9 173 ms 168 ms 161 ms cte-core-sw2.vwol.net [196.41.144.35]
10 116 ms 117 ms 113 ms www.mweb.co.za [196.2.63.110]

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

1 <1 ms <1 ms <1 ms router [192.168.2.1]
2 10 ms 7 ms 8 ms 41-132-52-1.dsl.mweb.co.za [41.132.52.1]
3 149 ms 132 ms 134 ms 197-80-4-94.jhb.mweb.co.za [197.80.4.94]
4 44 ms 46 ms 43 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 167 ms 170 ms 169 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 43 ms 59 ms 63 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 41 ms 40 ms 40 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 41 ms 41 ms 40 ms 196.28.178.66
9 29 ms 34 ms 47 ms cte-core-sw2.vwol.net [196.41.144.35]
10 51 ms 53 ms 56 ms www.mweb.co.za [196.2.63.110]

Trace complete.

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

1 <1 ms <1 ms <1 ms router [192.168.2.1]
2 21 ms 12 ms 16 ms 41-132-52-1.dsl.mweb.co.za [41.132.52.1]
3 185 ms 175 ms 174 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
4 167 ms 192 ms 167 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 15 ms 9 ms 19 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za [196.22.169.
225]
6 210 ms 205 ms 207 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 209 ms 210 ms 216 ms static161-134.netactive.co.za [196.22.161.134]
8 21 ms 37 ms 23 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 32 ms 33 ms 32 ms 196.44.31.99
10 164 ms 165 ms 169 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.2
2]
11 32 ms 43 ms 32 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 32 ms 32 ms 32 ms core-router1.jnb2.host-h.net [196.30.213.108]
13 22 ms 27 ms 22 ms 41.72.136.53
14 139 ms 136 ms 138 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
Hi Everyone

Just in case Friday wasn't interesting enough a portion of our JHB IPC capacity has gone offline so we are running at high utilization on our JHB network. Customers in JHB can expect increased latency and slow response times.

We have logged this urgently with Telkom and I'll update you as soon as we have an ETR.
 
Will@MWEB said:
Hi Everyone

Just in case Friday wasn't interesting enough a portion of our JHB IPC capacity has gone offline so we are running at high utilization on our JHB network. Customers in JHB can expect increased latency and slow response times.

We have logged this urgently with Telkom and I'll update you as soon as we have an ETR.
Click to expand...

Ah. :(
Your response is much appreciated.
 
how do i do a Tracing route?

but it seems that slow speed is everywhere on mweb
and sounds like half of mweb are failing :/
did a speed test again and got 37kb/s

in worcester
probaly falls under cape town aria?
 
sybertiger said:
how do i do a Tracing route?

but it seems that slow speed is everywhere on mweb
and sounds like half of mweb are failing :/
did a speed test again and got 37kb/s

in worcester
probaly falls under cape town aria?
Click to expand...

Hi sybertiger

I have sent you a private message with the steps on how to do it.
 
reg van die plaas af..

I'm in s.subs CPT and speeds are ok here..

michael@macserver:~$traceroute myadsl.co.za
traceroute to myadsl.co.za (41.203.21.137), 64 hops max, 52 byte packets
1 dsl-gw (192.168.0.1) 0.650 ms 0.311 ms 0.333 ms
2 41-133-138-1.dsl.mweb.co.za (41.133.138.1) 7.687 ms 7.224 ms 7.523 ms
3 te1-1-0.508.cpt-ipc-1.mweb.co.za (196.28.178.190) 9.528 ms 9.632 ms 9.145 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 60.665 ms 26.463 ms 9.648 ms
5 tengige0-2-0-0.11.cpt-up-1.mweb.co.za (196.28.178.97) 52.733 ms 11.776 ms
tengigethernet0-1-0-0.cpt-up-2.mweb.co.za (196.28.178.114) 11.959 ms
6 197-84-4-59.cpt.mweb.co.za (197.84.4.59) 15.210 ms
197-84-4-57.cpt.mweb.co.za (197.84.4.57) 12.232 ms 9.635 ms
7 mtn-pp.cpt-cinx-2.mweb.co.za (196.28.178.142) 11.345 ms 88.399 ms 10.624 ms
8 196.44.0.75 (196.44.0.75) 27.047 ms 10.888 ms 10.257 ms
9 rb-cr-1.za--ct-cr-1.za.mtnns.net (196.44.31.128) 38.840 ms 60.773 ms 40.860 ms
10 196.44.31.97 (196.44.31.97) 38.149 ms 79.840 ms 38.405 ms
11 ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 45.294 ms
ge4-0-0.gw17.jnb6.za.mtnbusiness.net (196.30.1.37) 49.318 ms 56.589 ms
12 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 79.475 ms 43.027 ms 38.413 ms
13 core-router1.jnb2.host-h.net (196.30.213.108) 39.885 ms 65.654 ms 76.594 ms
14 41.72.136.53 (41.72.136.53) 42.502 ms 39.798 ms 90.042 ms
15 mybroadband.co.za (41.203.21.137) 85.496 ms 41.027 ms 38.454 ms
Click to expand...

Looks like the routing is a bit broken to mweb.co.za, traced fine a few minutes ago now

michael@macserver:~$traceroute mweb.co.za
traceroute to mweb.co.za (196.2.63.110), 64 hops max, 52 byte packets
1 dsl-gw (192.168.0.1) 0.661 ms 0.294 ms 0.327 ms
2 41-133-138-1.dsl.mweb.co.za (41.133.138.1) 65.156 ms 8.269 ms 14.334 ms
3 196-28-178-222.adsl.mweb.co.za (196.28.178.222) 20.659 ms 9.360 ms 9.332 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 9.851 ms 9.938 ms 58.752 ms
5 196.28.178.66 (196.28.178.66) 16.548 ms 10.798 ms 9.560 ms
6 cte-core-sw2.vwol.net (196.41.144.35) 35.693 ms 55.790 ms 10.197 ms
7 * * *
8 * * *
9 * * *
Click to expand...

Is google peering down too? I see it's routing internationally.

michael@macserver:~$traceroute www.google.co.za
traceroute: Warning: www.google.co.za has multiple addresses; using 74.125.233.23
traceroute to www-cctld.l.google.com (74.125.233.23), 64 hops max, 52 byte packets
1 dsl-gw (192.168.0.1) 0.612 ms 0.407 ms 0.309 ms
2 41-133-138-1.dsl.mweb.co.za (41.133.138.1) 29.483 ms 8.154 ms 7.359 ms
3 196-28-178-222.adsl.mweb.co.za (196.28.178.222) 60.646 ms 22.613 ms 9.714 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 9.621 ms 9.137 ms
197-84-2-2.cpt.mweb.co.za (197.84.2.2) 9.259 ms
5 tengige0-2-0-0.11.cpt-up-1.mweb.co.za (196.28.178.97) 166.162 ms 163.239 ms
tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 186.349 ms
6 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 188.604 ms 186.480 ms 207.982 ms
7 176.67.177.131 (176.67.177.131) 163.834 ms 198.239 ms 200.386 ms
8 176.67.177.133 (176.67.177.133) 200.887 ms 164.925 ms 186.906 ms
9 195.66.224.125 (195.66.224.125) 230.581 ms
195.66.236.125 (195.66.236.125) 204.969 ms
195.66.224.125 (195.66.224.125) 196.369 ms
10 209.85.240.63 (209.85.240.63) 204.734 ms 211.153 ms 225.696 ms
11 209.85.252.45 (209.85.252.45) 201.524 ms 197.910 ms 194.865 ms
12 209.85.248.214 (209.85.248.214) 330.893 ms 326.746 ms 332.015 ms
13 * * *
14 cpt01s01-in-f23.1e100.net (74.125.233.23) 318.230 ms 318.550 ms 328.413 ms
Click to expand...
 
Will@MWEB said:
Hi Everyone

Just in case Friday wasn't interesting enough a portion of our JHB IPC capacity has gone offline so we are running at high utilization on our JHB network. Customers in JHB can expect increased latency and slow response times.

We have logged this urgently with Telkom and I'll update you as soon as we have an ETR.
Click to expand...

LOL, just my luck for this to happen on the day I signed up with MWEB.
 
For 1Mbps line this is the speed, nothing else downloading.
Download Speed: 126 kbps (15.8 KB/sec transfer rate)
Upload Speed: 212 kbps (26.5 KB/sec transfer rate)
Latency: 420 ms

And for local:
Download Speed: 131 kbps (16.4 KB/sec transfer rate)
Upload Speed: 369 kbps (46.1 KB/sec transfer rate)
Latency: 223 ms
 
Last edited:
Gielie Geelmielie said:
For 1Mbps line this is the speed, nothing else downloading.
Download Speed: 126 kbps (15.8 KB/sec transfer rate)
Upload Speed: 212 kbps (26.5 KB/sec transfer rate)
Latency: 420 ms

And for local:
Download Speed: 131 kbps (16.4 KB/sec transfer rate)
Upload Speed: 369 kbps (46.1 KB/sec transfer rate)
Latency: 223 ms
Click to expand...


It's happening to everyone including me!
 
blunt said:
reg van die plaas af..

Is google peering down too? I see it's routing internationally.
Click to expand...

Hi blunt

Yep it's come up in conversation here a few times recently. There are some issues with the local infrastructure which cause traffic going via the peering links to grind to a halt so we have shut them while Google address the matter.

Just an update on the JHB IPC issue currently, I've been informed that Telkom have isolated a cable break and are busy addressing the problem (no ETR yet, but holding thumbs that everything will be sorted in time for the Friday night gamers)
 
Gielie Geelmielie said:
For 1Mbps line this is the speed, nothing else downloading.
Download Speed: 126 kbps (15.8 KB/sec transfer rate)
Upload Speed: 212 kbps (26.5 KB/sec transfer rate)
Latency: 420 ms

And for local:
Download Speed: 131 kbps (16.4 KB/sec transfer rate)
Upload Speed: 369 kbps (46.1 KB/sec transfer rate)
Latency: 223 ms
Click to expand...

Hi Gielie Geelmielie

Send me your MWEB details please.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X