MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Alexcon said:
not sure if it's just cpt, in pta, 4mb mweb uncapped. its perfect at the moment. streaming music 128kb, streaming youtube and browsing int simultaneously. btw i recently changed my primary dns settings to 196.25.255.34 and secondary to 196.25.255.3. it seemed to give my browsing a kick over the weekend. give it a go ;) anything's worth a try these days...
Click to expand...

Please don't use those settings, those are SAIX addresses. The only reason it's working at all is because we are NATing them back to us which is going to be removed very soon.
 
Will@MWEB said:
The problem with that is that we really don't have any control over the content which is stored on the server other than basic retention and caching rules its a straight feed from an upstream news provider.
Click to expand...

Do we know the news providers?
 
Will@MWEB said:
Please don't use those settings, those are SAIX addresses. The only reason it's working at all is because we are NATing them back to us which is going to be removed very soon.
Click to expand...

Thanks for that Info. What about other local DNS servers when we experience problems with MWeb DNS?
 
ABCpt said:
Yes I did. After midnight I get full speed on news servers, and as I said, browsing is fine.
Click to expand...

Thats exactly what happens to me just on 384. Getting 10kb/s till 12 then after that its fine again. Think it crawls again at like 6-7am.
Is there a fix for this? Is using the SAIX addresses giving full news speeds?
 
International = DEAD

I thought this was resolved?

C:\Users\VanRensburg>ping www.engadget.com

Pinging win.blogsmith.aol.com.aol.akadns.net [195.93.80.36] with 32 bytes of dat
a:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

Tracert:

C:\Users\VanRensburg>ping www.engadget.com

Pinging win.blogsmith.aol.com.aol.akadns.net [195.93.80.36] with 32 bytes of dat
a:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\Users\VanRensburg>tracert www.engadget.com

Tracing route to win.blogsmith.aol.com.aol.akadns.net [195.93.80.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 34 ms 32 ms 36 ms 41-133-64-1.dsl.mweb.co.za [41.133.64.1]
3 44 ms 45 ms 46 ms Te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166
]
4 45 ms 45 ms 47 ms Vlan92.cpt-hscore-1.mweb.co.za [196.28.179.11]
5 49 ms 49 ms 48 ms TenGigE0-2-0-0.11.cpt-up-1.mweb.co.za [196.28.17
8.97]
6 197 ms 201 ms 198 ms pos0-0-3-0.lon-up-1.mweb.co.za [196.22.164.2]
7 198 ms 199 ms 198 ms 149.6.98.17
8 256 ms 256 ms 259 ms te7-6.ccr01.lon01.atlas.cogentco.com [154.54.36.
165]
9 209 ms 207 ms 209 ms te0-2-0-0.ccr21.ams03.atlas.cogentco.com [154.54
.28.157]
10 214 ms 210 ms 216 ms te0-3-0-1.ccr21.fra03.atlas.cogentco.com [154.54
.39.178]
11 213 ms 212 ms 422 ms te1-3.ccr01.fra07.atlas.cogentco.com [130.117.3.
149]
12 272 ms 283 ms 270 ms dar1-frr-G4-1-0.atdn.net [66.185.139.9]
13 223 ms 213 ms 217 ms edge1-frr-xe-0-0-0.net.aol.com [66.185.147.106]

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.
 
Last edited:
And to put the icing on the Cake!

Last Result:
Download Speed: 69 kbps (8.6 KB/sec transfer rate)
Upload Speed: 105 kbps (13.1 KB/sec transfer rate)
Latency: -1 ms
 
sigh, why hasnt this been escalated to upper management already and a statement made, i mean its been 1/4 of the month already.

I guess mweb are too bothered with what they will call their uncapped package from now on.

To mweb speedtest server 4mb line huzzuh
Download Speed: 224 kbps (28 KB/sec transfer rate)
Upload Speed: 346 kbps (43.3 KB/sec transfer rate)
Latency: -1 ms
 
Last edited:
i've been with mweb's basic package for just under a year now. i mainly use it to surf the net, work on my sites, uploading and downloading mp3s, videos, learning stuff, skype and online meetings.

They've been pretty decent, with no problems. A faster speed would be very cool though :)
 
So every monday the problems of slow international speeds come back and then on friday its all good for the weekend?
 
Will@MWEB said:
Please don't use those settings, those are SAIX addresses. The only reason it's working at all is because we are NATing them back to us which is going to be removed very soon.
Click to expand...

Hi Will

Please bear with me here as i'm in no way a guru like you guys when it comes to the intricacies of networking, although I know my way around the basics.

I've been having so much problems with Mweb (as has many) in the past weeks and since MegaXLR suggested to try the DNS benchmark tool Namebench, I changed my settings to the IS server.

attachment.php


http://namebench.appspot.com/id/4844006

Obviously that result is open for interpretation, but since I changed it I can promise you that it feels like a million percent increase. Its such a pleasure to access the internet again, bar the droppings at certain times (i.e 20h00...)

So to my question : Are you going to make it impossible for us to skip your dns servers now? Since theres obviously a problem on them. I don't know what ''NATing'' means, but since you are currently allowing access to alternate DNS servers on your network, does that mean you are aware that yours are problematic?

Regards

P.s : International is wacky atm. Recurring issue as well.
 
Last edited:
And once again, Mweb has problems with their network. Large lag spikes and severe crashes in speed. I really am getting tired of this emerging pattern. Every night its the same thing, you see the same complaints.

Surely the network management guys at Mweb have noticed this, or am I groping in the dark here?
 
@latro

dns servers just change www.google.com to 155.232.240.19 and vice versa, use whichever nameserver you like.

Im pretty sure that telkom and mweb dont peer, so when you type in www.google.com it will take longer before the IP gets resolved, making a substantial change to your general internet experience
 
Last edited:
Just out of interest, do you guys run your speedtest while downloads are running, or do you stop them?
 
avert said:
@latro

dns servers just change www.google.com to 155.232.240.19 and vice versa, use whichever nameserver you like.

Im pretty sure that telkom and mweb dont peer, so when you type in www.google.com it will take longer before the IP gets resolved, making a substantial change to your general internet experience
Click to expand...

So meaning they will still allow that IS name server that i'm using now to be used? If so then i'm happy in that regard.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X