13:31 Server monitoring indicates the ‘supertuxy’ server has stopped responding. We are working to fix this urgently.
13:43 We have identified a problem with one of the routers at the datacentre. We hope to resolve this within 10-15 minutes.
13:56 This server is back online. We apologise for any inconvenience caused.
15:30 We are aware of problems with some websites on the megalinux server. Some customers may be experiencing ‘Internal Server Error’ messages on their websites if their websites use PHP5. We are working to fix this urgently.
15:44 Websites should now be working again as we have put a temporary fix in place. All PHP5 sites are temporarily running on PHP4. We are now working to re-instate PHP5.
17:22 This issue is now resolved. Sorry for any inconvenience caused.
If you are still encountering any problems please refresh your webpage (Ctrl + F5), clear your browser’s cache and if the problem still persists please open a Support Ticket and we’ll be happy to investigate it.
13:41 We are aware of problems with some websites on the ‘megalinux’ server showing blank pages. We are working to fix this urgently.
13:55 There are some compatibility issues between RPM packages installed during a operating system update last weekend and the HTTP build on the server. We are going to re-build the Apache HTTP server and this should fix any issues. This normally take 40-50 minutes to build.
14:33 This issue is now resolved. Sorry for any inconvenience this problem caused.
10:57 Server monitoring indicates the ‘supertuxy’ server has stopped responding. We are working to fix this urgently.
11:00 Reboot under way.
11:10 Technicians are currently working on this server.
11:32 Server back online. We apologise for any inconvenience caused. Previous uptime was 60 days. Update to follow.
Update: Technicians tested the server on the workbench and found the network card to be faulty. A new card was fitted and the server was put back online.
00:25 We are aware of problems with some websites on the ‘megalinux’ server. We are working to fix this urgently.
00:46 This issue is now completely resolved. We apologise for any inconvenience caused.
Update: More info- A server software update which took place around 10pm was causing HTTPd errors on this server. The error messages built up in the Apache error log extremely fast over a few hours and caused the HTTP daemon to fail. We’ve changed log rotation settings across all our servers to prevent this from re-occuring.
21:56 We are aware of problems with some websites on the ‘ultramagnus’ server. We are working to fix this urgently.
22:40 We suspect the problem is related to automatic updates on the server. We are still working on this issue.
01:02 This issue is now completely resolved. We apologise for any inconvenience caused.
23:21 We are aware of problems with some websites on the ‘ultramagnus’ server, where the websites may be giving errors. We are working to fix this urgently.
00:03 This issue is now resolved. All websites should now be fixed. We apologise for any inconvenience caused.
21:41 We are aware of hardware issues affecting customers on the ultramagnus server. We are urgently working to fix this.
21:49 We have a technician on the ground working to resolve this problem. The server is currently on the workbench.
22:07 This server is now back online. We are continuing to monitor the hardware. We apologise for any inconvenience caused.
07:15 We are aware of connectivity issues affecting customers on the ultramagnus server. We are urgently working to fix this.
07:27 This issue has now been resolved. We apologise for any inconvenience caused.
08:47 We are aware of problems with some websites on the ‘ultramagnus’ server, where the websites may be giving errors. We are working to fix this urgently.
09:36 Most websites should now be working again. There are still 10-20 websites with problems that we are working to fix.
10:21 This issue is now resolved. All websites should now be fixed. We apologise for any inconvenience caused.