> 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-1/details/service-availability.md).

# Service Availability

### Availability commitment

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

As a reference, 99.99% is equivalent to approximately 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**. 
>
> Keeping your workloads running when a machine fails depends on how you design your architecture: that's continuity by design, and you'll see it in Concepts when it's available.

### Where to go next

* The resilience of the physical infrastructure: [Technical characteristics.](/docs-en/productos/servers/details/technical-specs.md)
* What you operate and what we operate: [What is a Server?](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.