MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Pr⊕phet said:
seriously, you telling me that if i have a problem with a product, but it's already been noted as faulty in the public domain and the company in question knows i have a problem, i still have to go and make posts and threads about it ?

seriously don't understand your logic. mweb has noted there is a fault, mweb has said they will fix it and yet you need to get everyone in to post they have a problem because of that problem ? unproductive ?
Click to expand...

No there is ALWAYS a problem, that is what people are complaining about! Once in a while is fine but all the time? I am sorry but I can't simply accept it anymore!
 
Linoman said:
No there is ALWAYS a problem, that is what people are complaining about! Once in a while is fine but all the time? I am sorry but I can't simply accept it anymore!
Click to expand...

so let me think for you : try another isp, ok ?

share with me the ip to your american host so i can tracert as well :)
 
208.97.187.204


traceroute to 208.97.187.204 (208.97.187.204), 64 hops max, 52 byte packets
1 login.router (10.0.0.2) 5.399 ms 1.732 ms 1.507 ms
2 41-133-108-1.dsl.mweb.co.za (41.133.108.1) 10.789 ms 10.803 ms 11.162 ms
3 te1-1-0.502.cpt-ipc-1.mweb.co.za (196.28.178.166) 12.282 ms 11.484 ms 12.067 ms
4 vlan92.cpt-hscore-1.mweb.co.za (196.28.179.11) 12.100 ms 12.731 ms 12.816 ms
5 tengige0-2-0-0.11.cpt-up-1.mweb.co.za (196.28.178.97) 15.123 ms 13.133 ms 15.074 ms
6 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 163.859 ms 166.837 ms 166.627 ms
7 * *
 
pos0-0-3-0.lon-up-1.mweb.co.za seems to be one borked hop :

Tracing route to dreamhost.com [208.97.187.204]
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 58 ms 11 ms 11 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 14 ms 12 ms 14 ms TenGigE0-0-0-0.11.vic-up-2.mweb.co.za [196.22.16
9.226]
6 12 ms 13 ms 15 ms TenGigE0-1-0-0.42.vic-up-1.mweb.co.za [196.22.16
9.217]
7 237 ms 236 ms 236 ms pos0-0-2-1.lon-up-1.mweb.co.za [196.22.163.234]

8 * * * Request timed out.
9 236 ms 235 ms 236 ms te3-4.ccr02.lon02.atlas.cogentco.com [154.54.36.
169]
10 313 ms 313 ms 313 ms te0-5-0-1.ccr22.jfk02.atlas.cogentco.com [154.54
.30.134]
11 317 ms 317 ms 317 ms te0-3-0-6.ccr22.dca01.atlas.cogentco.com [154.54
.41.13]
12 332 ms 329 ms 330 ms te8-1.ccr02.atl01.atlas.cogentco.com [154.54.1.1
21]
13 346 ms 346 ms 347 ms te0-0-0-6.ccr22.iah01.atlas.cogentco.com [154.54
.24.22]
14 380 ms 380 ms 380 ms te0-0-0-5.ccr22.lax01.atlas.cogentco.com [154.54
.5.194]
15 379 ms 380 ms 380 ms te4-8.ccr02.lax04.atlas.cogentco.com [154.54.6.2
42]
16 382 ms 382 ms 382 ms audio-visual-services-group-inc.demarc.cogentco.
com [38.104.82.234]
17 385 ms 383 ms 382 ms border11.po2-20g-bbnet1.lax.pnap.net [216.52.255
.104]
18 * newdream-9.border11.lax.pnap.net [216.52.220.146] reports: Destin
ation net unreachable.

Trace complete.
Click to expand...
 
however even WA fails... OMG it's not just mweb !!! we are all going to ****ing die !!! lol ?

Tracing route to dreamhost.com [208.97.187.204]
over a maximum of 30 hops:

