To help achieve the best possible price for you, we deploy our servers at a scale, pace, and expectation that helps us keep the costs low, to your benefit. However, this also means we defer maintenance on server failures until scheduled maintenance windows.
If the unfortunate situation occurs where a server fails, a replacement server is provided in your registration slot with the same OS and keys as the original was provisioned with. See also: Backups and Data Recovery.
Because of this, we have found the workloads that work best on these servers are for ephemeral scalable services which are spread across regions/pods, such as application farms.
The best parallel to this behavior are the lower-cost “Spot” instances at AWS, which have a lower price-point, but can be shut down as circumstances change.
As described prior, these servers are designed for distributed availability, so systems that support individual node failures are best. You can achieve greater than 5-9 SLA through through your software design, by setting up your service crossing multiple zones.
Full details on our SLA are in the Service Level Agreement section of our Terms and Policies.
