Account management
Accounts you own or are contracted to run, reached from an address that does not change between sessions. The most common job in this category and the one with the most conditions attached.
Most proxy work is one of two shapes: go wide and be forgotten, or come back and be recognised. These five jobs are the second shape, and each of them depends on an address that stays the same from one session to the next.
Every scenario below is open by default. A short list of targets needs a verification step first, and each page says plainly whether it is on that list.
In short: All five scenarios run on one static ISP address — a single IP registered to a named internet provider, kept for the period you pay for and used by nobody else while you hold it. What differs is why the address must not change and whether our Acceptable Use Policy attaches a condition; the table further down sets the five side by side.
A static address is the opposite of a rotating pool, which hands out a new address per request or per short window, and unlike a datacenter address it is registered to an internet provider rather than a hosting company. Address blocks are handed out through the five regional internet registries (IANA’s number resources page lists them), and who holds each block is public record, so a target can check the registration for itself.
These five were chosen because in each of them the address staying the same decides the outcome. The scenario pages draw on how the address types behave and on our published policies, not on measurements of any platform; the editorial policy says how figures are sourced.
Accounts you own or are contracted to run, reached from an address that does not change between sessions. The most common job in this category and the one with the most conditions attached.
Seeing your own site, prices and availability the way a visitor in another country sees them — repeatedly, from the same vantage point, so a difference between two runs means something changed.
Long sessions that must survive on one address. A connection that moves mid-session reads as an account being handed around, which is the one thing these platforms are watching for.
Checking that a campaign shows what it was booked to show, from the market it was booked in, without the ad system recognising you as the advertiser.
Working from the checking side rather than the evading one: reproducing what a signup or a transaction looked like, and understanding what the network behind it actually says.
Whether a fixed address fits work they already do, rather than a rotating pool or a datacenter address.
Why the address must not change in that job, and whether our Acceptable Use Policy attaches a condition to it.
| Why the address must not change | What the job needs from it | Condition under the policy | |
|---|---|---|---|
| Account management | A platform compares each sign-in with the account's history | One address per account, kept at renewal | Evidence of authority over accounts you do not personally own (§2) |
| Region testing | Two runs compare only from the same vantage point | One address per market, from 73 countries | None: named as needing no prior review (§2) |
| Gaming and streaming | A connection open for hours breaks when the address moves | One address for the whole session, over HTTP or SOCKS5 | None to start; bypassing geo-blocking or licensing rules is prohibited (§5) |
| Ad verification | This week's check is only useful next to last week's | An internet provider's network in the market that was bought | None: named as needing no prior review (§2) |
| Fraud prevention | A rule change should be the only variable in a test | A known registration to check lookups against | None for your own rules; written authorisation to test systems you do not own (§2) |
Because these are the ones where a fixed address registered to an internet provider is the deciding factor rather than a nice-to-have. Broad crawling, wide data collection and market-scale scraping are real jobs, but they are better served by a rotating pool, and pretending otherwise would sell you the wrong product. We would rather name five things we are right for than twelve we are merely adequate at. Rotating Residential
No. Ordering, connecting and running the service is open by default, and our acceptable use policy names ad verification, anti-fraud monitoring and testing by region as needing no prior review. Verification attaches to targets, not scenarios: accounts on third-party platforms you do not personally own, security testing against systems you do not own, collecting personal data, and targets in financial services, healthcare or government. Verification is a written confirmation, not a queue. Acceptable Use Policy
Technically yes, and it is usually a bad idea. Reputation is per address, so mixing an account you cannot afford to lose with exploratory work on the same IP means one job's mistake becomes the other job's problem. Separate the work that matters from the work that experiments.
You ask and we replace it, free, up to 20 % of your order per calendar month. The grounds are an address that stops responding, one that starts resolving to a different country, or one blocked on a target you told us about. For a product you paid a month ahead for, what happens on day three is a term worth reading before you buy, not after. Terms of Service