1 * * * Request timed out.
2 34 ms 32 ms 33 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
3 35 ms 34 ms 34 ms vl31.er.gw.cpt.za.wa.co.za [41.185.0.153]
4 33 ms 33 ms 33 ms 41.66.150.177
5 185 ms 185 ms 186 ms 41.66.132.49
6 * * * Request timed out.
7 * * * Request timed out.
8 266 ms 265 ms 265 ms te0-3-0-4.ccr22.bos01.atlas.cogentco.com [154.54
.5.122]
9 265 ms 264 ms 265 ms te0-0-0-3.ccr21.jfk02.atlas.cogentco.com [154.54
.44.37]
10 270 ms 270 ms 270 ms te0-3-0-6.ccr21.dca01.atlas.cogentco.com [154.54
.41.5]
11 372 ms 368 ms 373 ms te1-7.ccr01.atl01.atlas.cogentco.com [154.54.42.
190]
12 314 ms 308 ms 310 ms te0-2-0-1.ccr21.iah01.atlas.cogentco.com [154.54
.29.6]
13 333 ms 332 ms 332 ms te0-1-0-6.ccr21.lax01.atlas.cogentco.com [154.54
.0.225]
14 334 ms 334 ms 334 ms te4-4.ccr02.lax04.atlas.cogentco.com [154.54.1.1
0]
15 334 ms 334 ms 333 ms audio-visual-services-group-inc.demarc.cogentco.
com [38.104.82.234]
16 360 ms 422 ms 415 ms border11.po1-20g-bbnet1.lax.pnap.net [216.52.255
.40]
17 newdream-9.border11.lax.pnap.net [216.52.220.146] reports: Destination net
unreachable.

Trace complete.


C:\>ping 208.97.187.204

Pinging 208.97.187.204 with 32 bytes of data:
Reply from 216.52.220.146: Destination net unreachable.
Reply from 216.52.220.146: Destination net unreachable.
Reply from 216.52.220.146: Destination net unreachable.
Reply from 216.52.220.146: Destination net unreachable.

Ping statistics for 208.97.187.204:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Click to expand...
 
here's a trace i did earlier to one of the steam login servers, it also dies at lon1-up hop, though it still makes it through to the end.

tracert 72.165.61.187

Tracing route to 72-165-61-187.dia.static.qwest.net [72.165.61.187]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 7 ms 6 ms 41-132-28-1.dsl.mweb.co.za [41.132.28.1]
3 9 ms 9 ms 9 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 9 ms 9 ms 9 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 13 ms 11 ms 10 ms TenGigE0-1-0-0.12.vic-up-2.mweb.co.za [196.22.16
9.242]
6 11 ms 12 ms 12 ms TenGigE0-1-0-0.42.vic-up-1.mweb.co.za [196.22.16
9.217]
7 246 ms 234 ms 235 ms pos0-0-0-0.lon-up-1.mweb.co.za.175.22.196.in-add
r.arpa [196.22.175.210]
8 * * * Request timed out.
9 242 ms 309 ms 580 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
10 311 ms 311 ms 311 ms te0-3-0-4.ccr22.bos01.atlas.cogentco.com [154.54
.5.122]
11 312 ms 312 ms 312 ms te0-0-0-3.ccr21.jfk02.atlas.cogentco.com [154.54
.44.37]
12 320 ms 319 ms 320 ms te0-3-0-6.ccr21.dca01.atlas.cogentco.com [154.54
.41.5]
13 331 ms 337 ms 331 ms te4-2.ccr01.atl01.atlas.cogentco.com [154.54.28.
237]
14 329 ms 329 ms 333 ms te4-3.ccr01.atl02.atlas.cogentco.com [154.54.0.1
62]
15 331 ms 331 ms 331 ms qwest.atl02.atlas.cogentco.com [154.54.10.62]
16 401 ms 400 ms 401 ms tuk-edge-12.inet.qwest.net [67.14.4.10]
17 401 ms 400 ms 401 ms 63-234-174-50.dia.static.qwest.net [63.234.174.5
0]
18 * * * Request timed out.
19 402 ms 402 ms 401 ms 72-165-61-187.dia.static.qwest.net [72.165.61.18
7]

Trace complete.
Click to expand...
 
Yes well now I can't even access ANYSITE with MWEB, thank goodness for my 3G stick
 
Pr⊕phet said:
seriously, you telling me that if i have a problem with a product, but it's already been noted as faulty in the public domain and the company in question knows i have a problem, i still have to go and make posts and threads about it ?

seriously don't understand your logic. mweb has noted there is a fault, mweb has said they will fix it and yet you need to get everyone in to post they have a problem because of that problem ? unproductive ?
Click to expand...

Hardly making multiple threads about it, but posts in the MWEB thread? Sure.

MWEB can note all the faults they want, but the problem is that faults keep occurring, and it's ridiculous that I have to have several levels of redundancy on a consumer connection just to maintain constant Internet access.

Last I checked this was a consumer forum, so we as consumers should feel free to complain when services are underperforming. Telling us to switch ISPs and/or stop complaining if we don't like the service is absurd.
 
life|form said:
Hardly making multiple threads about it, but posts in the MWEB thread? Sure.

