Billed per IP per day
Static Residential · Short-term
Short-term static residential IPs are bought by the unit and billed by the day, from $0.08 per IP per day. Once assigned, the address stops rotating — it stays yours until that broadband line goes offline on its own, and the bandwidth across it is unmetered. It fits work that needs a stable identity but not a stable month: bulk registration, survey panels, timed drops, short multi-account audits. Pull them over the API, connect with user:pass, or map them to local ports and paste the credentials straight into an anti-detect browser.
- Fixed for the session
- Unmetered bandwidth
- API, user:pass or port forward
- Scale by IP count
07
Specifications
- IP type
- Static residential (ISP)
- Lease length
- 1 hour – 24 hours
- Exclusivity
- 100% dedicated
- Protocols
- HTTP / HTTPS / SOCKS5
- Peak bandwidth
- Up to 50 Mbps
- Traffic cap
- Unlimited
- Fraud score
- Clean
04
Where it fits
Bulk registration and account warm-up
One IP per account, so sign-up, verification and first login all come from the same address instead of jumping cities mid-flow. Release the batch when the run ends and the meter stops.
Survey panels and market research
Panels invalidate responses that arrive from the same address, and datacenter ranges are filtered outright. Buy exactly the IP count a study needs and return them when it closes.
Timed drops and release checks
Sneaker drops, ticketing and limited releases live inside a few hours and need a block of steady residential exits — not a month-long commitment.
Short multi-account audits
Taking over someone else's store, auditing an ad account, running a one-off compliance pass — a few days of work. A short-term IP costs a fraction of a monthly one and leaves the long-term slots for accounts you keep.
Engineering detail
Technical detail
- Pick country, state and city at extraction time, or filter by ASN to choose a carrier, and mix cities inside one batch.
- Three ways in: generate a list in the console, automate extraction over the API, or map each IP onto a fixed local port.
- Billing is IP × day and a partial day counts as one — no minute-level proration to reconcile at month end.
- Bandwidth over each IP is unmetered, so what you move across it never changes the price.
- When a line retires, pull a replacement in the same city and the days you already paid for carry over to it.
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 long does a short-term static residential IP stay alive?
It lasts as long as the underlying broadband line stays online — usually somewhere between a few hours and a few days, and the console shows an expected lifetime before you pull it. Billing runs by the day. If an address drops early, pull a replacement in the same city; the days already paid for carry across rather than being lost.
How does per-IP-per-day proxy billing work?
Unit price × number of IPs × days held, starting at $0.08 per IP per day and dropping with volume. The clock starts when you pull an IP and stops when you release it, with any partial day counted as a full one. Every batch is itemised in the console at https://user.zapip.net and can be exported.
How do I connect — API, user:pass or port forwarding?
Three ways, and they work together on the same batch. The console generates an IP:port list you can paste into an anti-detect browser or a script. The API suits automated top-ups and rotation logic. Port forwarding maps a batch onto fixed local ports, which is usually the smallest change to existing code.
Static residential proxy vs rotating residential proxy — which do I need?
Rotating exits change every request or every few minutes, so a target cannot tie your requests together — that is what scraping needs. A static IP stays put so a platform can recognise you as the same user across logins, orders or submissions. If the goal is anonymity, rotate; if the goal is a consistent identity, stay static.
Get one request working. Scale after that.
Test before you commit, with an engineer on your integration.