> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/security/qualite-de-nos-services.md).

# Quality of Service

We do our best to guarantee the best availability and the proper functioning of our services.

## Infrastructure & scalability

Our cloud infrastructure allows us to scale up our applications to reduce the impact of increased audience on response times.

## Real-time transparency on the availability of our services

All of our services are monitored by probes in real time. You can check the status of the service on the following page: [**https://status.dastra.eu**](https://status.dastra.eu)

## Availability

Our goal is to ensure an availability rate of 99.5% and a response time of our Rest API <1000ms

## Support

Our support team is committed to responding to all tickets in less than 48 hours.


---

# 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://doc.dastra.eu/en/security/qualite-de-nos-services.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.