📈 Traffic & Usage
Understanding how traffic is counted and managed helps you plan your usage and avoid unexpected interruptions.
How Traffic Is Counted
Traffic is measured in gigabytes (GB) and covers data transferred through the proxy — both inbound (responses from target sites) and outbound (your requests). The dominant component is typically the response size.
What consumes traffic:
- HTTP response bodies (HTML, JSON, images, etc.)
- HTTPS tunnel overhead
- Request headers
Traffic Validity & Extension
Traffic purchased on X2Proxy is valid for 90 days from the date of purchase.
After 90 days, any unused traffic is placed on pause — it is not lost. Your remaining balance is preserved and reactivated automatically with any new purchase, even the minimum available package. There is no minimum spend required to extend your balance — buying any traffic package reactivates your paused balance along with the new purchase.
Traffic purchased in separate orders each has its own 90-day clock, but all balances are reactivated together on any new purchase.
Usage Statistics
The Statistics section provides detailed analytics:
- Requests per day and per hour
- GB consumed per day
- Breakdown by country (if targeting is used)
- Protocol breakdown (HTTP vs. SOCKS5)
Statistics are available both at the main account level and inside each pool separately — useful for tracking usage by pool type or by sub-account.
Traffic Optimization Tips
- Avoid downloading large assets — for scraping tasks, skip images, videos, and large JavaScript bundles by filtering content types or using request interception in headless browsers.
- Cache responses — if re-visiting the same URLs, cache locally to avoid redundant proxy requests.
- Use targeted requests — request only the specific pages or API endpoints you need, rather than crawling entire sites.
- Compress responses — request gzip-encoded responses where the target server supports it to reduce transferred data volume.
Next: FAQ & Troubleshooting