MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
MWEB Guy said:
Hi subxero

"He especially pointed out that I am in no way a heavy downloader so 'should not be shaped so heavily' - his words."

I listened to the call and he did not say you shouldn't be shaped so heavily because you not a heavy downloader.

As I mentioned; we do not shape individuals.


As per your conversation with the technical specialist you'll monitor and provide feedback. Please let me know if you are encountering any speeds issues on normal HTTP downloads?
Click to expand...
Not interested anymore. The speed issue seems to be a spreading epidemic from what I have read. As for the phone discussion - you may have your interpretation - I have mine. If you had read my feedback, you would have noticed that it is http as well as nntp. That said, no-one chooses to pay for a 2mb service just for http browsing. That can be done sufficiently on a 1mb account. To shape popular download protocols as heavily as Mweb is doing at the moment, negates the need for a 2mb account. My experience with MWeb has degraded dramatically over the past month. Instead of positive feedback, I am seeing issues being avoided - which tells me there is no plan in place to rectify the situation. If my Mweb account is to perform the same as the cheap entry level accounts with other providers, then I no longer enjoy paying that much extra every month. It does not make sense. I still refer to Will stating he is getting 400kbps using nntp with Astraweb at the same time that I was getting a mere 30kbps. I am not saying I am being shaped as an individual, but it certainly can bee seen that way.

I enjoyed Mweb while it was performing, but fail to see any reason to stay when there is obvious denial that anything has changed since the beginning of the month.

Edit: You need not respond. My mind is made up. I will ignore this thread from now on.
 
Last edited:
Same boat here, speeds have gone to poo, getting half my line speed of 4mb not matter what http downloads i run, even if i use a download manager!!!!
 
Luloz.jpg


No complaints here!
 
subxero said:
Spoke too soon. NNTP back to 25-30kbps tonight. General web browsing on stock image sites = 40-80kbps max. Poor, very poor! Not into this anymore. It is pointless paying Telkom for the 2mb line rental and Mweb for a 2mb account which runs @ under 1mb speeds.

Your technical guy calls me on Saturday and guess what? Speeds were up to 200kbps all of the sudden. I explained the issue to him with regards to NNTP and the heavy shaping over the past month and he agreed that this is not the experience I should be having. He especially pointed out that I am in no way a heavy downloader so 'should not be shaped so heavily' - his words.

Edit: I may as well move to Telkom uncapped and make everything their fault! But I am not a sucker for that kind of punishment and will have to find another solution.
Click to expand...

Firstly the response you got in terms of shaping is not correct and I do apologize for this.

