Template — review with legal before relying on it. This document is starter copy and is not legal advice.

Service Level Agreement

Our uptime commitment for KingsNode game-server hosting, and the service credits available if we fall short.

Last updated: 24 August 2026

1. Uptime commitment

KingsNode targets a monthly uptime of 99.9% for the game servers and control panel we host on our managed infrastructure. Uptime is measured as the percentage of minutes in a calendar month during which your service is reachable and able to accept connections, excluding the periods described in section 4.

You can view current and historical operational status at any time on our status page.

2. How uptime is calculated

Monthly uptime percentage is calculated as:

Uptime % = ((Total minutes in month − Eligible downtime minutes) / Total minutes in month) × 100

“Eligible downtime” means unplanned unavailability caused by the infrastructure and services within our reasonable control. Downtime is measured from our monitoring systems and confirmed against server-side logs. Short, transient errors of under one minute are aggregated.

3. Service-credit schedule

If eligible monthly uptime falls below the committed level, you may claim a service credit calculated as a percentage of the monthly fee for the affected service, per the table below.

Monthly uptimeApprox. downtimeService credit
99.9% or higherUp to ~43m 12s / monthNo credit due
Below 99.9%~43m 12s – 7h 18m / month10% of monthly fee
Below 99.0%~7h 18m – 36h 30m / month25% of monthly fee
Below 95.0%More than ~36h 30m / month50% of monthly fee

Service credits are issued as account credit against future invoices for the affected service. They are not redeemable for cash. The maximum credit in any single billing month is 50% of that month’s fee for the affected service. Credits are your sole and exclusive remedy for any failure to meet the uptime commitment.

4. Exclusions

The uptime commitment and service credits do not apply to downtime caused by:

  • Scheduled maintenance announced in advance on our status page (we aim to give at least 24 hours’ notice and to schedule during off-peak hours), and emergency maintenance required to preserve security or stability.
  • Customer misconfiguration — including faulty mods, plugins, worlds, scripts, cron tasks, resource limits set by you, or software you install or modify.
  • Denial-of-service attacks beyond our mitigation capacity, volumetric or application-layer attacks that exceed the protection included with your plan.
  • Factors outside our reasonable control (force majeure), including upstream network or power failures at third parties, and internet backbone issues.
  • Suspension or termination of your service for breach of our Terms of Service or Acceptable Use Policy, or for non-payment.
  • Your use of beta, preview or free-of-charge services.
  • Problems with your own local network, device, or internet connection.

5. How to claim a credit

To request a service credit, email [email protected] within 30 days of the end of the affected month with:

  • your account email and the affected service or server ID;
  • the dates and approximate times of the downtime you experienced;
  • any logs, error messages, or monitoring data you can provide.

We will review each request against our monitoring records and respond within a reasonable time, normally 10 business days. Approved credits are applied to your next invoice.

6. Changes to this SLA

We may update this SLA from time to time. Material changes will be reflected by the “last updated” date above and, where appropriate, notified to active customers.

Questions about this document? Contact us at [email protected]. See also our Terms, Privacy Policy and System Status.