MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
hereticangel said:
try mweb news server, see if that is going along better, my usenetserver.com use to fly when i had, even recommend it to other people on mweb, but don't have it atm as i dont have download laptop to make it worth while :P
Click to expand...

Tried that, and a friends of mines Giganews account - same issue. NNTP never goes over 60KB/s on Mweb.
 
I'm streaming some video from Justin.TV and it's stuttering on 240p :-( I'm Skype'ing my GF and the quality is so bad. This is very frustrating. Lets hope whatever the problem is gets sorted out ASAP!!!
 
KaMoS said:
I'm streaming some video from Justin.TV and it's stuttering on 240p :-( I'm Skype'ing my GF and the quality is so bad. This is very frustrating. Lets hope whatever the problem is gets sorted out ASAP!!!
Click to expand...

Hi KaMoS,

Is it only Justin.TV and Skype you experiencing issues with? How is your normal browsing? Please provide me with your MWEB account details and I'll investigate further.

Kind regards,

MWEB Guy
 
Hey Mweb Guy. I have tried to collect some information for you about my World of Warcraft issues but they are inconsistent. I seem to be getting packet loss and that is probably the cause of my problems. Can you help me please identify if its my ADSL line (the stats havent really changed, just the downstream noise margin keeps fluctuating a lot between 19-16. It never used to fluctuate so much) or if its Mweb? I know Mweb has been shaping but this problem seems to have only started tuesday this week. Changing to another ISP doesnt alleviate this problem anymore and it leads me to believe it is my line but with no noticeable differences in line stats other than the regular noise fluctuations I am pretty stumped as to the cause.

Just did a tracert thought I should add it:

Tracing route to wow-europe.com [80.239.186.22]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 9 ms 9 ms 8 ms 41-132-12-1.dsl.mweb.co.za [41.132.12.1]
3 9 ms 10 ms 9 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 10 ms 9 ms 9 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 12 ms 21 ms 14 ms TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 14 ms 11 ms 12 ms tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.9
4]
7 231 ms 231 ms 231 ms pos0-0-2-1.lon-up-1.mweb.co.za [196.22.163.234]

8 234 ms 232 ms 233 ms 149.6.98.5
9 378 ms 231 ms 435 ms te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
10 420 ms 424 ms 422 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.
134]
11 * 233 ms 230 ms ldn-b4-link.telia.net [213.248.70.237]
12 268 ms 231 ms 231 ms ldn-bb2-link.telia.net [80.91.250.169]
13 241 ms 240 ms 240 ms prs-bb2-link.telia.net [80.91.247.240]
14 240 ms 238 ms 238 ms prs-b7-link.telia.net [80.91.252.146]
15 239 ms 238 ms 239 ms prs-sdix-i1-link.telia.net [80.91.247.149]
16 * * 80-239-170-114.customer.teliacarrier.com [80.239.170.114]
reports: Destination net unreachable.

Trace complete.


Ping to the HOP I got lost packets:

C:\Users\Zord>ping 213.248.70.237 -t

Pinging 213.248.70.237 with 32 bytes of data:
Reply from 213.248.70.237: bytes=32 time=233ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=238ms TTL=53
Request timed out.
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=265ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=233ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Request timed out.
Reply from 213.248.70.237: bytes=32 time=272ms TTL=53
Reply from 213.248.70.237: bytes=32 time=234ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=230ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53

Ping statistics for 213.248.70.237:
Packets: Sent = 43, Received = 41, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 230ms, Maximum = 272ms, Average = 233ms
 
Last edited:
Zord said:
Hey Mweb Guy. I have tried to collect some information for you about my World of Warcraft issues but they are inconsistent. I seem to be getting packet loss and that is probably the cause of my problems. Can you help me please identify if its my ADSL line (the stats havent really changed, just the downstream noise margin keeps fluctuating a lot between 19-16. It never used to fluctuate so much) or if its Mweb? I know Mweb has been shaping but this problem seems to have only started tuesday this week. Changing to another ISP doesnt alleviate this problem anymore and it leads me to believe it is my line but with no noticeable differences in line stats other than the regular noise fluctuations I am pretty stumped as to the cause.

Just did a tracert thought I should add it:

Tracing route to wow-europe.com [80.239.186.22]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 9 ms 9 ms 8 ms 41-132-12-1.dsl.mweb.co.za [41.132.12.1]
3 9 ms 10 ms 9 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 10 ms 9 ms 9 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 12 ms 21 ms 14 ms TenGigE0-1-0-0.12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 14 ms 11 ms 12 ms tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.9
4]
7 231 ms 231 ms 231 ms pos0-0-2-1.lon-up-1.mweb.co.za [196.22.163.234]

8 234 ms 232 ms 233 ms 149.6.98.5
9 378 ms 231 ms 435 ms te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
10 420 ms 424 ms 422 ms te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.
134]
11 * 233 ms 230 ms ldn-b4-link.telia.net [213.248.70.237]
12 268 ms 231 ms 231 ms ldn-bb2-link.telia.net [80.91.250.169]
13 241 ms 240 ms 240 ms prs-bb2-link.telia.net [80.91.247.240]
14 240 ms 238 ms 238 ms prs-b7-link.telia.net [80.91.252.146]
15 239 ms 238 ms 239 ms prs-sdix-i1-link.telia.net [80.91.247.149]
16 * * 80-239-170-114.customer.teliacarrier.com [80.239.170.114]
reports: Destination net unreachable.

Trace complete.


Ping to the HOP I got lost packets:

C:\Users\Zord>ping 213.248.70.237 -t

