South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
A quote comes to mind reading all these complaints...
"Where the hell is -- I had a quote somewhere, I was gonna Google it quickly --goddammit, I had internet like a few hours ago. MWEB! Internets!" - Jack
Pinging www.bbc.co.za [216.8.179.25] with 32 bytes of data:
Reply from 216.8.179.25: bytes=32 time=294ms TTL=49
Reply from 216.8.179.25: bytes=32 time=294ms TTL=49
Reply from 216.8.179.25: bytes=32 time=294ms TTL=49
Reply from 216.8.179.25: bytes=32 time=294ms TTL=49
Reply from 216.8.179.25: bytes=32 time=294ms TTL=49
Reply from 216.8.179.25: bytes=32 time=294ms TTL=49
Ping statistics for 216.8.179.25:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 294ms, Maximum = 294ms, Average = 294ms
Who's being agro?
Mweb are selling a service, if the service is unusable or down, a refund should be given. If the upstream provider they are using has an issue the onus is on them to sort it out with their provider and compensate users.
That's just the basic ethics of service delivery IMHO.
I appreciate the service I get from MWEB, but at the same time, I need, at the very least, to be able to get into my email and do basic things.
Is it just me or since seacom came back online my latency has gone up about 80ms to international sites. Its usually 220ms.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.246.93] with 32 bytes of data:
Reply from 212.58.246.93: bytes=32 time=203ms TTL=49
Reply from 212.58.246.93: bytes=32 time=202ms TTL=49
Reply from 212.58.246.93: bytes=32 time=203ms TTL=49
Reply from 212.58.246.93: bytes=32 time=203ms TTL=49
Ping statistics for 212.58.246.93:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 202ms, Maximum = 203ms, Average = 202ms
C:\Windows\system32>
Hi All
The SEACOM outage has been resolved and we are now running at full capacity as appose to the one third capacity we were running earlier on WACS. Service should slowly be returning back to normal.
We would like to apologize for the inconvenience that was caused.