MWEB Uncapped ADSL Feedback - Part 3

I'm throttled? I only download late at night, can't you only throttle me late at night...

Your throttle will automatically be lifted once you've dipped below the (approximate) 100GB threshold for your package over a 30 day rolling window.
 
So is there any news on the midnight outage ?

It's been sorted since. Are you able to connect? If not, switch your modem off for a bit before attempting to reconnect.
 
I'm not asking if it's fixed, I'm asking why there was an outage.

Why, because my clients are asking me why they had no access and I need to let them know .
 
Last edited:
I'm asking why there was an outage.

Why, because my clients are asking me why they had no access and I need to let them know .

Understandable. Which area are your clients from?
 
C:\Users\Nelis>tracert 185.34.104.212

Tracing route to 185.34.104.212 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.174
2 <1 ms <1 ms <1 ms 192.168.2.1
3 * 7 ms 8 ms 41-135-115-1.dsl.mweb.co.za [41.135.115.1]
4 11 ms 12 ms 12 ms 197-80-96-186.jhb.mweb.co.za [197.80.96.186]
5 148 ms 17 ms 11 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
6 194 ms 206 ms 192 ms tengig-0-0-0-2-11-vic-p-2.mweb.co.za [197.80.5
26]
7 194 ms 194 ms 192 ms s2-pos0-3-2-0-pos0-3-0-0.thd-p-1.mweb.co.za [1
.80.5.9]
8 197 ms 195 ms 195 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
9 192 ms 193 ms 193 ms xe-8-3-1.edge3.London1.Level3.net [195.50.124.
3]
10 * * * Request timed out.
11 * * * Request timed out.
12 204 ms 203 ms 204 ms unknown.Level3.net [212.162.40.138]
13 201 ms 201 ms 201 ms unknown.prolexic.com [72.52.48.35]
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.
 
p2p shaped to nothing 0kb ????

this mweb shaping is starting to get ridiculous ...

I wanted to download windows 10, from MS tonight.. I know mweb shape that too death too
 
p2p shaped to nothing 0kb ????

this mweb shaping is starting to get ridiculous ...

I wanted to download windows 10, from MS tonight.. I know mweb shape that too death too


Hi fbman, P2P gets given the lowest priority on our network and speeds are not guaranteed.

However the download from MS should be fine
 
I'm getting a lot of packet loss trying to reach amsterdam on mweb this afternoon. Unable to play planetside 2 (ping around 500 instead of 200) and my groups teamspeak sounds like they are underwater (how teamspeak always sounds over a poor link)

Edit: Also affecting web browsing. Sites/pages are slow to load or don't load. Eg: twitter.com
 
Last edited:
I'm getting a lot of packet loss trying to reach amsterdam on mweb this afternoon. Unable to play planetside 2 (ping around 500 instead of 200) and my groups teamspeak sounds like they are underwater (how teamspeak always sounds over a poor link)

Edit: Also affecting web browsing. Sites/pages are slow to load or don't load. Eg: twitter.com

HI, send me a PM wiith your MWEB details and also a trace route to a local and international site
 
Hey MWeb Guy

I use the DynDNS DDNS service for a couple of hosts on my network, and I'm having trouble with patchy DNS performance from MWeb's default DNS server(s) (usually 197.84.84.84 - 197-84-84-84.mweb.cpt.co.za).

<snip>

Can you shed any light on why that might be happening ?

I guess not, huh ?
 
We prefer our customers to use the automatic DNS settings instead.

Who said I wasn't using the auto settings at the time ??
After I picked up the problem with DNS, I launched some lookup queries to the same DNS server as was being supplied as the primary under the auto DNS settings, ie 197.84.84.84. This is an MWeb DNS server in Cape Town (called 197-84-84-84.cpt.mweb.co.za).
The problem is not what DNS settings I'm using, the problem is that MWeb's DNS servers occasionally refuse a valid query. Why ?
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X