> For the complete documentation index, see [llms.txt](https://docs.iproyal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iproyal.com/proxies/residential/dashboard/statistics.md).

# Statistics

In the 'Statistics' section of your Residential Proxies dashboard, you have the ability to monitor and analyze your proxy usage over time. This interactive graph, outlined by the orange dotted border in the image, provides a visual representation of your proxy traffic, which you can further adjust by selecting a specific time period. This can help you understand peak usage times or identify trends. Additionally, you have the option to filter the data by specific websites and choose the units of measurement (such as MB or GB).

For a more detailed review or record-keeping purposes, you can download the report by clicking the 'Download report' button. This tool is essential for managing your proxies effectively and ensuring that your usage aligns with your needs and expectations.

<figure><img src="https://22873178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4Y3jlvZjKrqTSLg2hBbJ%2Fuploads%2FRlGnidMTt5PnZsJ7odk5%2FA1.png?alt=media&amp;token=1a6a47c5-c1bd-40a6-8a4d-8477e17cf1af" alt=""><figcaption></figcaption></figure>


---

# 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.iproyal.com/proxies/residential/dashboard/statistics.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.