MWEB Uncapped ADSL Feedback - Part 3

SHVAK said:
Nah I do not blame them I trolled the crap out of them. I would have done the same if I was them :)
Click to expand...

ROFLMAO....:D
Sure but it's folks like us that make the difference. If everyone just accepted the status quo, nothing would change.....
I hate me too, but I will get over it. And for the record, I for one was totally entertained by the trolling, so a big THANKS is in order from my side ....

Bet we have the MWEB management at least talking about their silly policy ...us and good few others.:D
 
Mweb Guy, still no news on what you are going to do with speed upgrades? You do realise some people have already been upgraded. I guess a wait and see what happens approach is the new Mweb thing :)
 
SHVAK said:
Mweb Guy, still no news on what you are going to do with speed upgrades? You do realise some people have already been upgraded. I guess a wait and see what happens approach is the new Mweb thing :)
Click to expand...

Hi SHVAK,

No news as yet, as soon as our products have the information we will be posting it on all forums.
 
Meanwhile every other ISP has revised their products and even referred to the Telkom changes on their website.
 
Please can someone interpret these results for me? Tried restarting router already and no difference... :(

Turned off for 15 mins and it seems to be better. General browsing is still slow though. Youtube videos not really loading etc. Something DEFINITELY up...

traceroute www.myadsl.co.za
traceroute to www.myadsl.co.za (197.242.89.170), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2535.169 ms 767.949 ms 1082.901 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 42.343 ms 1629.701 ms 1938.897 ms
3 197-84-96-162.cpt.mweb.co.za (197.84.96.162) 4099.754 ms 844.030 ms *
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 3501.079 ms * 13.759 ms
5 197-84-5-226.cpt.mweb.co.za (197.84.5.226) 23.483 ms
197-84-5-241.cpt.mweb.co.za (197.84.5.241) 140.989 ms
197-84-5-242.cpt.mweb.co.za (197.84.5.242) 55.638 ms
6 197-84-7-5.cpt.mweb.co.za (197.84.7.5) 18.571 ms 22.696 ms 21.039 ms
7 africainx.ct1.napafrica.net (196.46.25.7) 20.208 ms 23.179 ms 20.152 ms
8 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 49.173 ms 63.428 ms 42.015 ms
9 41-66-132-242-f2.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.242) 46.280 ms 46.296 ms 44.564 ms
10 197.189.193.1 (197.189.193.1) 53.508 ms 48.222 ms 50.293 ms
11 197.189.193.62 (197.189.193.62) 55.239 ms 52.787 ms 50.347 ms
12 197.242.89.170 (197.242.89.170) 57.643 ms 50.890 ms 49.632 ms

What on earth is going on around hops 8-12!?

traceroute www.myadsl.co.za
traceroute to www.myadsl.co.za (197.242.89.170), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 13.497 ms 9.435 ms 16.021 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 24.815 ms 11.857 ms 13.116 ms
3 197-84-96-162.cpt.mweb.co.za (197.84.96.162) 12.025 ms 22.213 ms 12.604 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 12.063 ms 21.860 ms 11.302 ms
5 197-84-5-226.cpt.mweb.co.za (197.84.5.226) 21.283 ms
197-84-5-241.cpt.mweb.co.za (197.84.5.241) 27.649 ms
197-84-5-242.cpt.mweb.co.za (197.84.5.242) 25.160 ms
6 197-84-7-5.cpt.mweb.co.za (197.84.7.5) 19.723 ms 21.371 ms 46.239 ms
7 africainx.ct1.napafrica.net (196.46.25.7) 15.063 ms 37.727 ms 72.312 ms
8 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 216.612 ms 336.418 ms 776.586 ms
9 41-66-132-242-f2.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.242) 1161.199 ms * *
10 * 197.189.193.1 (197.189.193.1) 3321.941 ms 2331.053 ms
11 197.189.193.62 (197.189.193.62) 136.666 ms 48.894 ms 541.901 ms
12 197.242.89.170 (197.242.89.170) 892.283 ms 219.415 ms 66.527 ms


