MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Pinging www.l.google.com [155.232.240.19] with 32 bytes of data:
Request timed out.
Reply from 155.232.240.19: bytes=32 time=35ms TTL=55
Reply from 155.232.240.19: bytes=32 time=35ms TTL=55
Request timed out.
Request timed out.
Reply from 155.232.240.19: bytes=32 time=35ms TTL=55
Reply from 155.232.240.19: bytes=32 time=35ms TTL=55
Reply from 155.232.240.19: bytes=32 time=42ms TTL=55
Request timed out.
Request timed out.
Reply from 155.232.240.19: bytes=32 time=71ms TTL=55
Reply from 155.232.240.19: bytes=32 time=56ms TTL=55
Request timed out.
Reply from 155.232.240.19: bytes=32 time=44ms TTL=55
Request timed out.
Request timed out.
Reply from 155.232.240.19: bytes=32 time=37ms TTL=55
Reply from 155.232.240.19: bytes=32 time=92ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 155.232.240.19: bytes=32 time=35ms TTL=55
Request timed out.
Reply from 155.232.240.19: bytes=32 time=93ms TTL=55
Reply from 155.232.240.19: bytes=32 time=35ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 155.232.240.19: bytes=32 time=35ms TTL=55
Request timed out.

:(
 
We have experienced a brief dip in connectivity, everything seems to be back up again we will continue to monitor. Thank you for your updates and assisting us with our investigation.

Kind regards
MWEB Operations
 
Only connectivity problems/interruptions which have lasted for more than 10 minutes should be reported here :)

In fact, maybe only those that persist after a router restart should be reported. Even if it wasn't the router, by the time it's synced again, the problem may already be resolved :)
 
My downloads keep stopping before they are finished, it is making me unreasonably angry.

What do I do? As per usual phone MWEB and spend days on the phone trying to diagnose the problem? I need the file now! I am getting tired of such a rigmarole every time I want to do the simplest thing on the internet, like downloading a freaking 135 meg file.

Oh, and if anyone one has a clue, I am really struggling to upload files internationally.
 
@copacetic: You've cleared all caches and tried to download the file again by bypassing any caches?
 
SabreWolfy said:
@copacetic: You've cleared all caches and tried to download the file again by bypassing any caches?
Click to expand...

How would I go about bypassing the cache? Please pardon my dimness.

It's been a couple of files throughout the afternoon.

On that note, are there any good download programs I should be using?
 
wget --no-cache ...

Assuming you're using a real operating system, not a commercial one :) Or that you've downloaded wget for Win32. Otherwise clear your browser's cache, although it's not necessarily the same thing. The (broken) file may be (transparently) cached by MWeb somewhere. I had a similar issue months ago which, with the help of MWeb, I traced to a faulty port on the DSLAM.
 
Is there any reason why torrents are shaped soo much after 12 on a sunday morning? getting 25kB/s and getting full line speed on same download from a diff account so I know its not because of a lack of seeders?
 
My 4Mb line has come to the point of complete non usability , this has been going on for a while now.

Think it's time to move to another SP....

ping google.com
PING google.com (155.232.240.19) 56(84) bytes of data.
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=1 ttl=55 time=38.7 ms
64 bytes from 155.232.240.19: icmp_req=2 ttl=55 time=39.7 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=4 ttl=55 time=37.7 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=5 ttl=55 time=37.3 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=7 ttl=55 time=37.5 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=9 ttl=55 time=49.6 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=10 ttl=55 time=38.4 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=11 ttl=55 time=36.8 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=12 ttl=55 time=37.7 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=13 ttl=55 time=38.1 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=14 ttl=55 time=38.3 ms
64 bytes from 155.232.240.19: icmp_req=15 ttl=55 time=38.4 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=16 ttl=55 time=37.6 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=17 ttl=55 time=37.1 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=18 ttl=55 time=36.8 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=19 ttl=55 time=37.3 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=20 ttl=55 time=37.1 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=23 ttl=55 time=36.6 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=26 ttl=55 time=38.1 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=27 ttl=55 time=37.9 ms
64 bytes from gc-cpt-bree-g21-23-19.uni.net.za (155.232.240.19): icmp_req=28 ttl=55 time=37.8 ms
^C^C^C^C^C^C^C64 bytes from 155.232.240.19: icmp_req=29 ttl=55 time=37.7 ms

--- google.com ping statistics ---
29 packets transmitted, 22 received, 24% packet loss, time 56135ms
rtt min/avg/max/mdev = 36.602/38.338/49.613/2.562 ms
 
djtzar said:
My 4Mb line has come to the point of complete non usability , this has been going on for a while now.

Think it's time to move to another SP....

<snip>
Click to expand...

Think it's time to get your actual cabling/network card/router/DSLAM/line checked out.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X