MWEB Uncapped ADSL Feedback - Part 2

Status
Not open for further replies.
Dead here in Durban,im really considering a switch now as i game online a lot and its becoming frustrating especially as tomorrow is blue monday,we wanna play games instead of timing out all the time :P. wont even bother calling mweb as last week when i did,i waited so long,i just quit the call.not informative when it comes to these problems as well. :(
 
I switched to my backup account.

Once mweb international is back up for 10 minutes solid please tell me so I can switch back.
 
They must have some problem somewhere. I can game but my downloads dropped from 100% speed to under 40kbps and i am on a 4Meg account :/
 
They must have some problem somewhere. I can game but my downloads dropped from 100% speed to under 40kbps and i am on a 4Meg account :/

I had exact same problem. Gaming was impossible with consistant timeouts, browsing was crawling.
 
Well, Mweb is having very high packet loss today, 50-60% so the internet seems dead to me........ :cry:

Good MOrning Hummercellc, please provide me the pings to mweb.co.za and bbc.co.uk reflecting the packet loss.
 
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 10.0.0.2
2 3 ms 2 ms 2 ms 41-134-XXX-XXX.dsl.mweb.co.za [41.134.XXX.XXX]
3 41 ms 39 ms 44 ms 197-81-146-2.jhb.mweb.co.za [197.81.146.2]
4 45 ms 44 ms 46 ms 197-81-146-3.jhb.mweb.co.za [197.81.146.3]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:

1 2 ms 1 ms <1 ms 10.0.0.2
2 5 ms 2 ms 2 ms 41-134-XXX-XXX.dsl.mweb.co.za [41.134.XXX.XXX]
3 44 ms 44 ms 45 ms 197-81-146-2.jhb.mweb.co.za [197.81.146.2]
4 64 ms 56 ms 44 ms 197-81-146-4.jhb.mweb.co.za [197.81.146.4]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.


This is why I have cancelled all my accounts, without fail every week randomly I get this, I have been testing a Afrihost account along side the Mweb account and the Afrihost account never has this problem. Ever since the problem of 4meg accounts being limited to 1meg story Mweb has been a big ball off SH*T!
 
Last edited:
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 10.0.0.2
2 3 ms 2 ms 2 ms 41-134-XXX-XXX.dsl.mweb.co.za [41.134.XXX.XXX]
3 41 ms 39 ms 44 ms 197-81-146-2.jhb.mweb.co.za [197.81.146.2]
4 45 ms 44 ms 46 ms 197-81-146-3.jhb.mweb.co.za [197.81.146.3]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:

1 2 ms 1 ms <1 ms 10.0.0.2
2 5 ms 2 ms 2 ms 41-134-XXX-XXX.dsl.mweb.co.za [41.134.XXX.XXX]
3 44 ms 44 ms 45 ms 197-81-146-2.jhb.mweb.co.za [197.81.146.2]
4 64 ms 56 ms 44 ms 197-81-146-4.jhb.mweb.co.za [197.81.146.4]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.


This is why I have cancelled all my accounts, without fail every week randomly I get this, I have been testing a Afrihost account along side the Mweb account and the Afrihost account never has this problem. Ever since the problem of 4meg accounts being limited to 1meg story Mweb has been a big ball off SH*T!

Thanks for the information, can you please provide me pings to mweb and bbc as well.
 
This is why I have cancelled all my accounts, without fail every week randomly I get this, I have been testing a Afrihost account along side the Mweb account and the Afrihost account never has this problem. Ever since the problem of 4meg accounts being limited to 1meg story Mweb has been a big ball off SH*T!

Say what?????? :cry:
 
I had exact same problem. Gaming was impossible with consistant timeouts, browsing was crawling.

It was the same for me yesterday aswell, couldn't play for 30 min without dropping. Thought it was a Telkom issue initially but when I switched to my FNB account all was fine...
 
Say what?????? :cry:

In January this year, all 4meg accounts shaped & unshaped were being rate limited to 1meg.
No matter what you did you could not get 4meg on a 4meg account. Switching ISP's showed this was a Mweb problem, as many were affected it took 3 weeks for Mweb to sort this out, and ever since that time Mweb have been -1 for me.

Without fail almost everyday at random times there are latency spikes, followed by insane packet loss. Then all of a sudden everything is back to normal.

I have tested with a IS, MTN & TelkomSA accounts, and I do not have this problem. Only with Mweb?

I have decided to move to Afrihost, as Mweb Business support is shocking! and no one there can read.

I was told I may not cancel my account as I am in a contract, so I ask for proof that I had signed a contract.

I got emailed a form of some random person, when I pointed out I was not the person on the form only then did the penny drop at Mweb Business that they were looking at the wrong account.

So this is where I draw the line, stupid work at Mweb, who can not read or even get a account number right.

I have grown very tired of providing trace routes and pings and speedtests and this and that......

Mweb need to fix their network if they wish to retain clients, oh and employ people who can read!
 
In January this year, all 4meg accounts shaped & unshaped were being rate limited to 1meg.
No matter what you did you could not get 4meg on a 4meg account. Switching ISP's showed this was a Mweb problem, as many were affected it took 3 weeks for Mweb to sort this out, and ever since that time Mweb have been -1 for me.

Without fail almost everyday at random times there are latency spikes, followed by insane packet loss. Then all of a sudden everything is back to normal.

I have tested with a IS, MTN & TelkomSA accounts, and I do not have this problem. Only with Mweb?

I have decided to move to Afrihost, as Mweb Business support is shocking! and no one there can read.

I was told I may not cancel my account as I am in a contract, so I ask for proof that I had signed a contract.

I got emailed a form of some random person, when I pointed out I was not the person on the form only then did the penny drop at Mweb Business that they were looking at the wrong account.

So this is where I draw the line, stupid work at Mweb, who can not read or even get a account number right.

I have grown very tired of providing trace routes and pings and speedtests and this and that......

Mweb need to fix their network if they wish to retain clients, oh and employ people who can read!

I can see you are really infuriated by the entire situation.

I requested the pings in order for me to provide this to our network team for further investigation.
 
Hi, I'm in Centurion:

Some trace routes to bbc.co.uk and cnbc.com. It seems it's never normal anymore. MWEB's network needs fixing.

MWEB Guy, I know it's not your fault, but I think you need to stress to your management that the network is seriously malfunctioning and that it puts the future of MWEB in jeopardy.

tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 11 ms 16 ms 10 ms 197-80-132-118.jhb.mweb.co.za [197.80.132.118]
4 12 ms 12 ms 27 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 198 ms 197 ms 198 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 194 ms 195 ms 195 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 192 ms 194 ms 190 ms 176.67.177.131
8 * * * Request timed out.
9 190 ms 191 ms 190 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.142]
10 * * * Request timed out.
11 191 ms 191 ms 190 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 193 ms 192 ms 192 ms 132.185.255.140
13 191 ms 191 ms 191 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.

