> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tenderly.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Track Usage and Tenderly Units (TUs)

> See this month's Simulations, Monitoring, and Node RPC usage by project, network, and method, and find which resources drive your TU consumption.

The **Usage** page shows how much of each product the organization has used in the current calendar month, against the plan's monthly limit. Break usage down by project, product, Node RPC or Virtual Environment, network, and method to find what drives it.

## Open the Usage page

* In the [organization](/platform/account/organizations/overview) sidebar, click **Usage**. The link is shown to members with the **Manage billing** [permission](/platform/account/organizations/members#member-permissions).
* On the [Billing](/platform/account/billing/overview) page, click **View usage** on a usage row to open the page filtered to that product.
* From a Node RPC, click **Usage** in its sidebar or **Manage usage** on its Overview.

![Usage page with the Simulations category, broken down by project and product](https://mintcdn.com/tenderly/0H08brDMB_q5N4Dm/images/account/usage-simulations.webp?fit=max\&auto=format\&n=0H08brDMB_q5N4Dm\&q=85\&s=e0db10feed9da6242b952f850dcea045)

## What each category measures

Pick a **Category** in the **View configuration** panel. Each one has its own unit and monthly limit:

| Category | Products | Measures |
| - | - | - |
| **Simulations** | **Virtual Environments**, **Simulation API** | **Total Requests** (requests to Virtual Environment RPCs and Simulation API calls) or **RPS** |
| **Monitoring** | **Alerts**, **Web3 Actions** | **Total Scanned Txs** (transactions scanned by alerts and Web3 Actions) or **Scanned Tx/s** |
| **Node** | [Node RPC](/node-rpc/overview) | **Total TU** ([Tenderly Units](/node-rpc/pricing) consumed) or **TU/s** |

Node RPC usage is measured in Tenderly Units: every JSON-RPC method has a fixed TU cost, listed in the [TU cost table](/node-rpc/pricing#tu-cost-per-request). Requests rejected with HTTP 403 or 429 consume no TUs.

## Read the header

* The title shows the period, from the first day of the month to today, for example **Usage (1 Oct - 16 Oct)**. Node shows **TU Usage**.
* The large number is the usage so far against the monthly limit, with the percentage used. It turns red when usage passes the limit.
* **429 occurrences** counts the requests rejected for exceeding a rate limit over the last month.

## Filter and break down usage

**Filter** opens and closes the **View configuration** panel:

* **Category** and **Product** choose what to measure.
* **Measure** switches between totals and the per-second rate.
* **Breakdown** splits usage into series by **Project**, **Product Type**, **RPC**, **Network**, or **Method**. The default breakdown is Project, Product Type, and RPC.
* **Filter by** narrows to specific projects, RPCs, networks, or methods. **Clear all** removes the filters.

Above the chart:

* **Cumulative** turns the chart into a running total for the month, with the monthly limit drawn as a dashed line. It isn't available for per-second measures.
* **Chart type** switches between **Line** and **Stacked Line**.
* All times are in UTC.

The chart draws the top 10 series. The table below it lists every series with its total for the month and one column per day; RPC names link to the Node RPC or Virtual Environment. Clear a row's checkbox to hide that series from the chart.

## Find what drives usage

| Question | Set |
| - | - |
| Which project uses the most? | **Breakdown**: Project |
| Which Node RPC or Virtual Environment? | **Breakdown**: RPC |
| Which network? | **Breakdown**: Network |
| Which JSON-RPC method? | **Category**: Node or Simulations, **Breakdown**: Method |
| When did per-second usage peak? | **Measure**: TU/s, RPS, or Scanned Tx/s; the table shows the peak |

For request-level detail on a single Node RPC, including failed and rate-limited calls by status code, see [Monitor Node RPC usage, errors, and rate limits](/node-rpc/usage-and-errors).

## Usage warnings

When usage passes 80% of a monthly limit, project pages show a banner with the percentage used and links to **View usage** and **Contact us**. When a Node RPC has been rate-limited in the last 24 hours, the banner shows how many times. To raise a limit, [contact our sales team](https://tenderly.co/contact-us). What happens at the limit depends on the plan; see [Usage limits, rate limits, and write limits](/platform/account/billing/limits).

## Organizations on legacy billing

Organizations on the earlier billing model see **TU Usage** in the sidebar. The page works the same way, with every product measured in Tenderly Units:

* **Product**: **Virtual Environments**, **Node**, or **Simulation**.
* **Measure**: **Total TU** or **TU/s**.
* The header shows the TUs used this month against the monthly TU limit, and **429 occurrences**.

![Legacy TU Usage page broken down by project, product, and RPC](https://mintcdn.com/tenderly/0H08brDMB_q5N4Dm/images/account/tu-usage-legacy.webp?fit=max\&auto=format\&n=0H08brDMB_q5N4Dm\&q=85\&s=9a1bb10bb8cb9e1c35cc1384c8f5f204)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.