MWeb uncapped worse than Afrihost

E

epeer

Active Member
Joined
Oct 2, 2009
Messages
67
Reaction score
0
Switched to MWeb this month because Afrihost was sucking...

4MBit line...





Have consistently seen this kind of performance the whole month. On the odd occasion it works well, but on the whole - useless. Can't even stream small Youtube videos most of the time.

At this rate, I was better off with Afrihost.

Pathetic.
 
you must have fail somewhere, i suppose you gave them a call.

yesterday i updated and downloaded the spellborn chronicles without issues around max line speed.
last night to this morning i got the darkfall torrent also around max line speed (add pic later today).
this morning darkfall udpated also around max line speed.
 
Sorry but these days everyone who posts anti Mweb posts with so few posts just sounds to me like they have some vested interest in bad mouthing them.
Sorry if that offends, just my humble opinion.
 
Mweb is by far the best uncapped service on the market (In its price range ofcourse)!
 
epeer said:
Switched to MWeb this month because Afrihost was sucking...

4MBit line...





Have consistently seen this kind of performance the whole month. On the odd occasion it works well, but on the whole - useless. Can't even stream small Youtube videos most of the time.

At this rate, I was better off with Afrihost.

Pathetic.
Click to expand...


Hi epeer


I would like to apologize for the inconvenience
Please PM me your details and I will have a specialist look into this for you.


Regards
MWEB Operations
 
marine1 said:
Sorry but these days everyone who posts anti Mweb posts with so few posts just sounds to me like they have some vested interest in bad mouthing them.
Sorry if that offends, just my humble opinion.
Click to expand...

What does having only few posts have to do with anything? I complained about Afrihost just as much, so obviously no vested interest in bad mouthing MWeb in particular. If you bothered to even read my other posts you'd know that (there are so few of them, after all).

Fact is, it is not working properly for everyone. Speed test above _proves_ it.

My small amount of posts has more to do with the fact that I don't tend write anything until it has been really bad for quite some time. Because, I know these kind of issues usually resolve themselves in time.
 
Epeer PM MWEB Operations and let him assist you

The issue you are experiencing is clearly not system wide since most people haven’t been experiencing it.

So let the MWEB guys assist you and get it working the way it is suppose to work.

In that way you will be happy with the service they offer

here is a speed test that I just did
a couple of people is also using this line to browse
 
Last edited:
1 server in Pretoria, the other in WASHINGTON DC, am i missing something
 
Mweb is rubbish for day downloading.... works well at night (morning?) and weekends tho,
pulled 230gb thus far in the 2.5 weeks that iv been with them so its definitely not worse than afrihosts "large cap" account.
 
marine1 said:
Sorry man just don't know why people don't try their support and if they do, post it in their op
Click to expand...

Agreed, there is no point creating 101 complaint threads. When I have any issues I call MWEB directly, they have always been very professional and helpful.
 
...fast, though any other speed with that connected seeds would be funny ;) :D (last night till this morning)
fasttorrent2.jpg
 
Fader4 said:
Mweb is rubbish for day downloading.... works well at night (morning?) and weekends tho
Click to expand...

No good for me, I do most of my Internet work during office hours.

Spoke with the MWeb guys today about the issue. I must say, I did appreciate that they are able to engage with their clients on a more technical level (beyond just having monkeys logging tickets behind the help desk). That said, they were still clueless as to what the cause of the problem might be. They've "reset" my account, but performance is still poor to US based sites (UK sites seem okay today). I really don't understand how a bottleneck to the US can only be affecting me?

The problem seems to persist into the evening too:





I've sent MWeb some diagnostic info they asked for. They are investigating the problem...
 
epeer said:
No good for me, I do most of my Internet work during office hours.

Spoke with the MWeb guys today about the issue. I must say, I did appreciate that they are able to engage with their clients on a more technical level (beyond just having monkeys logging tickets behind the help desk). That said, they were still clueless as to what the cause of the problem might be. They've "reset" my account, but performance is still poor to US based sites (UK sites seem okay today). I really don't understand how a bottleneck to the US can only be affecting me?

The problem seems to persist into the evening too:





I've sent MWeb some diagnostic info they asked for. They are investigating the problem...
Click to expand...

