Use cases
Some bugs only show up for traffic that does not come from your office or your CI runner. A few outside addresses let you reproduce them on purpose.
Your rate limiter, firewall rules and regional rules were written for traffic you seldom produce yourself. You test from a trusted network, everything passes, and the first real user from another region finds the edge case for you.
Allowlists set their own trap. A partner allowlists one address, your integration test works from one machine, and nobody notices until a deploy moves the job somewhere else.
Datacenter IPs are static for the term and you choose country, region and city, so a test always leaves from a known address. That makes them easy to allowlist, easy to find in your logs, and cheap enough to keep one per region in a test suite.
When you need to see how your service treats consumer traffic, for example fraud rules that score data centre ranges differently, an ISP IP gives you a static address registered to a consumer provider.
Residential has no country selection, because the pool picks the exit IP. When a job depends on location, the ISP and datacenter lines let you choose country, region and city.
Rate limits, regional content, allowlists and failover each call for different locations and a different number of IPs.
Read the host, port, username and password from environment variables, so the same test runs with and without the proxy. The real values are on the service page in the dashboard.
Record which address each test left from. When a result looks odd, that is the first thing you will want to know.
There is no shared gateway address to copy from this site. Each service shows its own host, port, username and password on its page in the dashboard.
Testing your own applications and infrastructure is on our acceptable-use list. Load testing, port scanning or probing for vulnerabilities on systems you do not own is an attack under the same policy, and it gets the account closed. If you test a client’s system, have their permission in writing.
Against your own systems, yes. Concurrency is not metered, so the limit is the number of IPs you rent and what your service can take. Warn your hosting provider first so their abuse team does not mistake it for an attack.
Yes. ISP and datacenter IPs do not rotate. Each one is yours for the term you rented it for.
No. One IP can serve staging and production checks alike. Add IPs when you need other locations, or when you want to see how your limits handle several sources at once.
Tell us the site and what you need from it. We will say which line fits and how much to start with, before you spend anything.