MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
I am reaching the end of my patience! For the past week http downloads have been pathetic and unreliable. Downloading new drivers from nvidia: 25~50Kb/s, downloading purchased content from Cornocopia 3D store: 35~70Kb/s, downloading podcasts and app updates from itunes: 35~90Kb/s, tried downloading a torrent: 380~420Kb/s?!?!?!?!
I am on a premium mweb account and have now called to the mweb call centre 3 times. They just this evening made telkom change my line sync speed from 6.3Mbps to 4Mbps to see if that was causing the problem. Well no it wasnt. No change what so ever!! And they just dont seem to know what the issue is. According to the guy I spoke to im the only one who has called about having such a speed issue with http. So I told him to tell the techies to go online on the forums at mybroadband and actually see for themselves how many people are experiencing the same issues......now going on for at least 2 weeks.......and getting worse. My speeds tonight are way worse than ever before.
Someone at Mweb better check whats wrong with their network and/or shaping policy cause its seriously broken!!
 
@Zord Our engineers are currently relooking at every aspect of these configurations to see if they can make any improvements, or establish any cause for the symptoms being described, but it is a very complex environment and every bit of data that we can gather in terms of the customer experience can only help them in this cause.

So please instead of turning on the flamethrower send MWEB Guy some detailed stats illustrating the problem you're expriencing and if you're saying that things work better with a different isp account, please make sure that the testing is consistent and give some detail as to when and how you tested and what the results where.
 
http://imageshack.us/photo/my-images/706/hehtr.png/

(apologies to all mweb users for the large size on that image, it should be done in about 25-30mins)

And yeah im going to be bashing and raging until this is fixed pretty much,

Firstly, because i cant do anything else.
And Second, because its cold outside and theres never anything on TV.
 
avert said:
http://imageshack.us/photo/my-images/706/hehtr.png/

(apologies to all mweb users for the large size on that image, it should be done in about 25-30mins)

And yeah im going to be bashing and raging until this is fixed pretty much,

Firstly, because i cant do anything else.
And Second, because its cold outside and theres never anything on TV.
Click to expand...


Opening the link and going to the shop, hopefully it will be loaded when i get back at 9:15
 
Even pings to google.co.za times out every now and then. Will, this is to give more info so your engineers can fix this.

Pinging google.co.za [74.125.233.19] with 32 bytes of data:

Reply from 74.125.233.19: bytes=32 time=100ms TTL=56
Reply from 74.125.233.19: bytes=32 time=63ms TTL=56
Reply from 74.125.233.19: bytes=32 time=95ms TTL=56
Reply from 74.125.233.19: bytes=32 time=67ms TTL=56
Reply from 74.125.233.19: bytes=32 time=175ms TTL=56
Reply from 74.125.233.19: bytes=32 time=234ms TTL=56
Reply from 74.125.233.19: bytes=32 time=226ms TTL=56
Reply from 74.125.233.19: bytes=32 time=71ms TTL=56
Reply from 74.125.233.19: bytes=32 time=137ms TTL=56
Reply from 74.125.233.19: bytes=32 time=177ms TTL=56
Reply from 74.125.233.19: bytes=32 time=101ms TTL=56
Reply from 74.125.233.19: bytes=32 time=67ms TTL=56
Request timed out.
Reply from 74.125.233.19: bytes=32 time=78ms TTL=56
Reply from 74.125.233.19: bytes=32 time=146ms TTL=56
Reply from 74.125.233.19: bytes=32 time=33ms TTL=56
Reply from 74.125.233.19: bytes=32 time=50ms TTL=56
Reply from 74.125.233.19: bytes=32 time=181ms TTL=56
Reply from 74.125.233.19: bytes=32 time=231ms TTL=56
Reply from 74.125.233.19: bytes=32 time=141ms TTL=56
Reply from 74.125.233.19: bytes=32 time=172ms TTL=56
Reply from 74.125.233.19: bytes=32 time=278ms TTL=56
Request timed out.
Reply from 74.125.233.19: bytes=32 time=117ms TTL=56
Reply from 74.125.233.19: bytes=32 time=13ms TTL=56
Reply from 74.125.233.19: bytes=32 time=106ms TTL=56
Reply from 74.125.233.19: bytes=32 time=41ms TTL=56
Reply from 74.125.233.19: bytes=32 time=76ms TTL=56
Request timed out.
Reply from 74.125.233.19: bytes=32 time=186ms TTL=56
Reply from 74.125.233.19: bytes=32 time=142ms TTL=56
Reply from 74.125.233.19: bytes=32 time=75ms TTL=56
Reply from 74.125.233.19: bytes=32 time=54ms TTL=56
Reply from 74.125.233.19: bytes=32 time=62ms TTL=56
Reply from 74.125.233.19: bytes=32 time=98ms TTL=56
Reply from 74.125.233.19: bytes=32 time=124ms TTL=56
Reply from 74.125.233.19: bytes=32 time=101ms TTL=56
Reply from 74.125.233.19: bytes=32 time=167ms TTL=56
Reply from 74.125.233.19: bytes=32 time=13ms TTL=56
Reply from 74.125.233.19: bytes=32 time=193ms TTL=56
Reply from 74.125.233.19: bytes=32 time=12ms TTL=56
Reply from 74.125.233.19: bytes=32 time=184ms TTL=56
Reply from 74.125.233.19: bytes=32 time=12ms TTL=56
Reply from 74.125.233.19: bytes=32 time=167ms TTL=56
Reply from 74.125.233.19: bytes=32 time=12ms TTL=56
Reply from 74.125.233.19: bytes=32 time=13ms TTL=56
Reply from 74.125.233.19: bytes=32 time=13ms TTL=56
Reply from 74.125.233.19: bytes=32 time=95ms TTL=56
Reply from 74.125.233.19: bytes=32 time=104ms TTL=56
Reply from 74.125.233.19: bytes=32 time=112ms TTL=56
Reply from 74.125.233.19: bytes=32 time=140ms TTL=56
Reply from 74.125.233.19: bytes=32 time=39ms TTL=56
Reply from 74.125.233.19: bytes=32 time=16ms TTL=56
Reply from 74.125.233.19: bytes=32 time=169ms TTL=56
Reply from 74.125.233.19: bytes=32 time=108ms TTL=56
Request timed out.
Reply from 74.125.233.19: bytes=32 time=147ms TTL=56
Reply from 74.125.233.19: bytes=32 time=210ms TTL=56
Reply from 74.125.233.19: bytes=32 time=210ms TTL=56
Reply from 74.125.233.19: bytes=32 time=275ms TTL=56

