> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/organizations/server-usage.md).

# Server usage

Go to a server's **Usage** tab for its traffic, CPU and memory over time.

## Choosing a window

Everything on the tab is drawn for the window you pick at the top. The presets are:

* **Last 24h** (the default), **Last 7 days**, **Last 30 days**, **Last year**
* **This billing cycle** and **Previous billing cycle**, where the server's contract makes them available

You can also pick a **custom date range** from the calendar. A range can't start before the server's service start date, and can't span more than twelve months.

Your choice is kept in the page address, so a particular view can be bookmarked or shared.

## What's on the tab

| Card                                    | Shows                                                                                  |
| --------------------------------------- | -------------------------------------------------------------------------------------- |
| **Monthly traffic**                     | Traffic used this month, against what the contract includes.                           |
| **Traffic graph**                       | The uplink graph for the window you've chosen.                                         |
| **Traffic alerts**                      | A summary of the [alerts](/organizations/server-traffic-alerts.md) set on this server. |
| **CPU right now** / **CPU usage**       | The latest CPU reading, and CPU over the window.                                       |
| **Memory right now** / **Memory usage** | The latest memory reading, and memory over the window.                                 |

Each graph carries a strip of figures beneath it — **Current**, **Minimum**, **Maximum** and **Average** for the window on screen. The *right now* cards name the time of the last reading, so you can tell a quiet server from a stale one.

## The 95th percentile is not your bill

{% hint style="warning" %}
The **95th percentile** printed on the traffic graph is **not the figure you're billed on.** Bills cover one billing month sampled in 5-minute averages. This graph is drawn from **daily** averages, so the peaks that the billing figure is calculated from disappear.

To see traffic over the same span your invoice covers, pick the **This billing cycle** or **Previous billing cycle** preset. The Console shows this warning under the graph whenever the graph is drawn at a resolution that can't reproduce the billed figure.
{% endhint %}

## Related topics

* [Traffic alerts](/organizations/server-traffic-alerts.md)
* [Server details](/organizations/server-details.md)
* [The Servers page](/organizations/servers-page.md)


---

# 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.i3d.net/organizations/server-usage.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.