PING liveleak.com (208.71.130.253): 56 data bytes
64 bytes from 208.71.130.253: icmp_seq=0 ttl=240 time=250.915 ms
64 bytes from 208.71.130.253: icmp_seq=1 ttl=240 time=273.999 ms
64 bytes from 208.71.130.253: icmp_seq=2 ttl=240 time=241.431 ms
64 bytes from 208.71.130.253: icmp_seq=3 ttl=240 time=447.180 ms
64 bytes from 208.71.130.253: icmp_seq=4 ttl=240 time=904.028 ms
64 bytes from 208.71.130.253: icmp_seq=5 ttl=240 time=386.622 ms
64 bytes from 208.71.130.253: icmp_seq=6 ttl=240 time=248.328 ms
64 bytes from 208.71.130.253: icmp_seq=7 ttl=240 time=311.944 ms
64 bytes from 208.71.130.253: icmp_seq=8 ttl=240 time=334.777 ms
64 bytes from 208.71.130.253: icmp_seq=9 ttl=240 time=256.053 ms
64 bytes from 208.71.130.253: icmp_seq=10 ttl=240 time=378.966 ms
Request timeout for icmp_seq 11
64 bytes from 208.71.130.253: icmp_seq=11 ttl=240 time=1877.726 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
64 bytes from 208.71.130.253: icmp_seq=12 ttl=240 time=3619.251 ms
64 bytes from 208.71.130.253: icmp_seq=13 ttl=240 time=3133.718 ms
64 bytes from 208.71.130.253: icmp_seq=14 ttl=240 time=2598.824 ms
64 bytes from 208.71.130.253: icmp_seq=15 ttl=240 time=2390.290 ms
64 bytes from 208.71.130.253: icmp_seq=16 ttl=240 time=1492.816 ms
64 bytes from 208.71.130.253: icmp_seq=17 ttl=240 time=684.558 ms
64 bytes from 208.71.130.253: icmp_seq=18 ttl=240 time=232.159 ms
64 bytes from 208.71.130.253: icmp_seq=19 ttl=240 time=4094.590 ms

--- liveleak.com ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 232.159/1207.909/4094.590/1246.825 ms
 
Last edited:
Pings up and down every evening for the recent past. Even at midnight it's especially bad:

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

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 368 ms 427 ms 481 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 176 ms 88 ms 80 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 50 ms 16 ms 15 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 191 ms 274 ms 251 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 287 ms 291 ms 391 ms tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
7 506 ms 495 ms 561 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
8 663 ms 588 ms 694 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 410 ms 323 ms 391 ms 64.233.174.57
10 291 ms 424 ms 424 ms jnb01s02-in-f31.1e100.net [74.125.233.95]

Trace complete.

(nothing else running on the line when this was taken)

Edit: I should add that the attenuation, sound etc. are all excellent and have been checked by a Telkom technician. Sad feeling this is down to congestion which will only get worse when the line speeds are upgraded further
 
Last edited:
Dames said:
Please can someone interpret these results for me? Tried restarting router already and no difference... :(

Turned off for 15 mins and it seems to be better. General browsing is still slow though. Youtube videos not really loading etc. Something DEFINITELY up...

traceroute www.myadsl.co.za
traceroute to www.myadsl.co.za (197.242.89.170), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2535.169 ms 767.949 ms 1082.901 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 42.343 ms 1629.701 ms 1938.897 ms
3 197-84-96-162.cpt.mweb.co.za (197.84.96.162) 4099.754 ms 844.030 ms *
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 3501.079 ms * 13.759 ms
5 197-84-5-226.cpt.mweb.co.za (197.84.5.226) 23.483 ms
197-84-5-241.cpt.mweb.co.za (197.84.5.241) 140.989 ms
197-84-5-242.cpt.mweb.co.za (197.84.5.242) 55.638 ms
6 197-84-7-5.cpt.mweb.co.za (197.84.7.5) 18.571 ms 22.696 ms 21.039 ms
7 africainx.ct1.napafrica.net (196.46.25.7) 20.208 ms 23.179 ms 20.152 ms
8 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 49.173 ms 63.428 ms 42.015 ms
9 41-66-132-242-f2.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.242) 46.280 ms 46.296 ms 44.564 ms
10 197.189.193.1 (197.189.193.1) 53.508 ms 48.222 ms 50.293 ms
11 197.189.193.62 (197.189.193.62) 55.239 ms 52.787 ms 50.347 ms
12 197.242.89.170 (197.242.89.170) 57.643 ms 50.890 ms 49.632 ms

