Select Page

Service Level Agreement (SLA)

The SLA specifies our Service Availability and Error Response goals and outlines

remedies for any failure on our part to meet those goals.

This Service Level Agreement (“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 to Customer through service control panel,

dashboard or user interface). The notification will set out the effective date of any

changes. It is important that Customer review the SLA completely.

1. SERVICE AVAILABILITY.

WP Managed Secure 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 Service is available in a calendar month DIVIDED BY

(Total number of minutes in a calendar month LESS 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 WP Managed

Secure 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:

a. scheduled outages or Force Majeure events;

b. 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

WP Managed Secure, or use that exceeds Customer’s plan capacity (e.g. visitors

that exceed the limit for the Customer’s plan);

c. emergency maintenance (e.g. in order to apply a patch to address a security

vulnerability); and

d. maintenance that is performed during the below schedule.

Last updated: December 9, 2016