What this US page solves
Once the target market is the United States, the next step is usually not another product brochure—it is two decisions:
- Pick product class by task: public-side sampling / monitoring / localization, or authorized store long-lived identity
- Confirm in the console that US exits are orderable (cities and stock always follow the backend)
This is the US country landing under Locations: map “US × rotating/static” to on-site products and scenes—not a city inventory table. Still need the class frame? Rotating vs static residential. Sister markets: Japan · Singapore · United Kingdom. Hub: Locations.
Lawful, authorized commercial and technical use only. US scenes mean authorized business and self-checks on publicly reachable paths—not unauthorized access or bypassing platform rules. Not supported for use in mainland China.
How to split the US market: rotating by GB vs static by IP
Rotating residential (per GB)
Fit when you need rotatable, US-selectable, usage-flexible exits: public data sampling, price monitoring, ad creative / landing self-checks, localization short-flow previews, etc. Entry: Rotating.
Billing per GB: about $0.40/GB; 100 TB full bundle about $0.20/GB (full bundle only; not split; 1 TB = 1,000 GB). Math: Billing GB vs IP. Console wins on price.
One short flow (finish checkout or a landing once) can use a sticky session—same exit briefly; sticky ≠ monthly static. Params: console. Detail: Sticky vs static.
Static residential (per IP / month)
Fit when you need a relatively fixed exit for the term: authorized US-market store backends, persistent environments that need consistent network identity. Entry: Static.
Billing per IP / month: shared about $1.50, dedicated about $5 (USD). Boundary: Shared vs dedicated static. Store map: Ecommerce. Console wins on price.
Do not force rotating GB into long login identity, and do not force static monthly rent into “many URLs / many public page samples”—bill unit and exit behavior both mismatch.
One table: US-side task mapping
Choose by task
| Task | Prefer | Why | ZTProxy |
|---|---|---|---|
| Public multi-URL / multi-page sampling, price monitoring | Rotating + US geo | Traffic + rotatable exits, not monthly identity | Rotating; Price monitoring |
| One checkout / landing / short-flow preview | Rotating + short sticky | Same exit briefly; clearer path judgment | Rotating; Sticky vs static; Ad verification; Localization |
| Authorized US store backend; long fixed identity | Static (shared or dedicated) | Relatively fixed exit for the term | Static; Ecommerce; Shared vs dedicated |
| Unsure rotating vs static class | Selection guide | Align task and bill unit first | Rotating vs static |
Console wins; no platform-review or conversion promises.
Rotating vs static (US context)
| Dimension | Rotating residential | Static residential |
|---|---|---|
| What you buy | Rotatable / US-selectable residential exits + traffic | Relatively fixed US exit for the term |
| Billing | Per GB (~$0.40/GB; bundles on pricing) | Per IP / month (shared ~$1.50; dedicated ~$5) |
| Typical use | Monitoring, ad self-check, localization spot checks | Authorized stores, persistent environments |
| Entry | Rotating | Static |
| Common miss | Rotating for long login; sticky as monthly fixed | Static monthly for multi-page public sampling |
How to read region and inventory
Locations is the browse entry; whether US is orderable, and city/resource detail, always follow console/backend. This page invents no city counts, coverage %, or availability SLA. Smoke-test with small traffic or a short term before scale.
If the business target is Japan / Singapore / UK instead of the US, switch to: Japan · Singapore · United Kingdom.
How to read price
- Rotating: about $0.40/GB; 100 TB full bundle about $0.20/GB (not split)
- Static: shared about $1.50 /IP/month; dedicated about $5 /IP/month
- Currency USD; self-serve list may follow reseller settings—orders and bills follow console + Pricing
- Effective-cost mindset: Billing GB vs IP
- Payment context: USDT/USDC available; Visa/Mastercard applying / pending
Pre-order checklist
- Public-side sampling, or authorized store long identity? → match the table
- Target market confirmed US? Console geo / order page shows matching resource?
- Short sticky or rotate? (sticky params: console)
- Bill by GB or IP×month? Check Pricing
- Protocol / client fields: Docs EN quickstart; checklist HTTP / SOCKS5
- Lawful, authorized use? Avoid mainland China use restriction?
FAQ
For US business, rotating or static?
By task. Public monitoring, ad self-check, localization sampling → prefer Rotating. Authorized store long identity → prefer Static. Frame: Rotating vs static.
Who wins on US inventory and city coverage?
Console / backend. This page has no city list or stock numbers; the Locations hub is browse-only.
How is US rotating residential billed?
Per GB; on-site about $0.40/GB (bundles on pricing). USD; console + pricing page win.
Shared vs dedicated static for the US?
Isolation and stability expectations: shared about $1.50, dedicated about $5 /IP/month. Deep-dive: Shared vs dedicated.
How to set up US localization or ad verification?
Both usually use rotating + US geo; sticky for one short flow, rotate for multi-page / multi-sample. See Localization and Ad verification.
Can sticky session act as a US static IP?
No. Sticky keeps the same exit briefly; static is monthly fixed identity. Sticky vs static.
How does this differ from JP / SG / UK pages?
Same skeleton (task → product); different target market. JP leans Japanese/JPY localization pointers; SG/UK follow the same country-landing pattern. Compare: Japan · Singapore · United Kingdom.
Mainland China? Who wins on price?
All proxy services on this site are not supported for use in mainland China. Published prices are USD; orders and bills follow console + Pricing.
Next steps
- Use the task table: rotating or static
- Open Rotating or Static; confirm US exits in console
- Check Pricing; connect via Docs EN quickstart
- Scene deep-reads: Ecommerce · Localization · Price monitoring · Ad verification
- Other markets: Locations · Japan · Singapore · United Kingdom
Need help: [email protected] or on-site support (no invented response SLA).