Ping statistics for 74.125.233.19:
Packets: Sent = 60, Received = 56, Lost = 4 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 278ms, Average = 114ms
 
no missed pings here ABCpt on my mweb and afrihost, maybe do a tracert and try a constant ping to the first ip outside your router to help narrow down if it might be line related
 
1.Some torrents loading at 100 kB/s .
2.Cant stream a 3min you tube clip with out buffering for 10 mins.
3.Http is real slow.
4.Tried http and you tube after disconnecting torrents.

conclusion:The guys that do MWebs shaping have broken my internet.:cry:
 
vaalpens said:
no missed pings here ABCpt on my mweb and afrihost, maybe do a tracert and try a constant ping to the first ip outside your router to help narrow down if it might be line related
Click to expand...

Tracert not working for some strange reason. Will try and figire it out and post again later. Still, downloads improve after midnight. Haven't tried my afrihost account recently.
 
vaalpens said:
no missed pings here ABCpt on my mweb and afrihost, maybe do a tracert and try a constant ping to the first ip outside your router to help narrow down if it might be line related
Click to expand...

Thanks vaalpens I would also say this looks more line, or congestion related. ABCpt please provide MWEB Guy with your line details and he will check line conditions and log a request with Telkom to check exchange conditions as well.

This really serves to illustrate why I prefer to follow the correct troubleshooting process. If we assume that everyones symptoms are part of the same problem we not only end up with an incorrect set of symptoms, but we also waste valuable time in giving attention to unrelated complaints that could have been addressed through the normal processes.

EDIT: These are comparitive results for pinging google.co.za (also from CPT)

Reply from 74.125.233.17: bytes=32 time=10ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=10ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=18ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=50ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=14ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=8ms TTL=56
Reply from 74.125.233.17: bytes=32 time=9ms TTL=56
Reply from 74.125.233.17: bytes=32 time=10ms TTL=56
Reply from 74.125.233.17: bytes=32 time=10ms TTL=56

Ping statistics for 74.125.233.17:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 57ms, Average = 10ms
 
Last edited:
hmm Will

why not create form or something, ill even help set it up / type it out, where everyone can post their current line sync speed, Area and dialing code, pings and tracerts to a set of IP's and some speed tests / http downloads from different sources, both on Mweb and another ISP etc etc etc?
this might speed up the process of pinpointing the issue
 
Will@MWEB said:
I can assure you that Rudi is well aware of the complaints currently being expressed here and he is as concerned as I am.
Regardless of how much you may be in the mood to bash someone or flame at the moment the fact is that basic troubleshooting principles remain unchanged, which is something that should be very understandable in a Tech savvy community such as this one.

I'm not saying that all of you have line faults, or are suffering from Telkom problems, but if you don't allow my team to follow the basic principles of fault elimination and replication then I cannot establish any underlying trend, or reason for your problems, which in turn means when I go to our network engineers and tell them 'something is broken' that I will not have any of the supporting evidence I require to substantiate my claim, or provide them with a starting point for any meaningful investigation.
Click to expand...

