Notification at 20:04 on 23 July 2010 read that the link was back up and stable.
For now. (more…)
Posts Tagged ‘downtime’
[UPDATE] SEACOM – finally, a light of hope after cable outage and line down: 23 July
2010
07.22
07.22
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.
[UPDATE] SEACOM operational update re repairs and down time
2010
07.17
07.17
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…)
[UPDATE] SEACOM still eyeing the 22 July as targeted restore date
2010
07.15
07.15
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…)
[UPDATE] SEACOM – no news is good news?
2010
07.12
07.12
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…)
[UPDATE] SEACOM cable outage update – new ETA: down until 22 July
2010
07.09
07.09
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…)
[UPDATE] (no) News on SEACOM down due to router off Mombasa
2010
07.09
07.09
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…)
[UPDATE] SEACOM down – now their website, too
2010
07.08
07.08
Now the website, too...
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…)
[UPDATE] More news : SEACOM router down
2010
07.07
07.07
Local ISPs have been making a variety of attempts and efforts to reroute local traffic to bridge the virtual shut-down of the connectivity of those users solely dependent on the SEACOM fibre-optic cable for their Internet access.
Internet Solutions in South Africa have put in place a variety of rerouting options which, depending on the downstream ISPs, should result in improved browsing availability. Alternate international routes by IS were confirmed to be up in semi-live state yesterday late afternoon. (more…)
[UPDATE] SEACOM cable offline until at least 11 July
2010
07.06
07.06
Slow Internet access (if any – in some cases, you can’t connect to sites without using a proxy) in South Africa… SEACOM has announced that the actual repair on the repeater in segment 9 will take only a few hours, though the full process may take at least 6 – 8 days. The ship is not out and mobilised yet. On their website, there is an update relating to the latest system failure: (more…)
MTN Business goes down – Network Outage over
2009
12.02
12.02
Seems as though systems are being restarted / links restored, 1hr 10 min later… Whole of South Africa was affected by the network outage.
Running commentary here.
To quote the WebAfrica forum “Is this “network issue” anything to do with the power failure (and generator backup failure) that occurred at MTN moments ago bringing down the entire Hetzner hosting facilities?”
mybroadband.co.za is still struggling to come back online, and has been taken offline again…
Update: “According to MTN Business’ Edwin Thompson an Eskom power failure at 14:30 meant that the data centre relied on generator power this afternoon. Unfortunately the main generator ‘blew itself up’ which impacted the electricity infrastructure at the facility. While the power and generator system for the facility is fully redundant, Thompson explained that this it is not really possible to prepare for these types of unexpected events.
“The Gallo Manor data centre is a key hosting facility in South Africa with numerous large clients like iBurst and Hetzner. The downtime therefore does not only affect websites like MyBroadband, but also hosted services like authentication & billing for iBurst and hosted PBX solutions.” – mybroadband.co.za is back up…
MTN confirmed that it is experiencing network problems. “MTN is experiencing network problems in Pretoria and surrounding areas, which are impacting on all services. We are currently investigating the matter and we will shortly confirm how soon the problem is expected to be resolved,” said Sameer Dave CTO of MTN SA.
MTN Business goes down
2009
12.02
12.02
So MTN Business’s Datacentre is down (was Verizon Business, was UUNET). JNB issue, but whole network affected. Should sites not resolve, that’s most likely the problem. No indication of source of issue (Telkom ATM link? faulty Cisco router reload?)
We await with baited breath… Meanwhile, iol.co.za and FNB, as well as iafrica.com and Standard Bank, to name a few, are down…
The MTN Business sites are all non-responsive – all DNS not returning IPs, either… “Server not Found” issue…
Sigh…
Update:
It’s a doozy:
- ns4.iafrica.com returned (SERVFAIL)
- ns0.is.co.za returned (NORECORDS)
- ns1.coza.net.za returned (SERVFAIL)
- ns0.neotel.co.za returned (NORECORDS)
- ns2.coza.net.za returned (NORECORDS)
- ns0.plig.net returned (NORECORDS)
- ns2.iafrica.com returned (SERVFAIL)
- ns1.iafrica.com returned (SERVFAIL)
Update: Indeed, can confirm that there was a power failure in Johannesburg (JNB) (co-incidentally at the same time as the comment below). Alledgedly just been restored and network is being brought back online/troubleshot… They’re also investingating why the network in Cape Town (CPT) went down on a JNB issue…
Affects the entire network in South Africa, so browsing is going to be helluva slow…
Update: 16h30 — MTN Business Customer Centre is online again, guess they’re bringing things up step by step… But sites like mybroadband.co.za are still down…
Update: Allegedly, they were going to replace and update the Durban UPS setup today (and Cape Town, too), finishing at 13h00 (15h00), which is not to have caused the issue — no notices or information yet; there was not even a notification mail triggered (via any network).
Update: 16h41 — Iafrica.com’s back, as is Standardbank.co.za.
Total down time on network: 1hr 10min – all systems and mail and DNS responding correctly from the Farm. Some server up north don’t seem so lucky – looks like they’re being physically restarted!?
Sigh. Let’s see what the “explanation” is.