South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
http://www.seacom.mu/news/article-132/message-from-ceo-23-march/
Message from CEO – 23 March
As SEACOM has indicated in previous communications, multiple cable systems continue to be affected across Africa, the Middle East and Asia. I know that many of you are keen to know the cause of the outage is a physical cable cut some kilometres north of the coast of Egypt in the Mediterranean Sea. This is not likely to be known until the cable is repaired in the coming week or two and the damaged section is recovered from the seabed and inspected. However we suspect, based on our experience with sub-sea systems and the nature of the sea area where the cut has occurred, that the most likely cause is external aggression to the cable most probably caused by a larger vessel dragging its anchor across the sea bed. Unfortunately this remains a common cause of damage to cable systems globally, despite our continued efforts to protect the cable with armour, burying, notifications to ships of cable location and exclusion zones.
The SEACOM team’s first focus at this time remains getting restoration services turned up and our resources are committed to that work. However, this process is proving much more complex and taking longer than we were initially told by our suppliers and would have expected. Whilst we believed we had secured adequate restoration capacity between Egypt and Europe yesterday (Friday), it has since eventuated during today that the physical capability to connect this capacity to our services in Europe is neither adequate nor stable enough. In addition the capacity that may be available is in a long line of activations requested by many carriers (and requiring many hundreds of Gb’s) and is not progressing at the rate we, or our customers, need.
SEACOM continues to push for activation as a priority, co-ordinating across a number of carriers internationally. However, as this is not providing solutions in the time frame we require, we are also actively seeking new restoration solutions. This will continue to take some time and we are not able to provide timeframes as yet on when services will be restored.
Please be assured that the SEACOM team is working hard to get our services back up as quickly as we can. We will continue to communicate directly to customers and post here as we have information for you.
With our sincerest apologies,
Mark Simpson
CEO, SEACOM
It's difficult to find a really good ISP that doesn't rely on SEACOM and is big downloader friendly![]()
This.
The number of mweb users that have had to resort to Axxess/Afrihost free accounts is proof of just how ineffective mweb’s “redundancy” has been.
I think mweb are going to be receiving a mountain of cancellation letters come Monday morning.
I am using the Axxess 3 Gig offer - and I must say it appears to be flying along compared to my 4 meg MWeb.
What MWeb has done is give their competitors a massive bite at the cherry.
Will see how it goes.
That said, MWeb support here is great, but there is nothing that a support person can do when the techs in the background can't deliver the goods - I do not believe that it was too much to ask for the basics to be usable - the backend techs were less than successful @ achieving this.
Plugg ?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert eu.battle.net
Tracing route to eu.battle.net [80.239.186.40]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 11 ms 12 ms 11 ms 41-133-122-1.dsl.mweb.co.za [41.133.122.1]
3 26 ms 26 ms 26 ms te1-1-0.502.cpt-ipc-1.mweb.co.za [196.28.178.166
]
4 26 ms 26 ms 26 ms 197-84-3-2.cpt.mweb.co.za [197.84.3.2]
5 187 ms 176 ms 192 ms TenGigE0-7-0-2.12.cpt-p-2.mweb.co.za [196.28.178
.114]
6 * 183 ms 184 ms 197-84-4-195.cpt.mweb.co.za [197.84.4.195]
7 180 ms 183 ms 194 ms 176.67.177.131
8 * 194 ms * 176.67.177.129
9 184 ms 184 ms * 176.67.177.148
10 185 ms * 251 ms ldn-b5-link.telia.net [62.115.13.17]
11 * 191 ms 299 ms ldn-bb2-link.telia.net [213.155.132.196]
12 185 ms 185 ms * prs-bb2-link.telia.net [80.91.247.240]
13 191 ms 186 ms 186 ms prs-b8-link.telia.net [213.155.131.19]
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.
C:\Windows\system32>
Just out of interest, will I be able to do anything until seacom is done? It seems not even facebook is loading fully.
Mweb, will i be able to use a trial account of another ISP until this fiasco is sorted? Also, will i be able to if mweb control my line? If not then please appease me as a customer by granting me the same amount of days of unshaped access for the amount of days I have had no worthwhile internet...so far 2 days and counting. Seems if unreasonable internet seems like nothing worth accounting for in mwebs infrastructure, then my unreasonable request should fit right in
![]()
Already made use of both of these.... and also the 5GB's from Imaginet and the 5GB Trial from Webafrica, and the 7-day MWEB Uncapped Trial.
EDIT: URL's
Imaginet 5GB
MWEB 7 Days Uncapped Trial
Webafrica 5GB Trial