Traffic and Plans
How traffic is consumed, what rollover means for unused traffic, where your current plan is shown, and how to read the usage numbers.
Last updated
Traffic is the currency of the service. Understanding how it is counted and where to watch it prevents the two common surprises: running out mid-run, and paying for traffic you did not use.
Where traffic is shown
| Location | What it shows |
|---|---|
| Top bar chip | Your available traffic, at a glance, on every dashboard page |
| Usage tab on a product | Period traffic and the successful requests chart for that product |
| Traffic usage card | Consumption against the plan, with the current plan name and an Upgrade action |
| Sub-user allocation | How much of the total is set aside per sub-user, covered in Traffic Allocation |
How traffic is counted
Traffic counts the bytes that pass through the proxy, both directions. That has one practical consequence worth internalising: page weight matters more than request count. Fetching a large image-heavy page costs many times what fetching a small JSON response costs, for the same single request.
If your usage is higher than expected, look for anything that fetches full pages when a structured endpoint would do, and anything downloading images you do not need.
Rollover
Unused traffic rolls into the next month rather than expiring at the end of the cycle. Two consequences:
- You do not need to size a package tightly to a calendar month.
- A quiet month is not wasted.
Rollover is why the available figure in the top bar can exceed the amount of your most recent purchase.
Current plan and upgrading
The Traffic usage card shows consumption against the plan total, the name of the current plan, and an Upgrade action. Upgrade takes you to the pricing for the next step up on that product.
When traffic runs out
When allocated traffic is exhausted, the product stops serving requests through its endpoints. Requests fail rather than being billed over a limit, so the symptom is failures, not a surprise charge.
The fix is to add traffic from the product's Add Traffic tab, described in Buy Traffic. If a product shows as inactive with a Buy pill in the sidebar, the traffic ran out or was never added.
Note
Pooled sub-user allocations are soft caps, not hard ones. A sub-user set to Pooled draws from the shared wallet, so a heavy sub-user can consume more than its nominal share until the wallet itself is empty. Traffic Allocation explains when that matters.