MWEB Uncapped ADSL Feedback - Part 3

SpleenPoker said:
Probably a few minutes before I posted that message.

EDIT: Another disconnect right now.

EDIT2: Complete loss of international now too for a minute or so.
Click to expand...

When the international issue occurs, please provide me a trace route to bbc.co.uk
 
There is currently a problem on hop 3 197.84.96.138 affecting throughput both locally and internationally - latency between 122ms and 200ms (normally sub 40's). I'll post a complete trace shortly.

EDIT: Here we go:

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

1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 8 ms 8 ms 8 ms 41-135-192-1.dsl.mweb.co.za [41.135.192.1]
3 174 ms 173 ms 169 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 11 ms 10 ms 12 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 307 ms 306 ms 312 ms 197-84-5-225.cpt.mweb.co.za [197.84.5.225]
6 305 ms 307 ms 301 ms 197-84-4-32.cpt.mweb.co.za [197.84.4.32]
7 168 ms 170 ms 172 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
8 338 ms 307 ms 302 ms be-69-thd-p-2.mweb.co.za [176.67.177.162]
9 309 ms 311 ms 310 ms 176.67.177.148
10 301 ms 313 ms 313 ms ldn-b5-link.telia.net [62.115.13.17]
11 163 ms 153 ms 154 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.142]
12 * * * Request timed out.
13 312 ms 306 ms 310 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
14 303 ms 305 ms 305 ms 132.185.255.149
15 155 ms 154 ms 154 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.

Just to note, this doesn't happen on my Afrihost backup account. It seems to be only affecting MWEB ... and quite regularly I'm afraid. I've been having intermittent problems like this almost every weekend now for the past 2 months or so.
 
Last edited:
Mephisto_Helix said:
Ye, see it's not just me getting the traffic freeze throughout the night/early hours. Something is up and seeing that there are others saying the same thing, it's time to go from the "We have no reported blah blah blah" to "Oh shyte, something seems to be wrong, lets look into it" ..........

Plus, what exactly is meant by 'a Telkom problem' because I can switch from my Mweb account to any other one and have service, so where exactly is Telkom at fault? Are they giving only Mweb crap?
Click to expand...

+1, Its happened to me several times over the last 24 hours, a few minutes ago it happened again. Asked friends on other ISP's and they are fine but the people on Mweb i know are having the same issue, its extremely frustrating.
 
When the traffic is not dead, we have 400+ ping to International ......... on a damn weekend :mad:

Mweb -

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

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:
Reply from 212.58.244.20: bytes=32 time=337ms TTL=48
Reply from 212.58.244.20: bytes=32 time=349ms TTL=48
Reply from 212.58.244.20: bytes=32 time=352ms TTL=48
Reply from 212.58.244.20: bytes=32 time=363ms TTL=48

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

C:\Users\Andre>tracert bbc.co.uk

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

1 5 ms 5 ms 5 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
2 170 ms 170 ms 171 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
3 164 ms 168 ms 168 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
4 365 ms 361 ms 363 ms 176.67.177.227
5 354 ms 364 ms 363 ms ldn-b5-link.telia.net [62.115.13.13]
6 363 ms 358 ms 358 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
7 * * * Request timed out.
8 350 ms 351 ms 355 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
9 363 ms 359 ms 357 ms 132.185.255.149
10 361 ms 365 ms 369 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.
Click to expand...


AH -

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

Pinging bbc.co.uk [212.58.246.104] with 32 bytes of data:
Reply from 212.58.246.104: bytes=32 time=192ms TTL=52
Reply from 212.58.246.104: bytes=32 time=190ms TTL=52
Reply from 212.58.246.104: bytes=32 time=190ms TTL=52
Reply from 212.58.246.104: bytes=32 time=190ms TTL=52

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

C:\Users\Andre>tracert bbc.co.uk

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

