Yovale servicelevel agreement
This Service Level Agreement (SLA) governs the availability and performance of the Yovale managed WordPress hosting service. It explains the uptime target, how downtime is measured, what does and does not count toward the target, and how service credits are issued when the target is not met.
Read the SLA by section
The agreement is short and direct. Use the pills to jump to a clause; nothing is hidden behind progressive disclosure.
Definitions
The defined terms used throughout this SLA.
Service
"Service" means the Yovale managed WordPress hosting service made available to the Customer at yovale.com under the Yovale End User License Agreement, including the Customer's provisioned WordPress site(s), the dashboard, and the operational infrastructure that supports them.
Customer site
"Customer Site" means an individual WordPress site provisioned by the Customer through the Yovale dashboard. Uptime is calculated independently for each Customer Site.
Uptime, downtime, and availability
"Uptime" means the percentage of total minutes in a calendar month during which a Customer Site responded successfully to HTTP requests issued from Yovale's monitoring infrastructure.
"Downtime" means any minute during which a Customer Site failed to respond, returned a 5xx response code for more than 60 consecutive seconds, or was otherwise unreachable due to a fault in the Service.
"Availability" is calculated as (Total Minutes − Excluded Minutes − Downtime Minutes) / (Total Minutes − Excluded Minutes) for each Customer Site, expressed as a percentage.
Uptime target and measurement
How the uptime number is calculated and where the measurement is taken.
Monthly uptime target
Yovale targets 99.99% Availability per Customer Site, per calendar month. This target represents the operational goal Yovale designs the platform around.
Service credits become available when measured Availability falls below 99.9% for a given Customer Site in any single calendar month, in accordance with the credit schedule in Section 5.
How availability is measured
Availability is measured by Yovale's monitoring infrastructure, which issues HTTP probes against each Customer Site at one-minute intervals from at least two geographic regions.
A Customer Site is considered Down only when two consecutive probes from independent regions fail within the same minute, in order to filter transient network issues unrelated to the Service.
Monthly Availability is published in the Customer's dashboard and is the figure used for service credit calculations.
Exclusions
Downtime that does not count against the uptime target.
Planned maintenance
Planned maintenance windows announced through the Yovale dashboard, status page, or email at least 48 hours in advance are excluded from Availability calculations.
Yovale will schedule planned maintenance to minimize impact and will publish the start, end, and scope of the maintenance window before it begins.
Customer-caused unavailability
Downtime caused by Customer Site code, plugins, themes, custom configurations, exhausted plan resource limits, or actions taken from the Customer's account is excluded from Availability calculations.
Examples include site crashes caused by a Customer-installed plugin, deliberate suspension of the Customer Site by the account owner, exceeding the request, bandwidth, or storage limits of the active plan, and outages caused by the Customer's own DNS misconfiguration.
Force majeure and third-party dependencies
Downtime caused by events outside Yovale's reasonable control is excluded. This includes failures of upstream networks, internet backbone outages, denial-of-service attacks beyond the protective capacity of Yovale's edge, governmental action, natural disasters, and other events meeting the force majeure standard in the Yovale End User License Agreement.
Downtime caused by failures of Customer-controlled third-party services (for example, a Customer-configured SMTP provider rejecting transactional email) is also excluded.
Trial and free accounts
Trial accounts, free promotional accounts, and accounts that have not yet completed payment do not qualify for service credits under this SLA. The uptime target still applies operationally; only the credit remedy is limited.
Service credit schedule
What you receive when Availability falls below 99.9% for a Customer Site in a single calendar month.
Credit table
Availability between 99.5% and 99.9% inclusive: 10% credit against the next billing cycle, calculated on the proportional monthly cost of the affected Customer Site.
Availability between 99.0% and 99.5% (exclusive of 99.5%): 25% credit on the same basis.
Availability between 95.0% and 99.0% (exclusive of 99.0%): 50% credit on the same basis.
Availability below 95.0%: 100% credit on the same basis for the affected month.
How credits are applied
Credits are issued against the Customer's next renewal invoice for the plan that the affected Customer Site belongs to.
Credits do not roll forward beyond the next renewal cycle, are non-transferable to other accounts, and have no cash value.
The maximum service credit issued for any one Customer Site in any single calendar month is 100% of that Customer Site's proportional monthly cost.
How to claim a credit
The process and the time limits for submitting a credit claim.
Submit within 30 days
To request a service credit, the Customer must submit a written claim to support@yovale.com within 30 calendar days of the end of the month in which the qualifying downtime occurred.
The claim must reference the affected Customer Site, the calendar month, and the Customer's account email address. Yovale's measured Availability figure controls; supporting evidence from the Customer is welcomed but is not required.
Response and review
Yovale will acknowledge each claim within 5 business days and will issue a final determination within 15 business days of acknowledgement.
If the claim is approved, the credit will be applied to the next renewal invoice and the Customer will receive written confirmation. If the claim is rejected, Yovale will explain the basis for the rejection in writing.
Sole and exclusive remedy
Service credits issued under this SLA are the Customer's sole and exclusive remedy for any failure to meet the uptime target. This SLA does not create, expand, or restrict any other warranty, indemnity, or liability provision set out in the Yovale End User License Agreement.
Changes and contact
How updates to this SLA are communicated and where to reach Yovale.
Updates to this SLA
Yovale may amend this SLA from time to time. Material changes — including changes to the uptime target, the credit schedule, or the exclusion list — will be announced through the Yovale dashboard, status page, and customer email at least 30 days before they take effect.
Continued use of the Service after the effective date of an amended SLA constitutes acceptance of the new terms.
Contact
Service credit claims, SLA questions, and incident notifications are accepted at support@yovale.com. Live operational status, planned maintenance windows, and incident history are published on the Yovale status page linked from the dashboard.