Agreements
Service Level Agreement (SLA)
This page sets out what Hostaan commits to on service availability, incident response, and the compensation you receive if the service has an unexpected outage.
1. Scope
1.1 This service level agreement ("SLA") supplements the terms of service ("Terms") of Hostaan Oy ("Provider"). If the SLA and the Terms conflict on service availability and compensation for it, the SLA applies. In all other respects the Terms apply.
1.2 The SLA covers the following paid services ("Service"): the WP 30, WP 40 and WP 50 web hosting plans and the SmartWoo, Nextcloud, Managed Cloud and Reseller Cloud services in all their versions. It does not cover the smaller WP 10, WP 15 and WP 20 plans, SmartWP plans, Hostaan.one packages, the Kotisivukone site builder, DNS service, e-mail-only packages, domain names, SSL certificates, add-ons or any other services not mentioned here.
1.3 For Reseller Cloud, compensation is calculated from the price of the Reseller Cloud server, not from the prices the Customer charges its own customers.
1.4 The SLA is the Provider's commitment to the Customer only. It does not extend to the Customer's own customers, and the Customer may not promise its own customers service levels or compensation that bind the Provider.
2. Definitions
2.1 Outage means a Server-wide interruption in the availability of the Service's server ("Server") that the Provider's monitoring system records as a failure (the situation is shown on the public Service status page). An Outage starts at the first failed check and ends at the first successful check. Only a failure that affects the whole Server and can be verified from the Provider's monitoring counts as an Outage. A problem with a single site, hosting plan or user account is not an Outage.
2.2 Planned maintenance is maintenance announced in advance and entered in the monitoring system as a maintenance window. It is normally done at night (22:00–07:00 Finnish time) and announced, where possible, at least 48 hours ahead on the Service status page or by e-mail. Planned maintenance is not counted as an Outage.
2.3 A qualifying Outage is one continuous unplanned Outage lasting at least 30 minutes.
2.4 Monthly price is the list monthly price of the Service excluding VAT (VAT 0 %). If the Service is invoiced yearly or for another period, the list monthly price is used.
3. Availability and measurement
3.1 The Provider aims for Servers to be available at least 99.9 % of the time each month. The aim is not a guarantee: the Customer's binding remedy for an Outage is the compensation described in section 5.
3.2 Availability is measured for each Server by the monitoring system once a minute. The measured availability figures are published on the Service status page. The measurement also includes Outages caused by faults at the platform provider (e.g. UpCloud or Hetzner) and by attacks on the Provider's infrastructure.
4. Monitoring and response
4.1 Servers are monitored once a minute from several angles: reachability (ping), web server, database, e-mail, server load and WordPress security (malware detections). When the Service fails, the Provider's staff are notified within three minutes.
4.2 During office hours (Mon–Fri 8:00–16:00) staff start corrective action immediately, within a few minutes.
4.3 In the evenings (16:00–22:00) and at weekends (07:00–22:00) a separate on-call monitor follows the same metrics and typically reacts within 10–15 minutes, at the latest within 30 minutes.
4.4 Problems that occur at night (22:00–07:00) are fixed at the latest starting from 07:00 in the morning.
4.5 These are the minimum levels the Provider commits to. In practice we usually react faster. Exceeding a response time does not in itself entitle the Customer to compensation; compensation depends on the duration of the Outage under section 5.
5. Compensation
5.1 For a qualifying Outage the Customer is entitled to compensation equal to 10 times the part of the Monthly price that corresponds to the Outage (VAT 0 %). Compensation = 10 × Monthly price × Outage duration in minutes ÷ 43,200 (30 days).
5.2 Compensation is calculated for the whole duration of the Outage once it has lasted at least 30 minutes. Compensation is at most 100 % of the Monthly price of the Service for the same calendar month.
5.3 Example: the Server of a Reseller Cloud 3.0 UP400 (EUR 499/month, VAT 0 %) is unavailable for 8 hours (480 min). Compensation is 10 × EUR 499 × 480 ÷ 43,200 = EUR 55.44 (VAT 0 %).
5.4 Compensation is recorded on the Customer's account as an SLA balance (VAT 0 %). The balance is deducted from the Provider's invoices at the Customer's request once it reaches at least EUR 10 (VAT 0 %), and in future it can also be used to pay invoices in self-service. Compensation is not paid out in cash.
6. Claiming compensation
6.1 Compensation is claimed within 14 days after the Outage ended in the Hostaan control panel: log in, open the order the Outage affected under Orders and choose Claim SLA compensation. The button is shown only on orders covered by the SLA, and the claim is made by the owner of the customer account. The service, plan and domain name come from the order; the Customer enters the start and end time of the Outage.
6.2 The Provider checks the claim against the monitoring data and processes it within a reasonable time. Compensation is not given automatically without a claim.
6.3 Compensation is not given if the Customer has overdue unpaid invoices.
7. Exclusions
7.1 No compensation is given for Outages caused by: a) planned maintenance; b) actions of the Customer or the Customer's customers, such as their own software and code, or resources running out as described in sections 7.2 and 7.3; c) the Customer's own equipment and network connections; d) third-party services that the Provider does not provide (e.g. external DNS or external APIs); e) suspension of the Service under the Terms; f) force majeure as defined in the Terms; g) attacks that target only the Customer's own site or account and do not affect the availability of the Server. These Outages are also not counted towards availability under section 3.
7.2 Hosting plan resources (WP, SmartWoo and Nextcloud services). Every hosting plan has its own resource limits, such as CPU and memory limits, disk space, number of files, and database and process quotas. When a plan reaches a limit, the server's resource control (e.g. cgroups limits) slows down or stops the plan's processes, the disk cannot be written to, or the site may be unavailable. Such a situation affects only the Customer's own plan and is not a Server-wide failure, so it does not entitle the Customer to compensation even if the site is unavailable while it lasts. The plan can be changed to a larger one when needed.
7.3 Server resources (Managed Cloud and Reseller Cloud). The Customer is responsible for choosing a Server size that is sufficient for its use. No compensation is given for an Outage caused by the Server running out of CPU, memory, disk space, disk performance or other capacity because of the load from the Customer, the Customer's customers, or their sites and applications. Failures of the Server hardware, the cloud platform, the network or the system software maintained by the Provider do entitle the Customer to compensation. On request, the Provider helps to assess a suitable size and to move the Server to a larger one.
7.4 The Provider assesses the cause of an Outage from its monitoring system and the Server logs, and tells the Customer when the claim is processed if the Outage is excluded from compensation.
8. Relation to the Terms
8.1 Compensation under this SLA is the Customer's sole remedy for an Outage. It does not extend the Provider's liability under clauses 6.8 (indirect damages, loss of data and force majeure) and 6.9 (maximum liability) of the Terms, and compensation given counts towards the maximum in clause 6.9.
9. Changes to the SLA
9.1 The Provider may change this SLA by notifying Customers at least 30 days before the change takes effect. Changes that improve the Customer's position take effect immediately. The current SLA is always on this page.