Date of next review due: 1st April 2010.
This page details our arrangements for reliability and uptime which apply unless otherwise stated contractually.
Details here apply to all of:
We aim to exceed 99% uptime.
Historical downtime since December 2008 has been:
Non-emergency reboots are minimised and will always be scheduled for out-of-office periods if not at night-time.
Our main and development servers are monitored via a ping service, resulting in a text message being sent to one of the developers if no response is forthcoming.
During the hours of 10-6pm, e-mail to our main contact address, email@example.com, relating to unavailability of the site, will generally get a response within 2-4 hours if not immediately.
Outside office hours, we often in practice would respond to reports of a serious problem, though this should not be relied upon. Downtime is regarded as highest priority above all other work.
The two server administrators make efforts to avoid holidays at the same time.
Phone-based support is not available unless otherwise arranged.
Routing data imports are run overnight up to two or three times per week. During these times, the machine may be less responsive. If the journey planner is subject to a spike, we delay importing until the traffic to the site has eased.
Our backup routine is as follows:
All backups are made to a machine in a different datacentre, and additional off-site backups are in practice made every few months.
At present we have a single production server. We hope to purchase a second server for resilience and speed purposes, but full funding has not yet been found for this.
If your organisation requires increased resilience beyond what is outlined above, please contact us to discuss this; we are happy to consider server upgrades if funding to cover our costs is available.