Had same problem, canceled - moved to another ISP with good uncapped speeds... (One of my MWEB accounts in Waterfront CTN flies, another account in Tamboerskloof CTN slower than dial up both in the same Telkom exchange Leeusig 8)
 
epeer lets do a traceRT/ping so we can compare. [curious epeer are you in CT?]

tracert
1) www.google.com

Tracing route to www.l.google.com [64.233.179.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 * * * Request timed out.
3 11 ms 11 ms 11 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.16
9.134]
4 11 ms 11 ms 10 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 64 ms 63 ms 47 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 14 ms 14 ms 16 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]

7 269 ms 268 ms 270 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
8 285 ms 288 ms 290 ms 195.66.224.125
9 268 ms 267 ms 268 ms 64.233.175.25
10 412 ms 275 ms 275 ms 72.14.232.95
11 424 ms 424 ms 424 ms 64.233.174.41
12 423 ms 439 ms 423 ms 64.233.174.105
13 424 ms 423 ms 423 ms www.l.google.com [64.233.179.104]

Trace complete.
Click to expand...

2) some random usa ip 68.181.194.65

Tracing route to v249-gw-6.usc.edu [68.181.194.65]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [10.10.10.1]
2 * * * Request timed out.
3 10 ms 11 ms 10 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 11 ms 11 ms 10 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 18 ms 14 ms 15 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
6 13 ms 15 ms 15 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]

7 251 ms 251 ms 251 ms PO9-0.lon-001-access-1.interoute.net [89.202.130
.181]
8 289 ms 279 ms 268 ms xe-1-3-0-0.lon-001-score-1-re0.interoute.net [84
.233.218.178]
9 267 ms 282 ms 267 ms ae1-0.ams-koo-score-1-re0.interoute.net [84.233.
190.57]
10 290 ms 267 ms 274 ms ae0-0.ams-koo-score-2-re0.interoute.net [84.233.
190.2]
11 267 ms 268 ms 266 ms ae1-0.fra-006-score-1-re0.interoute.net [84.233.
190.50]
12 266 ms 266 ms 268 ms ae0-0.fra-006-score-3-re0.interoute.net [212.23.
42.166]
13 279 ms 450 ms 447 ms ge-1-6.r01.frnkge03.de.bb.gin.ntt.net [213.198.7
2.189]
14 265 ms 265 ms 265 ms ae-2.r21.frnkge04.de.bb.gin.ntt.net [129.250.5.2
17]
15 271 ms 271 ms 270 ms as-1.r23.amstnl02.nl.bb.gin.ntt.net [129.250.3.6
2]
16 355 ms 355 ms 405 ms as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.1
58]
17 350 ms 350 ms 350 ms ae-3.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.1
29]
18 433 ms 424 ms 424 ms as-2.r21.lsanca03.us.bb.gin.ntt.net [129.250.5.2
4]
19 424 ms 427 ms 421 ms po-2.r00.lsanca03.us.bb.gin.ntt.net [129.250.5.2
50]
20 430 ms 422 ms 424 ms 198.172.117.163
21 435 ms 437 ms 436 ms ln-usc3-tus2015.ln.net [130.152.181.145]
22 436 ms 431 ms 436 ms v249-gw-6.usc.edu [68.181.194.65]

Trace complete.
Click to expand...

pings

1) www.google.com
Pinging www.l.google.com [64.233.179.104] with 32 bytes of data:
Reply from 64.233.179.104: bytes=32 time=423ms TTL=51
Reply from 64.233.179.104: bytes=32 time=424ms TTL=51
Reply from 64.233.179.104: bytes=32 time=423ms TTL=51
Reply from 64.233.179.104: bytes=32 time=423ms TTL=51

Ping statistics for 64.233.179.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 423ms, Maximum = 424ms, Average = 423ms
Click to expand...

2) usa ip 68.181.194.65
Pinging 68.181.194.65 with 32 bytes of data:
Reply from 68.181.194.65: bytes=32 time=437ms TTL=237
Reply from 68.181.194.65: bytes=32 time=436ms TTL=237
Reply from 68.181.194.65: bytes=32 time=422ms TTL=237
Reply from 68.181.194.65: bytes=32 time=439ms TTL=237

Ping statistics for 68.181.194.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 422ms, Maximum = 439ms, Average = 433ms
Click to expand...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X