1 5 ms 5 ms 5 ms 105-236-7-129-esr-lo.mtnbusiness.co.za [105.236.
7.129]
2 15 ms 14 ms 14 ms 41.181.221.218
3 14 ms 14 ms 15 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
4 190 ms 189 ms 190 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
5 32 ms 33 ms 32 ms ct-cr-2.za--rb-cr-1.za.mtnns.net [196.44.31.68]

6 33 ms 33 ms 36 ms ct-cr-1.za--ct-cr-2.za-a.mtnns.net [196.44.31.10
9]
7 250 ms 193 ms 190 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.22
1]
8 175 ms 181 ms 175 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83
]
9 195 ms 195 ms 195 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
10 * * * Request timed out.
11 180 ms 180 ms 179 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
12 192 ms 192 ms 191 ms 132.185.255.165
13 190 ms 191 ms 191 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]

Trace complete.
Click to expand...
 
Last edited:
I have also done a traceroute. Getting twice the amount of latency in wow at the moment. Normally on 160ms.


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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 8 ms 197-87-145-1.cpt.mweb.co.za [197.87.145.1]
3 63 ms 63 ms 63 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 80 ms 82 ms 81 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 241 ms 222 ms 223 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 215 ms 220 ms 216 ms 197-84-4-197.cpt.mweb.co.za [197.84.4.197]
7 342 ms 338 ms 335 ms 176.67.177.235
8 353 ms 355 ms 357 ms ldn-b5-link.telia.net [62.115.13.17]
9 222 ms 222 ms 224 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.142]
10 * * * Request timed out.
11 * * * Request timed out.
12 220 ms 221 ms 220 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
13 206 ms 209 ms 209 ms 132.185.255.165
14 228 ms 231 ms 231 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Trace complete.
 
Same issues as the others, this seems to be happening quite often now

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 9 ms 8 ms 8 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 106 ms 107 ms 106 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 165 ms 165 ms 167 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 253 ms 258 ms 254 ms 197-84-5-225.cpt.mweb.co.za [197.84.5.225]
6 234 ms 237 ms 233 ms 197-84-4-32.cpt.mweb.co.za [197.84.4.32]
7 254 ms 256 ms 251 ms 197-84-4-195.cpt.mweb.co.za [197.84.4.195]
8 262 ms 259 ms 257 ms be-69-thd-p-2.mweb.co.za [176.67.177.162]
9 232 ms 235 ms 236 ms 176.67.177.227
10 317 ms 319 ms 319 ms ldn-b5-link.telia.net [62.115.13.13]
11 327 ms 325 ms 324 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
12 * * * Request timed out.
13 * * * Request timed out.
14 326 ms 327 ms 324 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
15 323 ms 328 ms 326 ms 132.185.255.165
16 333 ms 343 ms 332 ms fmt-vip133.cwwtf.bbc.co.uk [212.58.246.104]


Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter.Home [192.168.1.1]
2 9 ms 9 ms 8 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 105 ms 106 ms 107 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 172 ms 167 ms 171 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 94 ms 89 ms 89 ms 196.28.178.66
6 119 ms 114 ms 113 ms cte-core-sw2.vwol.net [196.41.144.35]
7 104 ms 105 ms 104 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Hi guys,

Thanks for all the feedback and traces provided.
I have notified our engineers and provided them with the info posted to investigate.
As soon as I have some feedback or more info I will let you know.

Thanks
 
I have a Business Uncapped 1 meg service with Fixed IP's

And since Mweb did the last maintenance it has been 'kuk'

Random disconnections, latency spikes for hours & heavy packet loss

I use this line only for SIP so I have no other traffic running on it....

