Traffic & 2× Billing
How traffic is measured, when the 2× surcharge applies, and how to estimate consumption.
How Traffic is Measured
Traffic is counted as the total bytes transferred through the proxy — both the request sent to the target server and the response received back. This is standard proxy billing and applies regardless of protocol (HTTP or SOCKS5).
Usage is synced from the network layer every 30 minutes. Your dashboard balance may lag slightly behind real-time consumption — build a safety buffer into your monitoring thresholds.
The 2× Surcharge
Precise geo-targeting (state, city, ZIP, ASN) narrows the available IP pool significantly. To compensate for the reduced pool size, these targeting levels consume traffic at 2× the normal rate: 1 GB of actual traffic deducts 2 GB from your quota.
| Targeting level | Residential | Mobile | Datacenter | Premium Residential |
|---|---|---|---|---|
Country only (cr) | 1× | 1× | 1× | 1× |
State (state) | 2× | 2× | 2× | 1× |
City (city) | 2× | 2× | 2× | 1× |
ZIP (zip) | 2× | 2× | 2× | 1× |
ASN (asn) | 2× | 2× | 2× | 1× |
The 2× rate is applied at the network level and cannot be toggled off. If you need city-level targeting without the surcharge, use Premium Residential.
Billing Examples
Example 1: Country-only (Residential, 10 GB quota)
You send requests through USERNAME__cr.us. Country targeting has no surcharge — 10 GB used, 0 GB remaining
Example 2: City targeting (Residential, 10 GB quota)
You send requests through USERNAME__cr.us;city.losangeles and transfer 4 GB of actual data. City targeting is 2×, so 8 GB is deducted — 2 GB remaining.
Example 3: City targeting (Premium Residential, 10 GB quota)
You send requests through USERNAME__cr.us;city.losangeles and transfer 4 GB. Premium Residential has no surcharge — 4 GB deducted, 6 GB remaining.
Save on city/state targeting
If your use case requires city or state precision, Premium Residential is often more cost-effective in practice despite the higher per-GB price, because it avoids the 2× surcharge entirely.
Monitoring Usage
Usage is visible in two places:
- Dashboard → Proxies — real-time usage bar per package
- GET /api/v1/packages/{id}/stats — programmatic access with daily/weekly/monthly breakdown
You will receive an email and in-app notification when your package reaches 90% usage. Configure notification preferences in Dashboard → Settings.