Traffic prioritization is a fixed set of rules applied on traffic classifications, basically ranging from traffic with Assurance Level 10 (top priority) down to Assurance Level 1 (yes it's torrents). These rules apply across the entire network for all customers on Shaped products.

There is absolutely no mechanism in place which adjusts the shaping experience for an individual user or is in any way linked to their usage.

Speeds on protocols like NNTP and p2p are going to fluctuate when the network is busy, we've never made a secret of this and honestly as much as do our level best to carry out upgrades proactively and predict future demands we can't promise you that the network utilization isn't going to spike at times.

To expect this and to expect that protocols of this type are going to hum along at line speeds 24/7 is really unrealistic.

Also if you're having NNTP problems you need to clarify what service you're using. The MWEB news server is a best effort service and I wont lie to you - it's not very fast :) As a comparison I ran a 24 hour test last week on an Astraweb account using a standard shaped 4mb account and the speed during peak network load did not drop below 350KB/s

I have been taking careful note of performance complaints coming through recently and I have monitoring and testing various aspects of the customer experience and making a general nuisance of myself with the engineers to try and determine the extent to which these complaints are related to our own network and which are isolated to certain customers/regions and are most likely a result of increased load on the Telkom infrastructure due to line speed upgrades.

My conclusions currently:

Yes there has been an increased load on our own network, however we are monitoring the situation very carefully and have it well in hand. Any slight pressure we are feeling on our own network right now is having a minimal impact on the customer experience and will be alleviated by regular schedule IPC upgrades taking place within the next week.

We are also seeing a number of issues filtering through in terms of poor customer experience post line-speed upgrades and these simply have to be investigated on a case by case basis. Not all upgraded lines are achieving the desired speeds and the truth is that some customers may need to be realistic about what their physical lines and exchanges are currently capable of.
 
Last edited:
Its seems you guys are waiting an awfully long time to fix something people have been complaining about week after week. It worries me that normal http or https traffic has started struggling on your network.

I must say, the degradation of the Mweb network is becoming more and more apparent, i truly hope you guys address the issues within "within the week"
 
For nearly 2 weeks now the latency of my line has been as follows:

Between ~6pm to 11pm


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

1 6 ms <1 ms <1 ms 192.168.0.254
2 138 ms 124 ms 107 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 105 ms 106 ms 92 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 88 ms 79 ms 85 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 122 ms 132 ms 124 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 88 ms 86 ms 88 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
7 135 ms 117 ms 141 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 135 ms 139 ms 144 ms 196.28.178.66
9 108 ms 118 ms 127 ms cte-core-sw2.vwol.net [196.41.144.35]
10 166 ms 185 ms 187 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to btlac2-adsl-gw1.altohiway.com [195.12.0.234]
over a maximum of 14 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 76 ms 79 ms 85 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 107 ms 111 ms 93 ms 197-80-4-106.jhb.mweb.co.za [197.80.4.106]
4 118 ms 137 ms * vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 294 ms 316 ms 284 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 315 ms 295 ms 286 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 269 ms 296 ms 321 ms 176.67.177.131
8 245 ms 255 ms 256 ms 176.67.177.133
9 209 ms 209 ms 223 ms ae1-scr010.sov.as13285.net [195.66.236.136]
10 270 ms 282 ms 295 ms host-78-144-1-138.as13285.net [78.144.1.138]
11 308 ms 326 ms 315 ms xe-10-1-0-scr001.thn.as13285.net [78.144.0.236]
12 293 ms 280 ms 258 ms host-78-144-0-164.as13285.net [78.144.0.164]
13 347 ms 223 ms 247 ms host-78-144-3-77.as13285.net [78.144.3.77]
14 * * * Request timed out.


Trace complete.

And then from 12pm:


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.254
2 11 ms 10 ms 10 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 12 ms 13 ms 11 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 13 ms 13 ms 14 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 39 ms 39 ms 39 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 42 ms 39 ms 39 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
7 34 ms 42 ms 45 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 32 ms 32 ms 31 ms 196.28.178.66
9 32 ms 32 ms 32 ms cte-core-sw2.vwol.net [196.41.144.35]
10 36 ms 33 ms 33 ms www.mweb.co.za [196.2.63.110]

Trace complete.


Tracing route to 195.12.234.168 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.0.254
2 13 ms 17 ms 16 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 13 ms 19 ms 16 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 19 ms 16 ms 15 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 194 ms 197 ms 193 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 192 ms 202 ms 194 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 198 ms 196 ms 196 ms 176.67.177.131
8 216 ms 195 ms 193 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 191 ms 191 ms 197 ms vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
10 191 ms 191 ms 191 ms ae-2-52.edge5.London1.Level3.net [4.69.139.107]
11 195 ms 194 ms 193 ms ldn-b5-link.telia.net [213.248.92.81]
12 191 ms 193 ms 194 ms ldn-bb1-link.telia.net [80.91.246.96]
13 216 ms 252 ms 205 ms prs-bb1-link.telia.net [213.155.134.36]
14 202 ms 206 ms 202 ms prs-b4-link.telia.net [80.91.251.112]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Already had Telkom test the line and reset the ports, but to no effect.
 
Wow, 45mins to download 40mb MSE update. An all time low for MWEB, know i wonder if i should have recommended so many people to join the network. cant get anything higher than 100kb on http!!
 
news.mweb.co.za is totally dead http downloads reminds me of the days of dialup, whats happening seems things are going from bad to worse....maybe its time to move on and find another ISP...after 12-13 years with mweb this is the pits

Edit: News.mweb.co.za just started crawling againg 20 - 27 kB/s
 
Last edited:
M10 said:
For nearly 2 weeks now the latency of my line has been as follows:

Between ~6pm to 11pm


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

1 6 ms <1 ms <1 ms 192.168.0.254
2 138 ms 124 ms 107 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 105 ms 106 ms 92 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 88 ms 79 ms 85 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 122 ms 132 ms 124 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 88 ms 86 ms 88 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
7 135 ms 117 ms 141 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 135 ms 139 ms 144 ms 196.28.178.66
9 108 ms 118 ms 127 ms cte-core-sw2.vwol.net [196.41.144.35]
10 166 ms 185 ms 187 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Tracing route to btlac2-adsl-gw1.altohiway.com [195.12.0.234]
over a maximum of 14 hops:

1 <1 ms <1 ms <1 ms 192.168.0.254
2 76 ms 79 ms 85 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 107 ms 111 ms 93 ms 197-80-4-106.jhb.mweb.co.za [197.80.4.106]
4 118 ms 137 ms * vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 294 ms 316 ms 284 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 315 ms 295 ms 286 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 269 ms 296 ms 321 ms 176.67.177.131
8 245 ms 255 ms 256 ms 176.67.177.133
9 209 ms 209 ms 223 ms ae1-scr010.sov.as13285.net [195.66.236.136]
10 270 ms 282 ms 295 ms host-78-144-1-138.as13285.net [78.144.1.138]
11 308 ms 326 ms 315 ms xe-10-1-0-scr001.thn.as13285.net [78.144.0.236]
12 293 ms 280 ms 258 ms host-78-144-0-164.as13285.net [78.144.0.164]
13 347 ms 223 ms 247 ms host-78-144-3-77.as13285.net [78.144.3.77]
14 * * * Request timed out.


Trace complete.

And then from 12pm:


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.254
2 11 ms 10 ms 10 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 12 ms 13 ms 11 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 13 ms 13 ms 14 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 39 ms 39 ms 39 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 42 ms 39 ms 39 ms TenGigE0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
7 34 ms 42 ms 45 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
8 32 ms 32 ms 31 ms 196.28.178.66
9 32 ms 32 ms 32 ms cte-core-sw2.vwol.net [196.41.144.35]
10 36 ms 33 ms 33 ms www.mweb.co.za [196.2.63.110]

Trace complete.


Tracing route to 195.12.234.168 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.0.254
2 13 ms 17 ms 16 ms 41-133-136-1.dsl.mweb.co.za [41.133.136.1]
3 13 ms 19 ms 16 ms 197-80-4-82.jhb.mweb.co.za [197.80.4.82]
4 19 ms 16 ms 15 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 194 ms 197 ms 193 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 192 ms 202 ms 194 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 198 ms 196 ms 196 ms 176.67.177.131
8 216 ms 195 ms 193 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.133]
9 191 ms 191 ms 197 ms vl-3602-ve-226.csw2.London1.Level3.net [4.69.166.149]
10 191 ms 191 ms 191 ms ae-2-52.edge5.London1.Level3.net [4.69.139.107]
11 195 ms 194 ms 193 ms ldn-b5-link.telia.net [213.248.92.81]
12 191 ms 193 ms 194 ms ldn-bb1-link.telia.net [80.91.246.96]
13 216 ms 252 ms 205 ms prs-bb1-link.telia.net [213.155.134.36]
14 202 ms 206 ms 202 ms prs-b4-link.telia.net [80.91.251.112]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Already had Telkom test the line and reset the ports, but to no effect.
Click to expand...

