> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/organization-and-account-settings/account-settings-and-support/service-level-agreement-sla-and-incident-management.md). # Service Level Agreement (SLA) and incident management The Service Level Agreements for the Didomi platform is set at 99% availability on a per monthly basis. Didomi has designed its tech stack with a distributed/redundant infrastructure to mitigate the risk of failure. Our tech stack is monitored 24 hours a day, 7 days a week with alerts sent directly to Didomi engineers through various monitoring tools (e.g. AWS CloudFront, New Relic, etc.). We are particularly cautious with our consent collection, storage and sharing that is mission critical to all our clients. We monitor and alert on the following elements: * Overall health of our servers, applications and content delivery network. * Average, 95/99/99.9 percentiles response times of our requests for reading/writing consents. * Number of consents collected per property (compared to historical trends). The Didomi development team is distributed across different time zones to ensure reactivity in case of an incident. --- # 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.didomi.io/organization-and-account-settings/account-settings-and-support/service-level-agreement-sla-and-incident-management.md?ask=&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.