MWEB Uncapped ADSL Feedback - Part 3

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 2 ms 3 ms 2 ms 192.168.1.1
2 82 ms 74 ms 79 ms 41-132-42-1.dsl.mweb.co.za [41.132.42.1]
3 110 ms 69 ms 78 ms 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
4 68 ms 62 ms 39 ms vl-92-cpt-hscore-2.mweb.co.za [197.84.3.2]
5 53 ms 46 ms 46 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
6 88 ms 93 ms 66 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
7 41 ms 26 ms 40 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
8 13 ms 18 ms 39 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
9 59 ms 41 ms 68 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 2 ms 8 ms 6 ms 192.168.1.1
2 68 ms 76 ms 69 ms 41-132-42-1.dsl.mweb.co.za [41.132.42.1]
3 74 ms 59 ms 67 ms 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
4 49 ms 41 ms 55 ms vl-92-cpt-hscore-2.mweb.co.za [197.84.3.2]
5 177 ms 173 ms 173 ms tengig-0-7-0-2-12-cpt-p-1.mweb.co.za [197.84.5.241]
6 173 ms 186 ms 180 ms tengig-0-7-0-0-cpt-p-2.mweb.co.za [197.84.4.32]
7 163 ms 176 ms 180 ms w1-pos0-3-3-0-pos0-3-4-1.thd-p-1.mweb.co.za [197.84.4.195]
8 234 ms 239 ms 228 ms be-69-thd-p-2.mweb.co.za [176.67.177.162]
9 191 ms 179 ms 169 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
10 190 ms 190 ms 171 ms be-15-777-thd-linx-1.mweb.co.za [176.67.177.133]
11 163 ms 173 ms 163 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
12 161 ms 185 ms 199 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 183 ms 177 ms 172 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 10.0 megabytes in 1:30 seconds. (113.00 KB/s)

Local Speedtest
Downloaded 8000.0 kilobytes in 1:24 seconds. (94.95 KB/s)




Test End Timestamp
2014-06-09 23:56:32,33
 
acidrain said:
Is there an issue in the diep river, cape town area?

Account is showing unthrottled but only getting 1.8Mbps on speedtest ( 4Meg Premium Uncapped ). Also been noticing lag spikes in dota.
Click to expand...

acidrain said:
Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 2 ms 3 ms 2 ms 192.168.1.1
2 82 ms 74 ms 79 ms 41-132-42-1.dsl.mweb.co.za [41.132.42.1]
3 110 ms 69 ms 78 ms 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
4 68 ms 62 ms 39 ms vl-92-cpt-hscore-2.mweb.co.za [197.84.3.2]
5 53 ms 46 ms 46 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
6 88 ms 93 ms 66 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
7 41 ms 26 ms 40 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
8 13 ms 18 ms 39 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
9 59 ms 41 ms 68 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 2 ms 8 ms 6 ms 192.168.1.1
2 68 ms 76 ms 69 ms 41-132-42-1.dsl.mweb.co.za [41.132.42.1]
3 74 ms 59 ms 67 ms 197-84-96-162.cpt.mweb.co.za [197.84.96.162]
4 49 ms 41 ms 55 ms vl-92-cpt-hscore-2.mweb.co.za [197.84.3.2]
5 177 ms 173 ms 173 ms tengig-0-7-0-2-12-cpt-p-1.mweb.co.za [197.84.5.241]
6 173 ms 186 ms 180 ms tengig-0-7-0-0-cpt-p-2.mweb.co.za [197.84.4.32]
7 163 ms 176 ms 180 ms w1-pos0-3-3-0-pos0-3-4-1.thd-p-1.mweb.co.za [197.84.4.195]
8 234 ms 239 ms 228 ms be-69-thd-p-2.mweb.co.za [176.67.177.162]
9 191 ms 179 ms 169 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
10 190 ms 190 ms 171 ms be-15-777-thd-linx-1.mweb.co.za [176.67.177.133]
11 163 ms 173 ms 163 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
12 161 ms 185 ms 199 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 183 ms 177 ms 172 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 10.0 megabytes in 1:30 seconds. (113.00 KB/s)

Local Speedtest
Downloaded 8000.0 kilobytes in 1:24 seconds. (94.95 KB/s)




Test End Timestamp
2014-06-09 23:56:32,33
Click to expand...

Morning acidrain

I would like to look further into this from our side. Please PM me the MWEB username and I will provide you with more information.
 
