Billed per GB
Rotating Residential · Traffic
Rotating residential proxies billed by the gigabyte, from $0.8/GB, exiting through 90M+ real home-broadband addresses. Rotate on every request, set an interval anywhere from 1 to 360 minutes, or hold one exit in a sticky session for up to 90 minutes. It suits work that arrives in batches — scraping runs, ad checks, SERP pulls — where usage spikes and then goes quiet, and whatever you do not use stays on the balance. Targeting resolves to city, state or ASN across 195 countries and regions.
- 90M+ global pool
- 120-min sticky sessions
- City & ASN targeting
- Traffic never expires
07
Specifications
- IP type
- Rotating residential (P2P)
- Pool size
- 90M+ IPs
- Protocols
- HTTP / HTTPS / SOCKS5
- Rotation
- Per request, or sticky up to 90 minutes
- Authentication
- User:pass / IP allowlist
- Avg response
- < 0.6s
- Success rate
- 99.9%
04
Where it fits
Marketplace price and stock scraping
Prices and availability differ by locale, so the request has to leave from the country you are pricing. Rotating on each request keeps one address from collecting rate limits across tens of thousands of pages.
Ad verification
Open the landing page from a real broadband exit in the city you bought, then check that the creative, the redirect chain and the geo-targeting match what was sold. You pay for the bytes and nothing else.
SERP and rank tracking
Search results are personalised by the requesting IP and its history. A fresh exit per query returns the ranking a real user in that market sees, not one shaped by your own crawler's footprint.
Short bursts that spike and stop
Flash-sale checks, a one-off backfill, a client asking for data by Friday. Traffic sits on the balance until you need it, so the quiet weeks cost nothing.
Engineering detail
Technical detail
- Rotation intervals are set per channel in the console, from 1 to 360 minutes, without touching crawler code.
- One account can run both modes at once — a 90-minute sticky session for anything logged in, per-request rotation for pagination.
- Targeting resolves to city, state and ASN, and separate jobs can exit through different countries in parallel.
- Usage breaks down by sub-account and channel, so a runaway job shows up in the console long before it shows up on the invoice.
- Reputation is checked continuously and flagged exits leave the pool automatically, holding request success at 99.9%.
Coverage
One network behind all four products — changing the billing model does not change how you connect or how you target.
All 33 markets- 195 countries & regions
- Available
- All 50 US states
- Available
- City-level targeting
- Precise
- ISP & ASN targeting
- Supported
FAQ
Questions about this product
How is a pay-per-GB residential proxy actually billed?
You are billed for the bytes that pass through the proxy — request and response, headers included. $0.8/GB is the entry rate and the unit price drops as volume grows, with consumption itemised by sub-account and channel in the console at https://user.zapip.net. Nothing expires, so an unused balance carries into the next month.
What rotation interval should I use for web scraping?
It depends on whether the target tracks a session. Stateless pagination is simplest with per-request rotation. Anything that logs in, adds to a cart or walks a multi-step form should hold a sticky session long enough to finish, up to 90 minutes. In between, a fixed interval somewhere in the 1–360 minute range — ten minutes is a common starting point — trades success rate against IP churn.
Rotating residential or unlimited bandwidth for large-scale scraping?
Choose by shape, not by size. Batch work that runs and then goes quiet fits the per-GB plan, because idle time is free. A pipeline that runs continuously at steady throughput fits the bandwidth plan, where you buy Mbps and the bytes are not metered. Roughly a terabyte a month is where the two cross over.
Does unused residential proxy traffic expire?
No. A traffic balance stays on the account until you use it — there is no 30-day reset and no expiry clock. Plans do not draw from each other either, so running a bandwidth plan alongside leaves the gigabytes untouched.
Get one request working. Scale after that.
Test before you commit, with an engineer on your integration.