What on earth is going on around hops 8-12!?

traceroute www.myadsl.co.za
traceroute to www.myadsl.co.za (197.242.89.170), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 13.497 ms 9.435 ms 16.021 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 24.815 ms 11.857 ms 13.116 ms
3 197-84-96-162.cpt.mweb.co.za (197.84.96.162) 12.025 ms 22.213 ms 12.604 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 12.063 ms 21.860 ms 11.302 ms
5 197-84-5-226.cpt.mweb.co.za (197.84.5.226) 21.283 ms
197-84-5-241.cpt.mweb.co.za (197.84.5.241) 27.649 ms
197-84-5-242.cpt.mweb.co.za (197.84.5.242) 25.160 ms
6 197-84-7-5.cpt.mweb.co.za (197.84.7.5) 19.723 ms 21.371 ms 46.239 ms
7 africainx.ct1.napafrica.net (196.46.25.7) 15.063 ms 37.727 ms 72.312 ms
8 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 216.612 ms 336.418 ms 776.586 ms
9 41-66-132-242-f2.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.242) 1161.199 ms * *
10 * 197.189.193.1 (197.189.193.1) 3321.941 ms 2331.053 ms
11 197.189.193.62 (197.189.193.62) 136.666 ms 48.894 ms 541.901 ms
12 197.242.89.170 (197.242.89.170) 892.283 ms 219.415 ms 66.527 ms


PING liveleak.com (208.71.130.253): 56 data bytes
64 bytes from 208.71.130.253: icmp_seq=0 ttl=240 time=250.915 ms
64 bytes from 208.71.130.253: icmp_seq=1 ttl=240 time=273.999 ms
64 bytes from 208.71.130.253: icmp_seq=2 ttl=240 time=241.431 ms
64 bytes from 208.71.130.253: icmp_seq=3 ttl=240 time=447.180 ms
64 bytes from 208.71.130.253: icmp_seq=4 ttl=240 time=904.028 ms
64 bytes from 208.71.130.253: icmp_seq=5 ttl=240 time=386.622 ms
64 bytes from 208.71.130.253: icmp_seq=6 ttl=240 time=248.328 ms
64 bytes from 208.71.130.253: icmp_seq=7 ttl=240 time=311.944 ms
64 bytes from 208.71.130.253: icmp_seq=8 ttl=240 time=334.777 ms
64 bytes from 208.71.130.253: icmp_seq=9 ttl=240 time=256.053 ms
64 bytes from 208.71.130.253: icmp_seq=10 ttl=240 time=378.966 ms
Request timeout for icmp_seq 11
64 bytes from 208.71.130.253: icmp_seq=11 ttl=240 time=1877.726 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
64 bytes from 208.71.130.253: icmp_seq=12 ttl=240 time=3619.251 ms
64 bytes from 208.71.130.253: icmp_seq=13 ttl=240 time=3133.718 ms
64 bytes from 208.71.130.253: icmp_seq=14 ttl=240 time=2598.824 ms
64 bytes from 208.71.130.253: icmp_seq=15 ttl=240 time=2390.290 ms
64 bytes from 208.71.130.253: icmp_seq=16 ttl=240 time=1492.816 ms
64 bytes from 208.71.130.253: icmp_seq=17 ttl=240 time=684.558 ms
64 bytes from 208.71.130.253: icmp_seq=18 ttl=240 time=232.159 ms
64 bytes from 208.71.130.253: icmp_seq=19 ttl=240 time=4094.590 ms

--- liveleak.com ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 232.159/1207.909/4094.590/1246.825 ms
Click to expand...