Horrible speeds again. Strangely though the below figures keeps on changing heavily during the day at random times. For example the second hop starts with 296 but earlier it was 50-60 something.

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

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 296 ms 288 ms 316 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 325 ms 341 ms 321 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 350 ms 388 ms 368 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 361 ms 451 ms 403 ms 196.28.178.66
6 438 ms 420 ms 369 ms cte-core-sw2.vwol.net [196.41.144.35]
7 479 ms 485 ms 485 ms www.mweb.co.za [196.2.63.110]

Speedtests looks fine. I've only started having this problem since about a week ago. Rather odd.

Edit , second run 10 seconds later

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

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 405 ms 393 ms 352 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 329 ms 318 ms 336 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 443 ms 441 ms 440 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 419 ms 417 ms 432 ms 196.28.178.66
6 326 ms 401 ms 423 ms cte-core-sw2.vwol.net [196.41.144.35]
7 481 ms 469 ms 387 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Last edited:
DarKWateR said:
Horrible speeds again. Strangely though the below figures keeps on changing heavily during the day at random times. For example the second hop starts with 296 but earlier it was 50-60 something.

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

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 296 ms 288 ms 316 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 325 ms 341 ms 321 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 350 ms 388 ms 368 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 361 ms 451 ms 403 ms 196.28.178.66
6 438 ms 420 ms 369 ms cte-core-sw2.vwol.net [196.41.144.35]
7 479 ms 485 ms 485 ms www.mweb.co.za [196.2.63.110]

Speedtests looks fine. I've only started having this problem since about a week ago. Rather odd.

Edit , second run 10 seconds later

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

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 405 ms 393 ms 352 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 329 ms 318 ms 336 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 443 ms 441 ms 440 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 419 ms 417 ms 432 ms 196.28.178.66
6 326 ms 401 ms 423 ms cte-core-sw2.vwol.net [196.41.144.35]
7 481 ms 469 ms 387 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Looking at these trace routes it looks a lot like a congested exchange.

Do you have a different ISP account that you can do a trace route on so that we have a comparison ?
 
acidrain said:
Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 2 ms 3 ms 2 ms 192.168.1.1
2 82 ms 74 ms 79 ms 41-132-42-1.dsl.mweb.co.za [41.132.42.1]
Click to expand...

Your problem is Telkom side. Your second hop should be <20ms. This points to congestion.
 
DarKWateR said:
Horrible speeds again. Strangely though the below figures keeps on changing heavily during the day at random times. For example the second hop starts with 296 but earlier it was 50-60 something.

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

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 296 ms 288 ms 316 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 325 ms 341 ms 321 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 350 ms 388 ms 368 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 361 ms 451 ms 403 ms 196.28.178.66
6 438 ms 420 ms 369 ms cte-core-sw2.vwol.net [196.41.144.35]
7 479 ms 485 ms 485 ms www.mweb.co.za [196.2.63.110]

Speedtests looks fine. I've only started having this problem since about a week ago. Rather odd.

Edit , second run 10 seconds later

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

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 405 ms 393 ms 352 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 329 ms 318 ms 336 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 443 ms 441 ms 440 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 419 ms 417 ms 432 ms 196.28.178.66
6 326 ms 401 ms 423 ms cte-core-sw2.vwol.net [196.41.144.35]
7 481 ms 469 ms 387 ms www.mweb.co.za [196.2.63.110]

Trace complete.
Click to expand...

Please see my above reply, your fault is on Telkom's end, not MWEB's.
 
so looks like everything is back to normal again

Code: 
Local Tracert 

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

  1     7 ms    35 ms     3 ms  192.168.1.1 
  2    12 ms    16 ms    21 ms  41-132-42-1.dsl.mweb.co.za [41.132.42.1] 
  3    18 ms    18 ms    13 ms  197-84-96-162.cpt.mweb.co.za [197.84.96.162] 
  4    12 ms    13 ms    14 ms  vl-92-cpt-hscore-2.mweb.co.za [197.84.3.2] 
  5    15 ms    23 ms    22 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
  6    21 ms    14 ms    12 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
  7    17 ms    13 ms    13 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
  8    14 ms    14 ms    13 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
  9    13 ms    19 ms    19 ms  41-86-110-143.mweb.co.za [41.86.110.143] 

Trace complete.
  
