1

Scope

This Service Level Agreement applies to web hosting, e-mail hosting, Kubernetes (paid plans), vServer and object storage. It does not apply to domains, since the reachability of a domain depends on the respective registry and on nameserver operation. It does not apply to the free Kubernetes namespace (free tier).

2

Availability

99%Network availability, monthly average

We measure reachability at the handover point between our network and the internet, determined by automated checks at intervals of no more than five minutes. Availability is calculated per calendar month and per affected service.

The following do not count as downtime: planned maintenance announced in accordance with the section "Maintenance Windows and Emergency Maintenance", faults outside our sphere of responsibility (in particular on the internet or at upstream suppliers), faults due to force majeure, and impairments attributable to the customer’s configuration, applications or actions. Downtime caused by emergency maintenance counts as downtime.

pursuant to § 4.3 of our Terms

3

Credits

If availability falls below target in a calendar month, you will receive, upon request, a credit against the fee for the affected service for that month.

Availability in the monthCredit
98% to below 99%10%
95% to below 98%25%
below 95%50%

Credits must be requested in text form within 30 days of the end of the affected calendar month. The credits for any one month are capped in total at 100% of the fee for the affected service for that month.

These credits are in addition to your statutory rights and do not exclude them. Further claims, in particular for reduction of price or for damages, remain unaffected; a credit received is set off against any damages claim subsequently asserted.

4

Kubernetes Versions

We support the last 2 minor versions.

Namespaces

Namespace products always run on a supported Kubernetes version and receive regular updates.

Version Choice

We determine the Kubernetes version of the cluster; the customer cannot choose a version. Version upgrades are announced on the status page.

Security updates are applied within 72 hours.

5

Maintenance Windows and Emergency Maintenance

We announce planned maintenance on our status page at least 24 hours in advance, stating the expected start, the expected duration and the affected services. The announced time does not count as downtime provided the work is completed within the announced duration; any time beyond that counts as downtime.

Emergency maintenance is work that cannot be postponed and is necessary to close a critical security vulnerability or to avert a comparably acute threat to the security or integrity of our platform, and that cannot wait for an announcement under paragraph 1. We may carry out emergency maintenance without prior announcement. We publish it on our status page as early as possible and at the latest without undue delay after it begins, stating the reason and the expected duration, limit it to what is necessary to avert the threat, and keep the interruption as short as possible.

Downtime caused by emergency maintenance counts as downtime within the meaning of the section "Availability". It is included in the availability calculation and can trigger credits.

For Kubernetes and vServers, the provisions on node and host restarts in the respective service agreement apply in addition.

https://status.itsh.dev