MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
wily me said:
Not sure what you mean? All I know it is very up and down and spiky. Maybe my line. Will feedback later.
Click to expand...

Hi wily

If you look at the trace the ms reported at each hop indicates your latency to that point on the network. Looking at which point it starts to climb from can give you an indication of where your problem is. If it increases at the 2nd and 3rd hop that's usually an indication that you're on a congested exchange. Can you take some more traces in the evenings when it's at it's worst and let us see those?

Thanks
Will
 
Thank you Will and especially MWEB-GUY, the salesman contacted me this morning. I have resigned up with MWEB and now on the 6 months MWEB+DSTV special.

Thank you sir :-)
 
Linoman said:
Thank you Will and especially MWEB-GUY, the salesman contacted me this morning. I have resigned up with MWEB and now on the 6 months MWEB+DSTV special.

Thank you sir :-)
Click to expand...

+DSTV? tell me more.
 
My Connection has gone to poo for the last few hours. 200ms pings to JHB and CPT and can't get more than 0.3mbps on my 4mbps line either locally or internationally.

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 60 ms 37 ms 8 ms 41-132-60-1.dsl.mweb.co.za [41.132.60.1]
3 237 ms 205 ms 206 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 210 ms 215 ms 267 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 255 ms 210 ms 331 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
6 245 ms 256 ms 247 ms 197-84-4-38.cpt.mweb.co.za [197.84.4.38]
7 334 ms 251 ms 339 ms 197-84-4-36.cpt.mweb.co.za [197.84.4.36]
8 250 ms 250 ms 273 ms 197-84-4-34.cpt.mweb.co.za [197.84.4.34]
9 338 ms 267 ms 299 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
10 321 ms 254 ms 249 ms 196-28-178-34.adsl.mweb.co.za [196.28.178.34]
11 256 ms 256 ms 312 ms www.mweb.co.za [196.2.63.110]
Click to expand...

Tracing route to www.gog.com [70.38.122.100]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 8 ms 7 ms 41-132-60-1.dsl.mweb.co.za [41.132.60.1]
3 261 ms 316 ms 255 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 275 ms 295 ms 239 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 286 ms 244 ms 293 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]
6 471 ms 476 ms 468 ms 197-84-4-38.cpt.mweb.co.za [197.84.4.38]
7 488 ms 482 ms 470 ms 197-80-5-7.jhb.mweb.co.za [197.80.5.7]
8 566 ms 495 ms 461 ms 149.6.98.17
9 507 ms 507 ms 534 ms te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.165]
10 630 ms 530 ms 544 ms te0-0-0-4.ccr21.lon13.atlas.cogentco.com [154.54.57.110]
11 541 ms 542 ms 673 ms te0-1-0-5.ccr21.ymq02.atlas.cogentco.com [154.54.80.125]
12 591 ms 560 ms 582 ms te8-4.cl-core06.cogent.mtl.iweb.com [38.104.154.202]
13 681 ms 546 ms 590 ms te6-4.v0700.cl-core05.mtl.iweb.com [67.205.127.93]
14 558 ms 684 ms 694 ms ip-70-38-122-100.static.privatedns.com [70.38.122.100]
Click to expand...

Looks like something is busted in the Durban network.
 
Hi Abn0rm4l,

Please could you check my PM I sent you.

Kind regards,
MWEB Guy
 
Somthing seems broken on MWEBs side.

tracepath www.mweb.co.za

1: ****-desktop.local 0.163ms pmtu 1500
1: IPCop.localdomain 1.962ms
1: IPCop.localdomain 1.510ms
2: IPCop.localdomain 1.675ms pmtu 1492
2: 41-132-60-1.dsl.mweb.co.za 33.525ms
3: 197-82-5-250.dbn.mweb.co.za 436.596ms asymm 6
4: 197-82-2-3.dbn.mweb.co.za 426.600ms asymm 6
5: 197-82-3-1.dbn.mweb.co.za 422.101ms asymm 6
6: tengig0-1-2-0.cpt-up-2.mweb.co.za 438.032ms asymm 7
7: vlan11.cpt-hscore-1.mweb.co.za 435.823ms asymm 9
8: 196-28-178-34.adsl.mweb.co.za 468.065ms asymm 10
Click to expand...
 
