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

# Traffic Limit

Set the maximum traffic a proxy plan can use within a chosen period. Control spending and share plans without the risk of overuse.

#### How to set it up

1. Open your plan and go to **Resources → Manage Traffic Limit**.
2. Choose a **Period**: 1 hour, 24 hours, 7 days or 30 days.
3. Enter the **Traffic limit** in GB (whole numbers only).
4. Choose an **Action** for when the limit is reached:
   * **Email notification**: you get an email, and the plan keeps working.
   * **Suspend Usage**: the plan stops working until traffic becomes available again.
   * **Suspend Usage & Email Notification**: the plan stops working, and you get an email.
5. Click **Save Configuration**.

To remove the limit, click **Clear Configuration**.

#### How the period works: rolling window

The limit works on a rolling window, not a calendar. It never resets at a fixed time (like midnight or the 1st of the month). At any moment, we count your usage for the **last** 1 hour / 24 hours / 7 days / 30 days, starting from the current moment.

{% hint style="info" %}
Each GB you use comes back exactly one period after you used it.
{% endhint %}

**Example:** limit of 5 GB per 24 hours, with Suspend Usage.

| When                    | Used in the last 24 hours                  | Status                  |
| ----------------------- | ------------------------------------------ | ----------------------- |
| Mon 09:00, you use 2 GB | 2 GB                                       | Working, 3 GB left      |
| Mon 15:00, you use 3 GB | 5 GB                                       | Paused                  |
| Tue 09:00               | 3 GB (the 2 GB from Mon 09:00 dropped out) | Working, 2 GB available |
| Tue 15:00               | 0 GB                                       | Full 5 GB available     |

If you use your whole limit at once, the full limit comes back one period later.

**Why a rolling window:** with a calendar limit, you could use the full limit at 23:59 and again at 00:01. With a rolling window, you can never go over your limit in any period of that length.

#### When the limit is reached

* **Suspend Usage:** requests return the error `USER_RATE_LIMIT_EXCEEDED`. The plan starts working again on its own as traffic comes back. If you need access sooner, raise the limit or clear the configuration.
* **Email notification:** nothing stops. The email only tells you that the limit was reached.

#### Good to know

* The limit applies to one plan, not your whole account.
* Changes take effect within about 1 minute.
* The limit doesn't add traffic. If your plan balance runs out first, the plan stops anyway.


---

# 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.dataimpulse.com/traffic-limit.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.
