Just in case you’re wondering where noble.gen.nz is, including several photos linked to from this blog, the server it’s hosted on failed this morning and is currently being worked on by my provider The Kiwi Web Hosting Company. This from their announcement page,
Tuesday 26 February 2008 – 07:36
Last updated: Tuesday 26 February 2008 – 15:14
Customers hosted on the sever Mitosis will be affected by a routing issue with this server, causing issues with both email and websites – technicians are currently working to resolve this as quickly as possible
The problem causing this issue has now been determined as a catastrophic hardware failure. Technicians are organising a replacement server, which will then have content from the failed server transfered to it. The process of restoring content can take a considerable period of time and resolution prior to noon today is unlikely. Further updates will be posted here as they become available.
The rebuild/restore process has taken longer than expected but our technicians are still working to get the server online as soon as technically possible. We deeply apologise for the ongoing interruption to service and appreciate your patience in this matter.
This is clearly no small issue, as the server has been out of action since at least 6am this morning, now 10 hours and counting, the longest outage I’ve seen to date. In KWH’s defence outages are rare and normally brief, so hopefully they’ll have it back up soon…
Edit at 7:45pm…
Approaching 14hr (or more) and still down, with a rather disappointing update from KWH,
Tuesday 26 February 2008 – 19:00
Work to date on restoring service for those sites that are hosted on the server Mitosis, has proved to be extremely difficult, with further unexpected issues being encountered. The restore process has had to be restarted, extending out the ETA of service restoration that we had hoped would be by close of business today. It is unlikely at this stage that the service will be able to be restored this evening. We are taking this opportunity while restoring content to virtualise the server, mitigating issues after the content restoration has been completed, and also providing some future redundancy should issues of this nature ever arise again.
We regret that we have not been able to restore service as this point in time to those customers affected by this outage, and are committed to ensuring a resolution as quickly as possible.
Looks like it will return tomorrow…