Hi M10

I must say, at first glance it does seem like it could be a congestion issue.
Have you tried another ISP account yet as a test to see if you get similar results.
6pm -11pm is peak time and would explain why i seems like more traffic is flowing through your exchange at those time.

Don't get me wrong, not trying to blame Telkom but the results speak for itself.
An hour later and things seem to be running fine.
 
AmonRe said:
Wow, 45mins to download 40mb MSE update. An all time low for MWEB, know i wonder if i should have recommended so many people to join the network. cant get anything higher than 100kb on http!!
Click to expand...

Thanks for the feedback, please see my reply to your PM.
 
News.mweb.co.za 35-41 KB/s, would have hoped it would have been a little faster at this time of the day.

Edit: 6 am and going at 33-38 KB/s
 
Last edited:
Reign said:
havent recieved any feedback problem still exists....
Click to expand...

Hi

I have not yet received any feedback since my earlier follow up.
I have requested that you be provided with feedback as soon as possible.
 
Just a quick question.

I play cs online and we end up playing our clannies generally on jhb servers. My ping to Cape Town servers is around 40 but to jhb servers its around 110. Is that normal?

I really hope it isnt because it would make this pretty much useless to me...
 
Lazy.Me said:
Its seems you guys are waiting an awfully long time to fix something people have been complaining about week after week. It worries me that normal http or https traffic has started struggling on your network.