This a trace route from last week
Tracing route to sip.voip.mweb.net [196.28.95.12]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 <1 ms <1 ms <1 ms 197-81-XXX-XXX.jhb.mweb.co.za [197.81.XXX.XXX]
3 22 ms 24 ms 21 ms 197-81-146-1.jhb.mweb.co.za [197.81.146.1]
4 23 ms 22 ms 24 ms 197-81-146-3.jhb.mweb.co.za [197.81.146.3]
5 24 ms 26 ms 24 ms 197-80-96-54.jhb.mweb.co.za [197.80.96.54]
6 24 ms 24 ms 26 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
7 25 ms 24 ms 25 ms 197-81-229-17.jhb.mweb.co.za [197.81.229.17]
8 24 ms 23 ms 24 ms sip.voip.mweb.net [196.28.95.12]

Trace complete.
Click to expand...

This is a Trace Route now
Tracing route to sip.voip.mweb.net [196.28.95.12]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 <1 ms <1 ms <1 ms 197-81-XXX-XXX.jhb.mweb.co.za [197.81.XXX.XXX]
3 259 ms 254 ms 249 ms 197-81-146-1.jhb.mweb.co.za [197.81.146.1]
4 240 ms 243 ms 249 ms 197-81-146-3.jhb.mweb.co.za [197.81.146.3]
5 244 ms 252 ms 249 ms 197-80-96-54.jhb.mweb.co.za [197.80.96.54]
6 244 ms 246 ms 247 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
7 245 ms 250 ms 242 ms 197-81-229-17.jhb.mweb.co.za [197.81.229.17]
8 254 ms 259 ms 255 ms sip.voip.mweb.net [196.28.95.12]

Trace complete.
Click to expand...

Mweb has broken the Internet, if I use my Afrihost account all is peachy on the same line....

My Afrihost account, but latency seems to peak when traffic hits the Mweb Network?
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 8 ms 8 ms 9 ms 105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
3 19 ms 15 ms 17 ms 41.181.221.214
4 17 ms 16 ms 16 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 18 ms 18 ms 19 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 18 ms 19 ms 19 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
7 19 ms 19 ms 20 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
8 20 ms 19 ms 20 ms postfix.wipronet.co.za [196.22.161.133]
9 85 ms 83 ms 89 ms tengig0-0-0-3.vic-p-1.mweb.co.za [197.80.7.1]
10 62 ms 65 ms 66 ms tengig0-0-0-0.cpt-p-2.mweb.co.za [197.84.4.46]
11 49 ms 49 ms 48 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
12 47 ms 49 ms 48 ms 196.28.178.66
13 76 ms 79 ms 77 ms cte-core-sw2.vwol.net [196.41.144.35]
14 50 ms 49 ms 49 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...
 
Even worse now....

Tracing route to sip.voip.mweb.net [196.28.95.12]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 <1 ms <1 ms <1 ms 197-81-XXX-XXX.jhb.mweb.co.za [197.81.XXX.XXX]
3 1144 ms 1342 ms 1941 ms 197-81-146-1.jhb.mweb.co.za [197.81.146.1]
4 1542 ms 1644 ms 1242 ms 197-81-146-3.jhb.mweb.co.za [197.81.146.3]
5 1744 ms 1340 ms 1140 ms 197-80-96-54.jhb.mweb.co.za [197.80.96.54]
6 1240 ms 1541 ms 1640 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
7 1240 ms 1739 ms 1740 ms 197-81-229-17.jhb.mweb.co.za [197.81.229.17]
8 1295 ms 1439 ms 1640 ms sip.voip.mweb.net [196.28.95.12]

Trace complete.
Click to expand...
 
Mweb Guy,

It's not just Cape Town that is affected? KZN as well... since last week....

Outage Num:20255
MWEB ADSL outage affecting Cape town and surrounding areas
MWEB ADSL members in the Cape Town area may experience intermittant high latency
Start Date:2014-04-19 17:14:56
End Date:
Status:Open
Click to expand...
 
Just to confirm, KZN is also having issues.

Been stable for 45 minutes now, although that's nothing to be proud of.
 
nakedhousee said:
Just to confirm, KZN is also having issues.

Been stable for 45 minutes now, although that's nothing to be proud of.
Click to expand...

Thanks for the feedback guys, I will advise the engineers to follow up on it.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X