package-premium instead of package-standard.
At a glance
What makes premium IPs different
Most blocks and CAPTCHAs are triggered by IP reputation, not by what you actually do. Standard residential IPs come from a much larger, less filtered pool. Premium IPs are selected for their history:- Clean histories. IPs haven’t been flagged, recycled across thousands of users, or associated with abusive traffic.
- No proxy-detection history. Each IP is screened to make sure it has never been detected as a proxy by major fingerprinting databases.
- Continuous monitoring. We monitor IP reputation against third-party blacklists and our own detection signals. IPs that show signs of degraded trust are rotated out of the pool and replaced.
When to use premium
Switch a workload from residential to premium when you see:- Elevated CAPTCHA rates on a target, even with realistic request pacing.
- Frequent blocks or inconsistent success across sessions.
- High-stakes flows — e-commerce checkouts, social platforms, and travel sites — where a failed request costs more than the difference in bandwidth price.
Connecting
Rotating (no session)
Every request gets a new premium IP:Sticky sessions
Hold the same premium IP across requests for a number of minutes. This example keeps a UK IP for 20 minutes:SOCKS5
Full parameter reference
Premium residential supports the same parameters as residential:
Username format:
Limits
Next steps
Residential proxies
The full parameter reference, and the lower-cost option for most targets.
CAPTCHA & block rates
How to improve success rates on difficult targets.
Authentication
Credentials, protocols, and output formats.
Generate proxies with the API
Create premium proxy lines programmatically.