Tracing route to cnbc.com [207.223.6.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 11 ms 12 ms 11 ms 197-80-132-118.jhb.mweb.co.za [197.80.132.118]
4 11 ms 12 ms 11 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 197 ms 205 ms 192 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 195 ms 194 ms 197 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 193 ms 193 ms 191 ms 176.67.177.131
8 * * * Request timed out.
9 190 ms 190 ms 191 ms globalcrossing-ic-135890-ldn-b5.c.telia.net [213
.248.81.74]
10 266 ms 264 ms 264 ms 67.17.193.18
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.
 
Hi, I'm in Centurion:

Some trace routes to bbc.co.uk and cnbc.com. It seems it's never normal anymore. MWEB's network needs fixing.

MWEB Guy, I know it's not your fault, but I think you need to stress to your management that the network is seriously malfunctioning and that it puts the future of MWEB in jeopardy.

tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 11 ms 16 ms 10 ms 197-80-132-118.jhb.mweb.co.za [197.80.132.118]
4 12 ms 12 ms 27 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 198 ms 197 ms 198 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.242]
6 194 ms 195 ms 195 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 192 ms 194 ms 190 ms 176.67.177.131
8 * * * Request timed out.
9 190 ms 191 ms 190 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.142]
10 * * * Request timed out.
11 191 ms 191 ms 190 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 193 ms 192 ms 192 ms 132.185.255.140
13 191 ms 191 ms 191 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.

Tracing route to cnbc.com [207.223.6.19]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 11 ms 12 ms 11 ms 197-80-132-118.jhb.mweb.co.za [197.80.132.118]
4 11 ms 12 ms 11 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 197 ms 205 ms 192 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.226]
6 195 ms 194 ms 197 ms pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
7 193 ms 193 ms 191 ms 176.67.177.131
8 * * * Request timed out.
9 190 ms 190 ms 191 ms globalcrossing-ic-135890-ldn-b5.c.telia.net [213
.248.81.74]
10 266 ms 264 ms 264 ms 67.17.193.18
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.

Good Day Future_Trader, your trace results seem normal.

Both traces completes.
 
Hi MWEB Guy,

Apologies, I'm not really to clued up on networks, but I thought the high number of time-outs is problematic.

Here's a ping to cnbc.com:

ping cnbc.com

Pinging cnbc.com [207.223.6.20] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.223.6.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

The website does load, but slowly and often does not complete.

My Main issue with MWEB is frequent slow international browsing and frequent interruptions in international connectivity.
 
Hi MWEB Guy,

Apologies, I'm not really to clued up on networks, but I thought the high number of time-outs is problematic.

Here's a ping to cnbc.com:

ping cnbc.com

Pinging cnbc.com [207.223.6.20] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.223.6.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

The website does load, but slowly and often does not complete.

My Main issue with MWEB is frequent slow international browsing and frequent interruptions in international connectivity.

Thanks for the feedback, please provide me pings to bbc.co.uk s well.
 
Hi MWEB Guy,

Apologies, I'm not really to clued up on networks, but I thought the high number of time-outs is problematic.

Here's a ping to cnbc.com:

ping cnbc.com

Pinging cnbc.com [207.223.6.20] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.223.6.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

The website does load, but slowly and often does not complete.

My Main issue with MWEB is frequent slow international browsing and frequent interruptions in international connectivity.
I'm using a different ISP, but my ping results are the same.
I also did a traceroute and from hop 16 everything timed out.
The page did open quickly for me though.
 
BBC looks normal. At the moment most international sites look normal, but the problem of slow international bandwidth (HTTP and HTTPS) comes and goes during the day. When it is slow, I see huge packet loss.

Downloads (non peer-to-peer) are sometimes good, sometimes not, it's intermittent. I'm not a sophisticated user so I can't tell about the rest.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X