Notices
| Server | Status | Load | Uptime |
| #1 | OK | |||||||||| | 99.9% |
| #2 | OK | |||||||||| | 99.77% |
| #3 | OK | |||||||||| | 98.57% |
| #4 | OK | |||||||||| | 99.86% |
| #5 | OK | |||||||||| | 99.99% |
| #6 | OK | |||||||||| | 100% |
| #7 | OK | |||||||||| | 99.29% |
Uptime is a measure of the availability of the service over the last 30 days.
19 April 2013
Server Six suffered an unplanned power outage of approximately 30 minutes, which necessitated database integrity checks on recovery; service has now been restored.
18 July 2012
We experienced an outage of approximately 20 minutes on servers Two and Three today due to a connectivity fault at our provider. Service is now fully restored.
27 April 2012
Server Six suffered a power event which caused a restart. This necessitated integrity checks on the database, which took approximately 20 minutes. Total downtime before service was fully restored was approximately 40 minutes. Apologies for the inconvenience caused.
08 December 2011
Our datacentre experienced a power event and forced servers Two and Three to restart. On startup, the databases required emergency integrity checks to be run. It was some time before these were completed and service was restored and stabilized. We apologize for the inconvenience caused.
25 September 2011
Server One suffered a network outage from 20:35 UTC to 3:00 UTC. We are investigating. Apologies for the inconvenience caused.
22 September 2011
Today we transferred Server Six to new hardware in order to boost performance and reduce latency. During this transition there was a short period of downtime on this server and on Server One due to related updates.