BrianB said:
Somthing seems broken on MWEBs side.
Click to expand...

Hi BrianB,

I am not aware of any issues at the moment apart from the one's listed on the notice board

Please pm with the type of issues you are experiencing and I will look into it for you.

kind regards,
MWEB Guy
 
MWEB Guy said:
Hi BrianB,

I am not aware of any issues at the moment apart from the one's listed on the notice board

Please pm with the type of issues you are experiencing and I will look into it for you.

kind regards,
MWEB Guy
Click to expand...

I'm getting very slow website response and loading times.

Have a look at the traceroute, both Abn0rm4l and I are getting a huge ping spike between 41-132-60-1.dsl.mweb.co.za (33.525ms) and 197-82-5-250.dbn.mweb.co.za (436.596ms). Either 197-82-5-250.dbn.mweb.co.za is faulty or the link to it is.

I do not get the ping spike when using my Afrihost account.
 
My 4M line in Durban is running real slow as well.

Something really not well at 197-82-5-250.dbn.mweb.co.za [197.82.5.250] .

Tracing route to easytracking.co.za [41.86.98.116]

over a maximum of 30 hops:



1 1 ms 1 ms <1 ms 192.168.100.50

2 10 ms 10 ms 10 ms 41-133-68-1.dsl.mweb.co.za [41.133.68.1]

3 444 ms 500 ms 433 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]

4 435 ms 435 ms 431 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]

5 428 ms 427 ms 442 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]

6 536 ms 549 ms 520 ms tengig0-0-0-0.vic-p-1.mweb.co.za [197.84.4.38]

7 446 ms 444 ms 440 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]

8 443 ms 432 ms 435 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]

9 500 ms 485 ms 433 ms 134.75.28.196.netactive.net [196.28.75.134]

10 422 ms 440 ms 422 ms 85.75.28.196.netactive.net [196.28.75.85]

11 498 ms 458 ms 453 ms 41-86-98-116.mweb.co.za [41.86.98.116]
 
zs6cey said:
My 4M line in Durban is running real slow as well.

Something really not well at 197-82-5-250.dbn.mweb.co.za [197.82.5.250] .
Click to expand...

I see your hop 2 is different to mine so it is definitely 197.82.5.250 that is the problem.
 
zs6cey said:
My 4M line in Durban is running real slow as well.

Something really not well at 197-82-5-250.dbn.mweb.co.za [197.82.5.250] .

Tracing route to easytracking.co.za [41.86.98.116]

over a maximum of 30 hops:



1 1 ms 1 ms <1 ms 192.168.100.50

2 10 ms 10 ms 10 ms 41-133-68-1.dsl.mweb.co.za [41.133.68.1]

3 444 ms 500 ms 433 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]

4 435 ms 435 ms 431 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]

5 428 ms 427 ms 442 ms 197-82-3-1.dbn.mweb.co.za [197.82.3.1]

6 536 ms 549 ms 520 ms tengig0-0-0-0.vic-p-1.mweb.co.za [197.84.4.38]

7 446 ms 444 ms 440 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]

8 443 ms 432 ms 435 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]

9 500 ms 485 ms 433 ms 134.75.28.196.netactive.net [196.28.75.134]

10 422 ms 440 ms 422 ms 85.75.28.196.netactive.net [196.28.75.85]

11 498 ms 458 ms 453 ms 41-86-98-116.mweb.co.za [41.86.98.116]
Click to expand...

BrianB said:
I'm getting very slow website response and loading times.

