Service Level Agreement

We target 99.5% Monthly Uptime for each running Cube, calculated as described in Section 2. This commitment is deliberately narrow: it covers only loss of connectivity to, or loss of root-disk access on, a Cube that is caused by the Krova Cloudinfrastructure we operate — the underlying host, host networking, the Firecracker hypervisor layer, and the storage backing the Cube's root disk.

It does not cover the availability, correctness or performance of the operating system, packages, containers, databases, applications or any other software you install, configure or run inside a Cube. A Cube that is reachable and has a working root disk is, for the purposes of this SLA, up — regardless of whether the software you are running inside it has crashed, hung, been misconfigured, or is otherwise unavailable for reasons within your control.

• “Monthly Uptime Percentage” means, for a given Cube and calendar month: (total minutes in the month − Downtime minutes) / total minutes in the month × 100. The calculation is limited to minutes during which the Cube was in the running state at the start of the Downtime Period, and excludes any period described in Section 4 (Exclusions).
• “Downtime” means a period during which a running Cube is, due to a cause within the Krova Cloud infrastructure described in Section 1, either (a) unreachable over the network on every network path we provide to it, or (b) unable to read from or write to its root disk. Downtime is measured from the first automated or customer-reported indication of the condition to the time the condition is resolved.
• “Downtime Period” means a single, continuous occurrence of Downtime lasting at least five (5) consecutive minutes. Downtime lasting less than five consecutive minutes does not count toward Monthly Uptime Percentage, and intermittent conditions that individually fall under this minimum are not aggregated to meet it.

If the Monthly Uptime Percentage for a Cube in a calendar month falls below 99.5%, you are eligible for a service credit against that Cube's charges for that month, calculated as follows:

• Monthly Uptime Percentage below 99.5%: 10%service credit of the affected Cube's charges for that month.
• Monthly Uptime Percentage below 99.0%: 20%service credit of the affected Cube's charges for that month.
• Monthly Uptime Percentage below 90.0%: 100%service credit of the affected Cube's charges for that month.

Only the highest applicable band for a given month is credited — credits are not cumulative across bands. Credits are calculated against the compute, sleep-storage and backup-storage charges actually billed for the affected Cube for the affected month, and are applied as account credit to the space that owns the Cube. We do not issue cash refunds under this SLA.

Monthly Uptime Percentage does not account for, and no Downtime or service credit accrues from, unavailability or disruption caused by or resulting from any of the following:

• Scheduled maintenance for which we provide reasonable advance notice, and emergency maintenance reasonably required to protect the security, integrity or stability of the Service or our infrastructure;
• Force majeure events beyond our reasonable control, including natural disasters, acts of government, power or utility failures, and internet backbone disruptions;
• Outages or degradation of upstream or third-party services we do not control, including upstream network providers, DNS registries and resolvers, certificate authorities, and third-party payment, email or storage providers;
• Your own acts, omissions or configuration, including software, firewall rules, network configuration, resource exhaustion, or credentials you control inside a Cube, and any misuse of the Service by you or anyone using your account;
• Any period during which the Cube, space or account is suspended or restricted in accordance with the Terms or our Acceptable Use Policy, including for a zero credit balance, a suspected Acceptable Use Policy violation, or non-payment;
• Any period during which the Cube is in a sleeping, stopped, booting or otherwise non-running state, including auto-sleep triggered by a zero credit balance — this SLA applies only to Cubes that are in the running state;
• Distributed denial-of-service (DDoS) attacks or other malicious traffic directed at your Cube, our infrastructure, or the internet paths between them; and
• Any beta, preview, early-access or experimental feature or offering, which is provided without any uptime commitment under this SLA.

To request a service credit, email [email protected] within 30 days of the end of the calendar month in which the claimed Downtime occurred. Your claim must include, at minimum: the affected Cube (by name or ID) and space, the dates and times (with time zone) of each claimed Downtime Period, and any supporting detail you have (error messages, monitoring records, or a description of what you observed). We will review claims in good faith against our own monitoring and infrastructure records, which are authoritative for determining whether Downtime occurred and its duration. Our determination of whether Downtime occurred, its duration, and the amount of any service credit due is made in our sole discretion and is final and binding, subject to any non-waivable right you have under applicable law. Claims submitted after the 30-day window, or that omit the information above, are not eligible for a credit.

The aggregate service credits issued under this SLA for a given Cube in a given calendar month will not exceed the total charges actually billed for that Cube for that month. In no event will credits under this SLA exceed the amount you paid us for the affected Cube in the month to which the claim relates.

The service credits described in this SLA are your sole and exclusive remedy, and our sole and exclusive liability, for any failure to meet the uptime commitment in Section 1 or for any Downtime, however arising. Any service credit issued under this SLA is, in all cases, subject to the overall limitation of liability set out in Section 14 of our Terms of Service and does not enlarge, and is counted toward, that limit.