TheLaggingShaman said:
Pings up and down every evening for the recent past. Even at midnight it's especially bad:

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

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 368 ms 427 ms 481 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 176 ms 88 ms 80 ms 197-84-96-186.cpt.mweb.co.za [197.84.96.186]
4 50 ms 16 ms 15 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 191 ms 274 ms 251 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 287 ms 291 ms 391 ms tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
7 506 ms 495 ms 561 ms 197-80-7-5.jhb.mweb.co.za [197.80.7.5]
8 663 ms 588 ms 694 ms 197-80-96-6.jhb.mweb.co.za [197.80.96.6]
9 410 ms 323 ms 391 ms 64.233.174.57
10 291 ms 424 ms 424 ms jnb01s02-in-f31.1e100.net [74.125.233.95]

Trace complete.

(nothing else running on the line when this was taken)

Edit: I should add that the attenuation, sound etc. are all excellent and have been checked by a Telkom technician. Sad feeling this is down to congestion which will only get worse when the line speeds are upgraded further
Click to expand...

Guys I'm not being funny here but I feel it could be related to Telkom Exchange congestion and upgrades have commenced from the 11th so I think we may see high latency issues to most users on the network :( It's quite sad for us Internet-holics but hopefully this will be all over soon in certain areas as the upgrades are finalized in batches.
 
GreatD7007 said:
Guys I'm not being funny here but I feel it could be related to Telkom Exchange congestion and upgrades have commenced from the 11th so I think we may see high latency issues to most users on the network :( It's quite sad for us Internet-holics but hopefully this will be all over soon in certain areas as the upgrades are finalized in batches.
Click to expand...

All we can do now is be patient and hope Telkom don't play silly buggers ;)
 
GreatD7007 said:
Guys I'm not being funny here but I feel it could be related to Telkom Exchange congestion and upgrades have commenced from the 11th so I think we may see high latency issues to most users on the network :( It's quite sad for us Internet-holics but hopefully this will be all over soon in certain areas as the upgrades are finalized in batches.
Click to expand...

I didn't think of that! And now when I think about it, last night was the first time it's been SO bad. I've never seen stuff jumping up and down so much on our line before. I just hope this is temporary, because ADSL is virtually unusable like this.

Edit: MWEB Guy, what say you?
 
Dames said:
I didn't think of that! And now when I think about it, last night was the first time it's been SO bad. I've never seen stuff jumping up and down so much on our line before. I just hope this is temporary, because ADSL is virtually unusable like this.

Edit: MWEB Guy, what say you?
Click to expand...


Morning Dames I agree, seeing the spike as early as the 2nd hop can point to a congested exchange.
 
MWEB Guy said:
Morning Dames I agree, seeing the spike as early as the 2nd hop can point to a congested exchange.
Click to expand...

And with the below?

What on earth is going on around hops 8-12!?

traceroute www.myadsl.co.za
traceroute to www.myadsl.co.za (197.242.89.170), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 13.497 ms 9.435 ms 16.021 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 24.815 ms 11.857 ms 13.116 ms
3 197-84-96-162.cpt.mweb.co.za (197.84.96.162) 12.025 ms 22.213 ms 12.604 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 12.063 ms 21.860 ms 11.302 ms
5 197-84-5-226.cpt.mweb.co.za (197.84.5.226) 21.283 ms
197-84-5-241.cpt.mweb.co.za (197.84.5.241) 27.649 ms
197-84-5-242.cpt.mweb.co.za (197.84.5.242) 25.160 ms
6 197-84-7-5.cpt.mweb.co.za (197.84.7.5) 19.723 ms 21.371 ms 46.239 ms
7 africainx.ct1.napafrica.net (196.46.25.7) 15.063 ms 37.727 ms 72.312 ms
8 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 216.612 ms 336.418 ms 776.586 ms
9 41-66-132-242-f2.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.242) 1161.199 ms * *
10 * 197.189.193.1 (197.189.193.1) 3321.941 ms 2331.053 ms
11 197.189.193.62 (197.189.193.62) 136.666 ms 48.894 ms 541.901 ms
12 197.242.89.170 (197.242.89.170) 892.283 ms 219.415 ms 66.527 ms
 
Dames said:
And with the below?

What on earth is going on around hops 8-12!?