Regards to what you are saying, this has been proven that it is a MWEB issue with my problem at hand. Still nothing from MWEB. My reference number is 598186
 
vaalpens said:
hmm Will

why not create form or something, ill even help set it up / type it out, where everyone can post their current line sync speed, Area and dialing code, pings and tracerts to a set of IP's and some speed tests / http downloads from different sources, both on Mweb and another ISP etc etc etc?
this might speed up the process of pinpointing the issue
Click to expand...

Now that's a great suggestion :) I'll throw something together first thing tomorrow morning and get it up here.
 
MWeb guy has my details and permission to monitor my network traffic. Will check again tomorrow with my Afrihost account and provide feedback.
 
ok, the 2 vm's are finished and ready for testing, one on afrihost and the other on mweb (the mweb one took a few minutes longer to set up and download stuff...)
 
mweb
Tracing route to google.co.za [74.125.230.116]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 21 ms 135 ms 39 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 21 ms 18 ms 20 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 115 ms 107 ms 99 ms TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.169.241]
6 83 ms * 27 ms tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.94]
7 261 ms 251 ms * pos-1-2-0.lon-up-1.mweb.co.za [196.22.163.230]
8 261 ms * 261 ms 195.66.224.125
9 * 321 ms 249 ms 64.233.175.27
10 277 ms 263 ms 283 ms 209.85.251.62
11 350 ms 247 ms 252 ms 74.125.230.116

Trace complete.


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

1 24 ms 24 ms 19 ms 196-210-149-129.dynamic.isadsl.co.za [196.210.149.129]
2 35 ms 38 ms 37 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
3 * 37 ms 37 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
4 23 ms 21 ms 19 ms core1b-rba-te2-0-1.ip.isnet.net [168.209.1.181]
5 248 ms 254 ms 259 ms 168.209.201.41
6 250 ms 269 ms 249 ms 168.209.246.66
7 272 ms 255 ms 255 ms 195.66.226.125
8 264 ms 253 ms 268 ms 209.85.252.76
9 264 ms 262 ms 256 ms 72.14.232.134
10 275 ms * 253 ms 216.239.49.45
11 278 ms 277 ms 259 ms 209.85.243.81
12 * * 255 ms ww-in-f99.1e100.net [209.85.229.99]

Trace complete.


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

1 * * * Request timed out.
2 36 ms 32 ms 31 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.43.11.134]
3 27 ms 24 ms 20 ms 196.43.26.106
4 34 ms 31 ms 36 ms 165.165.38.147

Trace complete.

hope this is of use.
 
slow the entire day, even my DAD noticed (and the most he does online is browse gumtree or plays farmville on my sister's facebook account)

Pinging google.co.za [74.125.233.18] with 32 bytes of data:
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Request timed out.
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Request timed out.
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.233.18: bytes=32 time=164ms TTL=56
Reply from 74.125.233.18: bytes=32 time=14ms TTL=56
Reply from 74.125.233.18: bytes=32 time=27ms TTL=56
Reply from 74.125.233.18: bytes=32 time=14ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Request timed out.
Reply from 74.125.233.18: bytes=32 time=11ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=98ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=342ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=36ms TTL=56
Reply from 74.125.233.18: bytes=32 time=15ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=27ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=11ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=21ms TTL=56
Request timed out.
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=14ms TTL=56
Reply from 74.125.233.18: bytes=32 time=11ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=15ms TTL=56
Reply from 74.125.233.18: bytes=32 time=51ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=47ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=15ms TTL=56
Reply from 74.125.233.18: bytes=32 time=19ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=36ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=14ms TTL=56
Reply from 74.125.233.18: bytes=32 time=20ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=16ms TTL=56
Reply from 74.125.233.18: bytes=32 time=14ms TTL=56
Reply from 74.125.233.18: bytes=32 time=13ms TTL=56
Reply from 74.125.233.18: bytes=32 time=17ms TTL=56
Request timed out.
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=131ms TTL=56
Reply from 74.125.233.18: bytes=32 time=12ms TTL=56
Reply from 74.125.233.18: bytes=32 time=15ms TTL=56

Ping statistics for 74.125.233.18:
Packets: Sent = 70, Received = 61, Lost = 9 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 342ms, Average = 26ms
Click to expand...

Pathetic
 
Downloading a file from HP.com using HTTP , running at 21 Kb/s on a 4 Mbps line.

Also did a ping to www.google.co.za and while I am not losing any packet the response times are slow

Ping statistics for 74.125.230.114:
Packets: Sent = 161, Received = 161, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 234ms, Maximum = 252ms, Average = 236ms

Just tested World of Tanks now, ping is 330ms.
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X