MWEB can note all the faults they want, but the problem is that faults keep occurring, and it's ridiculous that I have to have several levels of redundancy on a consumer connection just to maintain constant Internet access.

Last I checked this was a consumer forum, so we as consumers should feel free to complain when services are underperforming. Telling us to switch ISPs and/or stop complaining if we don't like the service is absurd.
Click to expand...

+1

Keep posting whatever you want to say about the people you are giving YOUR money to.
 
life|form said:
Hardly making multiple threads about it, but posts in the MWEB thread? Sure.

MWEB can note all the faults they want, but the problem is that faults keep occurring, and it's ridiculous that I have to have several levels of redundancy on a consumer connection just to maintain constant Internet access.

Last I checked this was a consumer forum, so we as consumers should feel free to complain when services are underperforming. Telling us to switch ISPs and/or stop complaining if we don't like the service is absurd.
Click to expand...

true, but i would have to ask myself this : why stay with something that clearly is not working.

if we all just kept moaning about a service rendered by a company and never voted with our pockets, they will keep on being just that sad panda you are experiencing them to be. unless of course in your case you can't afford the competition and have to stick it out with mweb, is that the case ?

all i'm saying in short is ( and i never said GTFO if you don't like it ) is that if it doesn't suit your needs, why are you still with them ?

i've tested linoman's host with both my mweb and my webafrca, both failing - though it was magically noted that just mweb fails, right.

i mean it would not be as fun as when we actually agree that not just mweb is at fault here...



VioAdmin said:
+1
Keep posting whatever you want to say about the people you are giving YOUR money to.
Click to expand...
i'm curious, at what point are you going to put where your mouth is ?
 
Pr⊕phet said:
true, but i would have to ask myself this : why stay with something that clearly is not working.

if we all just kept moaning about a service rendered by a company and never voted with our pockets, they will keep on being just that sad panda you are experiencing them to be. unless of course in your case you can't afford the competition and have to stick it out with mweb, is that the case ?

all i'm saying in short is ( and i never said GTFO if you don't like it ) is that if it doesn't suit your needs, why are you still with them ?
Click to expand...

I think you need to inject some grey into that black-and-white world of yours. I don't have to love a service unconditionally to keep paying for it, and I won't apologize for the faults of a service simply because I pay for it, nor will I claim that the fault lies with me for continuing to pay for it.
 
Pr⊕phet said:
this might be daft, but did you try the google dns instead of mweb's ?

8.8.8.8
8.8.4.4

i think...



give me the host's ip at least so i can do a tracert for myself. no harm i'm sure.
Click to expand...

I use opendns and tried WA's dns and mweb's DNS as well as my own custom dns servers... I usually try to not have monkeys tell me **** I know is untrue or "reboot your router" type **** and waste my money on phone calls.
 
Hi all,

All links have been restored and traffic should now start to normalise, thanks everyone for you patience and understanding.

Engineers will continue to monitor.

Kind regards
MWEB Operations
 
All working here. NNTP at full speed!! This is more like it. I haven't seen full speed like this for about 3 weeks!

.....bugger. Shouldnt have said anything. After 20 mins its now throttled back to 100Kbs :(
 
Last edited:
Coldon said:
here's a trace i did earlier to one of the steam login servers, it also dies at lon1-up hop, though it still makes it through to the end.
Click to expand...

Gents please bear in mind a request timed out on a particular hop in the trace is more often than not simply an indication that the router on that hop is not responding to ICMP requests :)
 
Last edited:
The faulty link on the Cape Town IPC has been restored and the network is operating at full capacity again, thanks for your patience while we sorted this out. I've noticed a couple of the last few posters expressing frustration over what really sound like localized problems to me. I know that it's nearly impossible to keep you guys completely happy when it comes to P2P speeds :), but the network is in very good shape at the moment so I really would like to ask that those of you who are experiencing general problems with browsing, streaming, or latency please work with our reps here, give them as much info as you can and we will do everything we can to try and help you resolve your problems.
 
Still having jitter on my account.turn off all PC's and unplugged all network cables and then did a pingtest with a laptop running a freshly installed copy of win7. jitter jumps between 10 and 150.ping jumps between 80 and 230.


problem has to be with my mweb account or my telkom line.going to call telkom for a port recreate (forgot again today) and if that doesn't work then someone from telkom will have to come check the boxes to see if all the rain water is cleared.


if all else fails,I'm calling mweb to try and solve it.
 
Please let us know if you don't come right Bloodhound -I'll make sure we do everything we can to assist.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X