traceroute www.myadsl.co.za
traceroute to www.myadsl.co.za (197.242.89.170), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 13.497 ms 9.435 ms 16.021 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 24.815 ms 11.857 ms 13.116 ms
3 197-84-96-162.cpt.mweb.co.za (197.84.96.162) 12.025 ms 22.213 ms 12.604 ms
4 197-84-2-2.cpt.mweb.co.za (197.84.2.2) 12.063 ms 21.860 ms 11.302 ms
5 197-84-5-226.cpt.mweb.co.za (197.84.5.226) 21.283 ms
197-84-5-241.cpt.mweb.co.za (197.84.5.241) 27.649 ms
197-84-5-242.cpt.mweb.co.za (197.84.5.242) 25.160 ms
6 197-84-7-5.cpt.mweb.co.za (197.84.7.5) 19.723 ms 21.371 ms 46.239 ms
7 africainx.ct1.napafrica.net (196.46.25.7) 15.063 ms 37.727 ms 72.312 ms
8 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 216.612 ms 336.418 ms 776.586 ms
9 41-66-132-242-f2.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.242) 1161.199 ms * *
10 * 197.189.193.1 (197.189.193.1) 3321.941 ms 2331.053 ms
11 197.189.193.62 (197.189.193.62) 136.666 ms 48.894 ms 541.901 ms
12 197.242.89.170 (197.242.89.170) 892.283 ms 219.415 ms 66.527 ms
Click to expand...

I tell you what, I have escalated this to our specialists to contact you.

Your ref number is 1280325
 
Dames said:
Why thank you MWEB Guy :)

Will only be able to check everything later when I'm home from work though.
Click to expand...

You should be called around 20:30 tonight. It could be before, depending on the previous calls scheduled.
 
Hi Mweb guy,

I have posted on here before regarding problems and was hoping you could help me out again. On our business ADSL line (4mbit) we are having massive issues with latency/packet loss for the past week or so. I have called Telkom and they say the line is fine. we have also performed a port reset.

I found this listed under the Network Status Notices section:

Outage Num:17641
Telkom ADSL outage affecting Kraaifontein ( 021 - 987, 988 )
Telkom ADSL services in the following area may be Inaccessible : Kraaifontein ( 021 - 987, 988 )
Start Date:2013-11-11 11:44:09
End Date:
Status:Open

Does this explain our issues? I am not seeing the same thing at home (same area) which is why I am asking. Basically we have massive latency and/or packet loss anytime any kind of traffic is started on the line. Here is an example of high latency anytime any kind of traffic is initiated: http://gyazo.com/a7f086ac186b0a9542bc157ebcd36d50

Any help you could provide would be appreciated.
 
Last edited:
KRayn3r said:
Hi Mweb guy,

I have posted on here before regarding problems and was hoping you could help me out again. On our business ADSL line (4mbit) we are having massive issues with latency/packet loss for the past week or so. I have called Telkom and they say the line is fine. we have also performed a port reset.

I found this listed under the Network Status Notices section:

Outage Num:17641
Telkom ADSL outage affecting Kraaifontein ( 021 - 987, 988 )
Telkom ADSL services in the following area may be Inaccessible : Kraaifontein ( 021 - 987, 988 )
Start Date:2013-11-11 11:44:09
End Date:
Status:Open

Does this explain our issues? I am not seeing the same thing at home (same area) which is why I am asking. Basically we have massive latency and/or packet loss anytime any kind of traffic is started on the line. Here is an example of high latency anytime any kind of traffic is initiated: http://gyazo.com/a7f086ac186b0a9542bc157ebcd36d50

Any help you could provide would be appreciated.
Click to expand...

Hi KRayn3r

If there is an outage then there will be no connectivity at all. The traffic og the outage area is also not re-direct to a different exchange.

Please provide me with the Business account details and I'll have a Premier department make contact with you.
 
Dames said:
I didn't think of that! And now when I think about it, last night was the first time it's been SO bad. I've never seen stuff jumping up and down so much on our line before. I just hope this is temporary, because ADSL is virtually unusable like this.

Edit: MWEB Guy, what say you?
Click to expand...

MWEB Guy said:
Morning Dames I agree, seeing the spike as early as the 2nd hop can point to a congested exchange.
Click to expand...

Yeah it's unfortunate but it will be worth it in the end, trust me. I can't wait for the upgrades to take place but hope its not too long a wait from now! :) Sorry to hear about your congested exchange, mine was congested last week. Bad latencies :(
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X