> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers/details/service-availability.md).

# Service Availability

The availability commitment of Plenit's infrastructure on which your servers run

### Availability commitment

|              |        |
| ------------ | ------ |
| Availability | 99,99% |

As a reference, 99.99% is approximately equivalent to 4.4 minutes of downtime per month, or about 53 minutes per year.

The full SLA terms—measurement period, calculation method, exclusions, and service credits—are set out in the official service level agreement.

### Availability is not high availability

> #### 🚧 What this commitment covers
>
> The SLA refers to the availability of our **infrastructure**.
>
> Whether your workloads stay up when a machine fails depends on how you design your architecture: that is continuity by design, and you'll see it in Concepts when it becomes available.

### Where to follow

* The resilience of the physical infrastructure: [Technical features.](https://docs.plenit.com/docs-en/productos/servers/details/technical-specs.md)
* What you operate and what we operate: [What is a server?](https://docs.plenit.com/docs-en/productos/servers/concepts/what-it-is.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/servers/details/service-availability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
