Templ.io aims to provide 99.95% uptime, and this Service Level Agreement (“SLA”) is our way for us to guarantee this to you our customer;
This SLA is incorporated into Customer’s Agreement with us, and made a part of it. Terms not defined in this SLA have the definitions set out in the Agreement. The remedies set out in this SLA are Customer’s sole and exclusive remedy for issues covered by the SLA. While we will not modify this SLA arbitrarily, we may do so from time-to-time. Should we make a change to this SLA, we shall notify Customer (e.g. by email or by notification in the Customer control panel). The notification will set out the effective date of any changes. It is important that Customer review the SLA completely.
1. SERVICE AVAILABILITY.
Templ.io will provide service availability of 99.95% (“Service Availability”), calculated on a calendar month basis. The Service Availability will be calculated as follows:
[Total number of minutes in the affected calendar month DIVIDED BY (the total number of minutes of downtime in the affected calendar month MINUS excused downtime)]
2. HOW TO RECEIVE SLA CREDITS.
Customer will receive a credit of five percent (5%) of Customer’s monthly fee for each hour in which we fail to meet the Service Availability for such month (“SLA Credits”). In order to receive SLA Credits, Customer must make a request in writing to templ.io via Support or to Customer’s account manager (if applicable) within 30 days of the event giving rise to such SLA Credits. SLA Credits are based on our monitoring, may not exceed the total amount of recurring fees Customer has paid to us for the month in which we failed to meet the Service Availability, are forfeited at the expiration or termination of the Agreement, may not be aggregated, and will not be paid in cash.
3. EXCUSED DOWNTIME.
“Excused Downtime” means:
- scheduled outages or Force Majeure events;
- downtime caused by a non-standard environment, Customer machine access, Customer’s violation of the Agreement including the Acceptable Use Policy, Customer authored code or changes to the Site or Services by parties other than templ.io, or use that exceeds Customer’s plan capacity (e.g. visitors that exceed the limit for the Customer’s plan);
- emergency maintenance (e.g. in order to apply a patch to address a security vulnerability); and
- planned maintenance that is performed during predetermined time.