Practical guide
Plan your Static proxies workflow
Choose continuity when the same network identity matters across repeated actions.
Start with a reproducible sample
Test how the selected IP behaves through reconnects and the intended session duration.
- Define one target, a permitted task, and the settings that must remain fixed.
- Check the exit IP and location, then run the complete task in the intended client.
- Record valid results, errors, traffic, and timing. Change one setting at a time.
- Scale only after the sample meets your acceptance criteria and the traffic budget.
What makes the test meaningful
Record the exit IP at the start, after reconnecting, and at the end of the test.
Limits to account for
Static behaviour, exclusivity, and address lifetime are separate product terms. Confirm them before relying on an IP allowlist.
| Task | Starting configuration | Verify before scaling |
|---|---|---|
| Independent regional observations | Chosen country; rotation between samples | Exit-IP location, valid response content, and traffic per result |
| Login or another multi-step session | Continuous session; consistent browser profile | IP continuity, cookies, authentication, and account permissions |
Static proxies: questions before launch
What should I verify when testing Static proxies?
Record the exit IP at the start, after reconnecting, and at the end of the test.
Should I keep one IP or rotate it?
Use a continuous session for login and other multi-step tasks. Test rotation between independent requests. Verify the exit IP in your application; connection settings and a fixed address are different things.
Does a proxy guarantee access or a successful outcome?
Static behaviour, exclusivity, and address lifetime are separate product terms. Confirm them before relying on an IP allowlist.
Residential traffic pricing
Choose the plan that matches your workflows
The rate depends on traffic volume. Check the final amount and available payment methods in your dashboard before payment.
