MWEB Uncapped ADSL - Official Q & A

Status
Not open for further replies.
@PeterCH @MWEB Operations

Tested it as well, on Mweb the page will not load, MTN/SAIX it loads fine.
The rest of the site loads fine, just the above mentioned page doesnt.
 
rambo919 said:
Post office and parcel tracking pages has for me always mostly not worked or worked slow enough to make murder a very good option...
If im lucky it decides to work, this behaviour was customary WAY before uncapped so I just thought it was a gov related service being governmental hehehe
Click to expand...

+1 Track and trace site did not work reliably last year on a capped MWeb account.
 
SabreWolfy said:
+1 Track and trace site did not work reliably last year on a capped MWeb account.
Click to expand...

Thanks SabreWolfy, again this makes me think that the site may be prone to caching issues as this is something we did encounter from time to time with SAIX transparent caches as well.
I'm going to ask our networks team to look into this, but I really do need a volunteer with a parcel to track to step forward so that I can give them some more data to work with :)

Kind Regards
MWEB Operations
 
Mweb operations, see explain this dude :D


Pinging games.saix.net [196.43.22.222] with 32 bytes of
Reply from 196.43.22.222: bytes=32 time=13ms TTL=245
Reply from 196.43.22.222: bytes=32 time=12ms TTL=245
Reply from 196.43.22.222: bytes=32 time=13ms TTL=245
Reply from 196.43.22.222: bytes=32 time=12ms TTL=245

I wish i knew if it was my exchange or mweb. Mweb man how would i know if it is a telkom problem? Obviously speaking to telkom has been fruitless :D.
 
Hi killadoob

That's a really nice ping, very different from the one you posted yesterday.
I will contact you privately on the details you provided to discuss how we can investigate this further.

Kind Regards
MWEB Operations
 
killadoob said:
Mweb operations, see explain this dude :D


Pinging games.saix.net [196.43.22.222] with 32 bytes of
Reply from 196.43.22.222: bytes=32 time=13ms TTL=245
Reply from 196.43.22.222: bytes=32 time=12ms TTL=245
Reply from 196.43.22.222: bytes=32 time=13ms TTL=245
Reply from 196.43.22.222: bytes=32 time=12ms TTL=245

I wish i knew if it was my exchange or mweb. Mweb man how would i know if it is a telkom problem? Obviously speaking to telkom has been fruitless :D.
Click to expand...

When the ping is slow, a tracepath would show where the bottleneck is?
 
killadoob said:
Explain a bit more please :D.

How do i do a tracepath?
Click to expand...

If you're using a commercial operating system from Redmond, the command is "tracert":

Code: 
tracert games.saix.net

It will return the time taken for a packet to reach each of the hops between you and the destination, which may assist in determining if their is a problem somewhere en route.

Here's mine for reference:

Code: 
<snip>
 2:  XX.dsl.mweb.co.za (AA.XX.YY.ZZ)             119.627ms 
 3:  tengig-0-0-0-107.vic-ipc-1.mweb.co.za (196.22.169.158) 120.828ms asymm  4 
 4:  vl-92.vic-hscore-1.mweb.co.za (196.22.189.2)         121.886ms asymm  5 
 5:  tengig-0-0-0-0-11.vic-up-1.mweb.co.za (196.22.169.225) 126.087ms asymm  6 
 6:  rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.8.249) 121.880ms asymm  7 
 7:  rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za (196.43.11.166) 120.744ms asymm  9 
 8:  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za (196.43.23.6) 125.261ms asymm  9 
 9:  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za (196.43.23.30) 129.698ms asymm 10 
10:  nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222) 133.145ms reached
     Resume: pmtu 1492 hops 10 back 245

Someone else will have to explain why trace times are always slower than ping times:

Code: 
$ ping games.saix.net
PING games.saix.net (196.43.22.222) 56(84) bytes of data.
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_seq=1 ttl=245 time=33.7 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_seq=2 ttl=245 time=32.6 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_seq=3 ttl=245 time=32.8 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_seq=4 ttl=245 time=31.5 ms
64 bytes from nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222): icmp_seq=5 ttl=245 time=29.1 ms
 
Last edited:
If you're using a Redmond based operating system you can also use pathping. It has the same syntax as tracert, but will run for approximately 5 minutes and give you statistics on the average latency for each hop - useful if you are trying to measure the stability of the connection.
 
MWEB Operations said:
Thanks SabreWolfy, again this makes me think that the site may be prone to caching issues as this is something we did encounter from time to time with SAIX transparent caches as well.
I'm going to ask our networks team to look into this, but I really do need a volunteer with a parcel to track to step forward so that I can give them some more data to work with :)

Kind Regards
MWEB Operations
Click to expand...

Hi,
Thanks for the reply.
The site only loads up partially for me so that not even the box where you input the T&T number appears. Chances are if the site can load completely, it will work from that point on.

Ta,
P.
 
My MWEB 4meg improved rather dramatic, since I've cancelled my account. Speeds improved from 10kbps the previous week to 400-430kbps this past week. I'm reconsidering my cancellation...
 
mika1000 said:
My MWEB 4meg improved rather dramatic, since I've cancelled my account. Speeds improved from 10kbps the previous week to 400-430kbps this past week. I'm reconsidering my cancellation...
Click to expand...

That's great news, please reconsider your cancallation. We are constantly working on network improvements.
 
Is it true that MWEB only charges either full month or half month and no pro rata rates? I'm keen on signing up but not sure if I should wait till the end of the month.
 
anarchy-rabbit said:
Is it true that MWEB only charges either full month or half month and no pro rata rates? I'm keen on signing up but not sure if I should wait till the end of the month.
Click to expand...

Hi anarchy-rabbit,

Since 1 May 2010 we have applied a daily pro-rata rule, this means you will only be charged for the remaining period of the month.

This rule is applicable on all our capped and uncapped products.

Kind Regards
MWEB Operations
 
mika1000 said:
My MWEB 4meg improved rather dramatic, since I've cancelled my account. Speeds improved from 10kbps the previous week to 400-430kbps this past week. I'm reconsidering my cancellation...
Click to expand...

ROFL! If I were cynical I'd suggest: ClientSpeed = AvailableBandwidth + BonusBandwidth * (HasCancelled == True)

:)
 
Last edited:
PeterCH have you tried adjusting your MTU size?

You can check what it is and then try one or two other sizes
Default for PPPOE is 1492 but you can also set it to 1500 or drop it down to 1478 and test it
Allot of times if there is one specific site that gives hassles it is caused by MTU size issues
 
Veneficus said:
PeterCH have you tried adjusting your MTU size?

You can check what it is and then try one or two other sizes
Default for PPPOE is 1492 but you can also set it to 1500 or drop it down to 1478 and test it
Allot of times if there is one specific site that gives hassles it is caused by MTU size issues
Click to expand...

Why would it work via a VPN connection to an offshore (European) bandwidth provider though and not work when using MWEB directly?
Would the MTU setting affect that?

I'll check it anyway. Thanks for the suggestion.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X