> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/legacy-products/proxy-builder/proxy-builder-cloud-dashboard/analytics-tab.md).

# Analytics Tab

Learn about the Analytics page on the Proxidize Cloud Dashboard.

{% hint style="info" %}
This feature is only available for Proxidize Business plan.
{% endhint %}

The Analytics page gives you real-time monitoring insight into all your proxies. You can sort though each host and endpoint individually to get an overview of its performance. You can also see performance over the last hour, last 24 hours, last 7 days and last 30 days.

Details include:

* Number of Hosts
* Number of Endpoints
* Host Uptime
* Endpoint Uptime
* RAM Usage
* CPU Usage
* Current Bandwidth
* Data Usage
* Average Download Speed
* Average Upload Speed
* Average Bandwidth Usage
* Endpoints Per Vendor
* Endpoints Per Status
* Endpoints Uptime Heatmap

![](/files/1d08635708e2038d66dc9c930456f2e50324db3a)


---

# 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://help.proxidize.com/legacy-products/proxy-builder/proxy-builder-cloud-dashboard/analytics-tab.md?ask=<question>&goal=<endgoal>
```

`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.