International Tracert 

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1     8 ms    35 ms    39 ms  192.168.1.1 
  2    13 ms    12 ms    12 ms  41-132-42-1.dsl.mweb.co.za [41.132.42.1] 
  3    12 ms    12 ms    13 ms  197-84-96-162.cpt.mweb.co.za [197.84.96.162] 
  4    14 ms    15 ms    17 ms  vl-92-cpt-hscore-2.mweb.co.za [197.84.3.2] 
  5   163 ms   161 ms   159 ms  tengig-0-7-0-2-12-cpt-p-1.mweb.co.za [197.84.5.241] 
  6   158 ms   160 ms   159 ms  tengig-0-7-0-0-cpt-p-2.mweb.co.za [197.84.4.32] 
  7   162 ms   163 ms   161 ms  w1-pos0-3-3-0-pos0-3-4-1.thd-p-1.mweb.co.za [197.84.4.195] 
  8   159 ms   159 ms   160 ms  be-69-thd-p-2.mweb.co.za [176.67.177.162] 
  9   157 ms   164 ms   160 ms  be-3-777-thd-up-1.mweb.co.za [176.67.177.131] 
 10   181 ms   164 ms   160 ms  be-15-777-thd-linx-1.mweb.co.za [176.67.177.133] 
 11   169 ms   157 ms   157 ms  linx-gw2.thdo.ncuk.net [195.66.236.240] 
 12   158 ms   166 ms   158 ms  te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 13   161 ms   158 ms   158 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.
  
International Speedtest 
Downloaded 10.0 megabytes in 29 seconds. (347.77 KB/s)
  
Local Speedtest 
Downloaded 8000.0 kilobytes in 23 seconds. (333.56 KB/s)
  
  
  
  
Test End Timestamp 
2014-06-10 18:49:55,30
 
I'm such a noob on these things, but I've had to switch my modem/router off and on at least 20 times today. Usually it is a couple of times but now it is unbearable.

A traceroute shows this...

traceroute to mweb.co.za (196.2.63.110), 64 hops max, 52 byte packets
1 10.0.0.2 (10.0.0.2) 7.829 ms 2.745 ms 1.240 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 13.154 ms 13.577 ms 16.605 ms
3 197-84-96-186.cpt.mweb.co.za (197.84.96.186) 14.155 ms 17.220 ms 14.681 ms
4 vl-92-cpt-hscore-1.mweb.co.za (197.84.2.2) 17.574 ms 16.697 ms 18.970 ms
5 196.28.178.66 (196.28.178.66) 21.589 ms 22.979 ms 82.922 ms
6 cte-core-sw2.vwol.net (196.41.144.35) 16.375 ms 14.443 ms 14.933 ms
7 * * *
8 * * *
Click to expand...

And so the * continue on and on. 15 is the highest I've gone. Anyone got any ideas?

I'm on a 4mb premium account btw.
 
Tried a different destination and it went well. Seems like mweb is the problem????

traceroute to news24.com (41.86.110.143), 64 hops max, 52 byte packets
1 10.0.0.2 (10.0.0.2) 1.663 ms 1.323 ms 0.972 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 55.010 ms 64.809 ms 65.602 ms
3 197-84-96-186.cpt.mweb.co.za (197.84.96.186) 66.051 ms 59.768 ms 54.676 ms
4 vl-92-cpt-hscore-2.mweb.co.za (197.84.3.2) 48.197 ms
vl-92-cpt-hscore-1.mweb.co.za (197.84.2.2) 28.608 ms
vl-92-cpt-hscore-2.mweb.co.za (197.84.3.2) 26.138 ms
5 196.28.178.66 (196.28.178.66) 26.202 ms
vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 30.643 ms
196.28.178.66 (196.28.178.66) 105.441 ms
6 gig5-2-cpt-opt-65-1.optinet.net (196.41.133.166) 42.196 ms
gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 41.322 ms
gig5-2-cpt-opt-65-1.optinet.net (196.41.133.166) 49.152 ms
7 opti-cpt-n1-hosting.optinet.net (197.84.196.6) 63.616 ms 51.018 ms 48.983 ms
8 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 41.272 ms 48.959 ms 53.525 ms
9 news24.com (41.86.110.143) 49.788 ms 47.722 ms 46.309 ms
Click to expand...

Edit: I should mention I've got unodns settings in my modem. Not sure how that affects things???
 
Spizz said:
Tried a different destination and it went well. Seems like mweb is the problem????



Edit: I should mention I've got unodns settings in my modem. Not sure how that affects things???
Click to expand...

Firstly you should try another ISP, like a free GB from Afrihost and/or WebAfrica.

Perhaps also try the 'automatic DNS/retrieve from ISP' in your router?
 
