> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/the-portal-explained/support/service-level-report.md).
# Service level report
Is our service up to standards
The Service reports page provides in an overview of the availability of our service per month.
1. Click on **SLA Reports** in the menu for an overview of the availability of our services
2. Click on the **calendar** icon to choose another month to see report history
3. Click on the **info** icon for a brief explanation of the key performance indicator (KPI)
4. Click on a specific service for more report details on performance history
5. Shows the service level of a specific service for the selected month
{% hint style="info" %}
Do you have a Modular or Tailored subscription? See your Service Level Agreement for the agreed availability.
{% endhint %}
Service Reports
## Report details
The **report details** show more report details on performance history.
1. Choose a **from** date and **to** date to present the graphs for a certain period
2. The KPI **Value** is the measurement of an availability for the specific month
3. The KPI **Norm** is the standard we strive for and use as minimum availability standard
4. Click **SLA Report overview** to go back to the Service reports page
Report details
---
# 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.kpnthings.com/kpn-things/the-portal-explained/support/service-level-report.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.
