Checking remaining traffic
Updated 2 min read
Residential and mobile proxies are coming soon and cannot be ordered yet. This article describes how their traffic is counted.
Traffic is counted per proxy. On Residential, read the Bandwidth column on the line's list. On any line, open a proxy and read Bandwidth used on its Capacity card. Residential and mobile traffic is billed per GB.
Why your logs differ from the meter
The figure is measured at the proxy, so it can differ from what your own logs and tools count, and a gap between the two is expected.
| Cause | Effect on your own count |
|---|---|
Retries |
Each retry uses traffic, even when your tool logs one request |
Compression |
The body your tool sees after decompressing is larger than what crossed the wire |
Failed and redirected requests |
Still use traffic |
A new connection for every request |
Uses more traffic than reusing connections |
A small, stable gap is normal. A large or growing one is worth investigating.
An invoice records what was paid for, not what was used. Usage is shown per proxy.
Using less traffic
- Request only what you need, and send
Accept-Encoding: gzipso responses arrive compressed. - Block images, fonts and video in headless browsers.
- Reuse connections.
- Stop retrying a request that keeps failing for the same reason.
Running low
A residential proxy sends one email when little of its traffic remains, and its page shows Nearly out. Requests stop when the allowance is spent. To add more, see Buying residential or mobile traffic (coming soon).
When the figure looks wrong
Write to support@proxyforge.io if usage keeps rising while every client is stopped, or does not move while they run. Include the proxy ID, the time you checked with your time zone, and the figures you saw. Leave out passwords.