PostmanPot said:
Firstly you should try another ISP, like a free GB from Afrihost and/or WebAfrica.

Perhaps also try the 'automatic DNS/retrieve from ISP' in your router?
Click to expand...

Problem is the disconnects have little or no pattern. They can go a day or so without a problem then bang, once an hour. And a gig lasts about 5 minutes in my house so I'm thinking I need to trial 10 gigs or so over a day or two. I'll check out the DNS tip in the morning though and see what MWEB Guy says about the traceroute.

Cheers.
 
Spizz;12834559 I'll check out the DNS tip in the morning though and see what MWEB Guy says about the traceroute.[/QUOTE said:
Gonna blame Telkom.

Ask MWEB Guy for DNS settings on the router.

For interests sake, what router is it .... TP Link / Belkin?
Click to expand...
 
Spizz said:
Problem is the disconnects have little or no pattern. They can go a day or so without a problem then bang, once an hour. And a gig lasts about 5 minutes in my house so I'm thinking I need to trial 10 gigs or so over a day or two. I'll check out the DNS tip in the morning though and see what MWEB Guy says about the traceroute.

Cheers.
Click to expand...

Disconnects = Telkom/router. I would strongly suggest purchasing a D-Link DSL-2500 single port ADSL modem/router for <R250 in order to test (friends/family can borrow it too).

Otherwise, regarding DNS, should be similar on the DSL-2750:

fzyNh2m.png


But I don't think it'll solve your problems. In any case, rather try use the above setting instead of other DNSes/services IMO.
 
MWEB Guy said:
Looking at these trace routes it looks a lot like a congested exchange.

Do you have a different ISP account that you can do a trace route on so that we have a comparison ?
Click to expand...

Hi again..

I don't have another ADSL account but id a tracert again this evening...

Tracing route to www.saix.net [196.25.1.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 338 ms 343 ms 319 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 352 ms 367 ms 406 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 475 ms 509 ms 486 ms vl-92-cpt-hscore-2.mweb.co.za [197.84.3.2]
5 315 ms 324 ms 296 ms tengig-0-7-0-2-12-cpt-p-1.mweb.co.za [197.84.5.2
41]
6 279 ms 317 ms 356 ms 197-84-7-5.cpt.mweb.co.za [197.84.7.5]
7 342 ms 351 ms 400 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 443 ms 436 ms 458 ms 196.43.25.205
9 434 ms 426 ms 409 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
10 * * wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.
30] reports: Destination net unreachable.

Trace complete.

Then I simply disconnect and reconnected...

Tracing route to www.saix.net [196.25.1.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ADSL [192.168.1.1]
2 20 ms 15 ms 13 ms 41-132-70-1.dsl.mweb.co.za [41.132.70.1]
3 8 ms 8 ms 8 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 16 ms 28 ms 26 ms vl-92-cpt-hscore-1.mweb.co.za [197.84.2.2]
5 12 ms 12 ms 12 ms tengig-0-0-0-2-11-cpt-p-1.mweb.co.za [197.84.5.2
25]
6 13 ms 20 ms 26 ms 197-84-7-5.cpt.mweb.co.za [197.84.7.5]
7 34 ms 33 ms 31 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 19 ms 18 ms 16 ms 196.43.25.205
9 8 ms 8 ms 8 ms wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [1
96.43.11.22]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [196.43.11.22] reports: Dest
ination net unreachable.

Trace complete.

:confused:
 
PostmanPot said:
Disconnects = Telkom/router. I would strongly suggest purchasing a D-Link DSL-2500 single port ADSL modem/router for <R250 in order to test (friends/family can borrow it too).
Click to expand...

This ^^

Borrow a router, or if finance permits get a spare. I seem to chew thru routers like mad.

Routers go faulty for no apparent reason. I have one out of box failure.

Hey, didnt MWEB give you a FON ??
 
Last edited:
DarKWateR said:
Hi again..

I don't have another ADSL account but id a tracert again this evening...
Click to expand...

AH Free account - just need to send them ID.

Would be interesting to see tracert from MWEB followed by AH.

Disconnect router from power for a short time and reconnect? Is it a FONNY router??
 
TEXTILE GUY said:
This ^^

Borrow a router, or if finance permits get a spare. I seem to chew thru routers like mad.

Routers go faulty for no apparent reason. I have one out of box failure.

Hey, didnt MWEB give you a FON ??
Click to expand...

Yeah, but I can't put the unotelly DNS settings on it so it's still in the box. Not sure if that situation has changed yet?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X