Have a look at the traceroute, both Abn0rm4l and I are getting a huge ping spike between 41-132-60-1.dsl.mweb.co.za (33.525ms) and 197-82-5-250.dbn.mweb.co.za (436.596ms). Either 197-82-5-250.dbn.mweb.co.za is faulty or the link to it is.

I do not get the ping spike when using my Afrihost account.
Click to expand...

Hi Guys, thanks for all the information; our engineers are looking at the problem as we speak. Hopefully we will have a solution shortly.

Kind regards, MWEB Guy
 
BrianB said:
I see your hop 2 is different to mine so it is definitely 197.82.5.250 that is the problem.
Click to expand...

Pinging IP:197.82.5.250

!!!!!!!!!!!!!!!!

Ping Size (in bytes): 32
Ping attempts: 16
Successful Replies: 16
Failed Replies: 0
Percentage: 100%
Average Round Trip Time: 454ms

Yes, I agree. 454ms to the local Durban hub is not good.
 
The problem seems to have been fixed/bypassed.

Thanks MWEB Guy

1: IPCop.localdomain 1.463ms
1: IPCop.localdomain 1.341ms
2: IPCop.localdomain 1.370ms pmtu 1492
2: 41-132-60-1.dsl.mweb.co.za 33.485ms
3: tengig-0-0-0-104.vic-ipc-1.mweb.co.za 43.193ms asymm 7
4: vl-92.vic-hscore-2.mweb.co.za 68.589ms asymm 7
5: TenGigE0-1-0-0.12.vic-up-2.mweb.co.za 67.490ms asymm 8
Click to expand...
 
Will@MWEB said:
Hi wily

If you look at the trace the ms reported at each hop indicates your latency to that point on the network. Looking at which point it starts to climb from can give you an indication of where your problem is. If it increases at the 2nd and 3rd hop that's usually an indication that you're on a congested exchange. Can you take some more traces in the evenings when it's at it's worst and let us see those?

Thanks
Will
Click to expand...


Ok some feedback. We had again rain with added lightning today so my line went completely dead. Works out to be the Duxbury line conditioner that did it's Job and did it well as after some troubleshooting I took it out of the circuit and all worked fine. See the difference below. I hope it stays like this.

Thanks Mwebguy.

>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 READYSHARE [10.0.0.1]
2 2 ms 1 ms 1 ms 192.***.*.*
3 19 ms 19 ms 19 ms 41-133-120-1.dsl.mweb.co.za [41.133.120.
4 21 ms 21 ms 20 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [1
3.206]
5 21 ms 20 ms 20 ms vl-92.vic-hscore-2.mweb.co.za [196.22.18
6 46 ms 42 ms 43 ms TenGigE0-1-0-0.12.vic-up-2.mweb.co.za [1
9.242]
7 46 ms 46 ms 43 ms 197-84-4-34.cpt.mweb.co.za [197.84.4.34]
8 50 ms 51 ms 49 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.1
9 42 ms 41 ms 41 ms 196-28-178-34.adsl.mweb.co.za [196.28.17
10 42 ms 41 ms 41 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Previously
>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 READYSHARE [10.0.0.1]
2 2 ms 13 ms 31 ms ***.***.***
3 64 ms 57 ms 56 ms 41-133-120-1.dsl.mweb.co.za [41.133.120.1]
4 92 ms 60 ms 91 ms 197-80-4-94.jhb.mweb.co.za [197.80.4.94]
5 66 ms 63 ms 62 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
6 117 ms 126 ms 104 ms TenGigE0-1-0-0.12.vic-up-2.mweb.co.za [196.22.16
9.242]
7 135 ms 95 ms 95 ms 197-84-4-34.cpt.mweb.co.za [197.84.4.34]
8 77 ms 80 ms * vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
9 89 ms 85 ms 87 ms 196-28-178-34.adsl.mweb.co.za [196.28.178.34]
10 87 ms 90 ms 89 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...
Last night it was three times worse
Click to expand...
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X