Pinging 213.248.70.237 with 32 bytes of data:
Reply from 213.248.70.237: bytes=32 time=233ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=238ms TTL=53
Request timed out.
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=265ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=233ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Request timed out.
Reply from 213.248.70.237: bytes=32 time=272ms TTL=53
Reply from 213.248.70.237: bytes=32 time=234ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=230ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=231ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53
Reply from 213.248.70.237: bytes=32 time=232ms TTL=53

Ping statistics for 213.248.70.237:
Packets: Sent = 43, Received = 41, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 230ms, Maximum = 272ms, Average = 233ms
Click to expand...

Hi Zord,

Thank you for the info. Which account are you using from MWEB and are they both used on the same telephone number?

Kind regards,

MWEB Guy
 
Yes they are. I am using the Mweb Uncapped 4mbit account. I am not getting a stable ping while trying that ping test. The odd spikes in ping and packet loss sound like its my line but I am not sure. The 280ms pings vs the constant 230ms pings are confusing. I am not sure whats causing that either.
 
Last edited:
gdiza said:
news.newsdemon.com is dead.
MWEB please investigate and fix your rules.

europe.newsdemon.com is fine.
Click to expand...

Hi gdiza,

I have refreshed your MWEB account. Please power down your router for 20-30 min and test. Have you perhaps tried with a different account?

Kind regards,

MWEB guy
 
C:\Documents and Settings\MwebIsExtremelySlow>tracert mybroadband.co.za

Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [10.0.0.2]
2 * 11 ms 18 ms 41-132-34-1.dsl.mweb.co.za [41.132.34.1]
3 16 ms 11 ms 20 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 15 ms 10 ms 10 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 29 ms 57 ms * TenGigE0-1-0-0.12.vic-up-2.mweb.co.za [196.22.16
9.242]
6 * 12 ms 11 ms jx2621-1-S1-AP.mweb.net [196.22.163.5]
7 66 ms 60 ms 73 ms static161-134.netactive.co.za [196.22.161.134]
8 54 ms 13 ms 12 ms jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

9 * 13 ms 12 ms 196.44.31.99
10 68 ms 73 ms 80 ms ge4-0-0.gw17.jnb6.za.mtnbusiness.net [196.30.1.3
7]
11 * * 33 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 45 ms 60 ms 96 ms core-router1.jnb2.host-h.net [196.30.213.108]
13 54 ms 39 ms 12 ms 41.72.136.53
14 99 ms 80 ms 74 ms 41.203.21.137

Trace complete.

C:\Documents and Settings\MwebISSlow>tracert mobafire.com

Tracing route to mobafire.com [50.56.52.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.800VGT [10.0.0.2]
2 * 8 ms 8 ms 41-132-34-1.dsl.mweb.co.za [41.132.34.1]
3 56 ms 49 ms 47 ms 41-86-107-18.mweb.co.za [41.86.107.18]
4 * 17 ms 10 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 21 ms 34 ms 51 ms TenGigE0-0-0-0.11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 15 ms 28 ms 29 ms tengige0-3-1-0.mid-up-1.mweb.co.za [196.22.169.2
10]
7 * 237 ms 235 ms pos-1-2-0.lon-up-1.mweb.co.za [196.22.163.230]
8 248 ms 240 ms 245 ms 149.6.98.5
9 257 ms 255 ms 233 ms te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
10 239 ms 257 ms 243 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.3.
225]
11 * 234 ms 233 ms abovenet.lon01.atlas.cogentco.com [130.117.14.21
8]
12 * * 234 ms ge-5-1-0.mpr1.lhr2.uk.above.net [64.125.27.149]

13 * * * Request timed out.
14 327 ms 315 ms 316 ms xe-0-3-0.cr1.dca2.us.above.net [64.125.29.17]
15 * 312 ms * xe-2-2-0.cr1.lga5.us.above.net [64.125.26.98]
16 * * 338 ms xe-3-2-0.cr1.ord2.us.above.net [64.125.24.34]
17 * * 354 ms xe-0-1-0.er1.ord7.us.above.net [64.125.30.141]
18 352 ms 343 ms 335 ms 64.124.65.218.allocated.above.net [64.124.65.218
]
19 * * 352 ms core1-ed1-edge3.ord1.rackspace.net [173.203.0.10
1]
20 385 ms 347 ms 339 ms core1-aggr301a-4.ord1.rackspace.net [184.106.126
.33]
21 334 ms 334 ms 340 ms 50.56.52.19

Trace complete.
Click to expand...

slow
 
DeadCore said:
slow
Click to expand...

Hi DeadCore,

Have you tried refreshing your ADSL connection? How many PC's are active to the router? Please send me your MWEB account details and I'll investigate further.

Kind regards,

MWEB Guy
 


No offence MWEB, but I have got to be honest, the experience I had in the beginning (good) has now turned into one that is rather depressing.

It's bad enough that 384 is slow enough running at max speed....
 
TheYak said:
RIDICULOUSLY slow tonight! Just painful! Time to start looking for another ISP, I think. *sigh*
Click to expand...

Hi TheYak,

Have you tried refreshing your connection. I see your router has dropped connection 4 times already today or have you been rebooting it.

Is it browsing, downloading or email that is slow?

Kind regards,

MWEB Guy
 
copacetic said:


No offence MWEB, but I have got to be honest, the experience I had in the beginning (good) has now turned into one that is rather depressing.

It's bad enough that 384 is slow enough running at max speed....
Click to expand...

Hi copacetic,

Please do a speed test from the following link: http://www.mweb.co.za/helpcentre/MWEBSpeedTest.aspx

Is it browsing, downloading or email that is slow?

Please send me your MWEB account details.

Kind regards,

MWEB guy
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X