The three questions that actually decide survival
- Is the IP exclusively mine? Shared “static” IPs inherit every previous tenant's history. Ask explicitly whether the address is dedicated, and for how long you hold it.
- Is the range genuinely ISP-registered? Ask for the ASN and check it yourself. Relabelling a datacenter range as “ISP” is the most common misrepresentation in this market, and it is trivially verifiable.
- What is the history? Nobody sells you a written history, but a range that fails on first contact with your target had one. This is why testing a small amount before committing matters more than any spec sheet.
All three are answerable in about a minute with our IP check tool, which prints the autonomous system and its owner alongside header, timezone and WebRTC leak tests.
Type by workload, at this tier
| Workload | IP type | Non-negotiable |
|---|---|---|
| High-value long-lived identities | Dedicated static residential / ISP | Exclusive, verified ASN, one per identity |
| Strictest platforms | Dedicated mobile port | Rotation on demand, not on a timer |
| Session-based work at volume | Rotating residential, sticky | Session length you control |
| Anything with money attached | Never shared, never datacenter | — |
Why single-network suppliers are the real risk now
2026 made this concrete. When Google dismantled the IPIDEA ecosystem, every brand reselling that one upstream went down together — PIA S5, 922, LunaProxy, and IP2World itself. Users lost logins, issued proxies and prepaid balances in the same week, regardless of which logo they had bought from.
The lesson is not “pick a better brand”. It is that a supplier with one backend hands you its single point of failure. Working across several independent networks from one balance means a bad week on one pool is a dropdown change instead of a migration and a lost balance.
Profile hygiene, briefly
Nothing exotic, just the things that still catch experienced operators: timezone and language matched to the IP country per profile, sticky sessions on anything logged in, retired IPs never recycled onto new identities, and a written mapping of profile to address so a ban tells you what else is exposed. The browser-agnostic version lives in our antidetect proxy guide.