Notification at 20:04 on 23 July 2010 read that the link was back up and stable.
For now. (more…)
Notification at 20:04 on 23 July 2010 read that the link was back up and stable.
For now. (more…)
SEACOM expects all connectivity to be restored to full pre-crash conditions by 23 July 2010. The repairs are not complete yet, but, officially, “in the final stages of completion”, with only testing to go before the cable goes back down into the water.
Finally, SEACOM has posted new (well, another) report regarding the undersea outage off Mombasa, which, though initially projected to be completed by 11 July will most probably only be finished by 22 July 2010 according to latest reports.
Finally, though, they have announced that the “designated ship has been deployed to the location of the fault where it will proceed to locate the cable on the seabed.” They say that this action will have to take place in and around the area the cabled was dropped by the installation ship over a year ago due to tidal movements that may have relocated the cable on the sea bed. “This is normal and caused by the natural sea bed movements and strong submarine currents in that area.” (more…)
Nothing much new, there is not even an operational update from SEACOM. However, unofficial reports are still pointing to 22 July 2010 as the targeted completion date forthe service to be restored for the submarine cable running up the East African coast. (more…)
Since their last update, SEACOM – via their news section or the SEACOM Blog which are ostensibly the same (sort of very weak SQL coding and gaping holes asking for SQL injection) – has not released any further news since 9 July 2010 — the target date of recovery is 22 July 2010. (more…)
There has been a flurry of updates relating to the repairs to the SEACOM cable. In short – don’t expect anything before 22 July – previous expectations of “5 – 8 days” were over-enthusiastic from the operator themselves…
While restoration capacity has successfully been sourced and implemented from other cable operators servicing the eastern and southern African regions, a lot of work lies ahead regarding the actual SEACOM cable. It appears that the exact location of the cable break, above and beyond the previously reported repeater issues, has been pinpointed at 4 700m below sea level, resulting in the need for specialised repair equipment, robotics and expertise.
The repairs, according to SEACOM, are in the hands of third-party contractors who – beyond weather and sea conditions – run on their own timeline. So the cable operators, SEACOM, have put forward 22 July as a possible next repair date. (more…)
So the site’s back, but there’s no news. No news is good news?
Please note that our News module is currently unavailable, due to a security patch implemented by Hosting – we are working on the problem and the news will be back ASAP. (more…)
The official source for SEACOM press releases, www.seacom.mu has decided to follow suit on the router off Mombasa that has decided to crash, with a very boring bog-standard JET Database error message after the “Detecting Flash” redirection:
Microsoft JET Database Engine error ‘80004005’
Unspecified error
/index2.asp, line 10 (more…)
It seems that a looped include error has broken http://news.bbc.co.uk, creating repetitive nestings — or just a whole whack of emphasis on the Copenhagen climate change story which is self-included 5 times – no wonder the poor BBC Apache server reports “[an error occurred while processing this directive]” — seems that there is an incorrect citing or link… ho hum… happens to all of us 🙂
I’m sure it’ll be fixed soon (though the last update time points to either a serious error or a very slow news day Blair: ‘Right to remove’ Saddam is competing directly with the Climate change prosters march in Copenhagen story (which incidentally does not have a link on the page…)
Ah, the wonder of automation… I wonder what impact this has on twitter and news.google.com feeds?
Update: 9 minutes later, they fixed it 🙂