I must say, the degradation of the Mweb network is becoming more and more apparent, i truly hope you guys address the issues within "within the week"
Click to expand...

Trust me if there were issues that needed to be addressed on our side I would be doing everything possible to make sure this was happening :) We currently have more than ample capacity on our international links and the capacity on our regional IPC links is reviewed and adjusted on a monthly basis in accordance with usage trends and growth forecasts.

We have noted that there are some spikes in utilization at peaks times and we've been monitoring this very closely. We're nowhere near at a level I would call degradation though - just an increase in load which would probably exhibit itself primarily as some reduction in speed on the very low priority protocols during peak times, which is something you should expect on a shaped product.

I have noted the increase in customer complaints with some concern and both myself and MWEB Guy have been following up and investigating these cases where possible. For the most part the issues I'm seeing at the moment are related to customers not having a great experience post line-speed upgrades, rather than anything I can trace back to our own network.
 
Handz said:
Just a quick question.

I play cs online and we end up playing our clannies generally on jhb servers. My ping to Cape Town servers is around 40 but to jhb servers its around 110. Is that normal?

I really hope it isnt because it would make this pretty much useless to me...
Click to expand...

It depends heavily on where the servers are hosted Handz - and your ADSL line of course. Your pings onto any servers hosted on the MWEB network should be really optimal. Cape Town to Cape town on a good line is capable of sub 20ms while pings of 40 odd to our JHB servers would be achievable.

Maybe you can posts some traces to servers you usually play on and we can take a look?
 
Heres a trace to one of the JHB servers we use.

Tracing route to 196.30.66.46 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 10 ms 11 ms 10 ms 41-133-132-1.dsl.mweb.co.za [41.133.132.1]
3 28 ms 28 ms 28 ms te1-1-0.508.cpt-ipc-1.mweb.co.za [196.28.178.190
]
4 29 ms 28 ms 29 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 39 ms 40 ms 39 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178
.98]
6 29 ms 29 ms 29 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 37 ms 36 ms 36 ms mtn-pp.cpt-cinx-2.mweb.co.za [196.28.178.142]
8 31 ms 31 ms 31 ms 196.44.0.75
9 92 ms 96 ms 99 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.25
0]
10 111 ms 114 ms 111 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
11 113 ms 110 ms 107 ms 196.31.220.10
12 109 ms 110 ms 111 ms tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.n
et [196.31.220.23]
13 108 ms 104 ms 101 ms tengigabitethernet5-1.hr10.jnb6.za.mtnbusiness.n
et [196.31.63.154]
14 102 ms 102 ms 105 ms 196.30.66.46

Trace complete.

We playing in DGL tournament online and the majority of those game seem to be played on JHB servers.

Is there anything that can be done?
 
8 31 ms 31 ms 31 ms 196.44.0.75
9 92 ms 96 ms 99 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.25

sorry seems the data is at the mtn data centre, but there cpt to jhb latency seems insane.

to get best pings to mtn , mweb should route the cpt data to jhb on there network , because mtn seems the problems
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X