> For the complete documentation index, see [llms.txt](https://docs.stakingrewards.com/verified-provider-program/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakingrewards.com/verified-provider-program/verification-methodology/sr-rating/verification-criteria/reliability.md). # Reliability At Staking Rewards we only want to provide the highest quality to our users, and this also holds true for the Providers we verify. When it comes to Validators, reliability and performance is one of the most key metrics we look at when deciding whom to verify. Some of the key metrics and topics we look at are: * Historical average performance on validator operations * How the maintenance team is set up and supported * Whether there is an alerting system in place for fixing issues ASAP * Slashing history of the Provider’s staking services --- # 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.stakingrewards.com/verified-provider-program/verification-methodology/sr-rating/verification-criteria/reliability.md?ask=&goal= ``` `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.