80M+ residential IPs
A large global residential pool for continuous multi-region data work.
Geo-targeted residential proxy
80M+ residential IPs with country and region targeting
Route requests through an 80M+ residential IP pool covering 190+ countries and regions. Purchase does not lock a location; choose a country or region and SESSION when extracting proxies. This product is available only on traffic-based packages.
80M+ residential proxy IPs190+ countries and regionsCountry / region + SESSIONTraffic packages only
Geo-targeted residential proxyready
GEO + SESSION ROUTING123PROXY NETWORK
PRODUCT PROFILEResidential exits matched to each taskLocation and SESSION travel with authentication
READY
POOL80M+ residential IPs
COVERAGE190+ locations
TARGETINGCountry / region
BILLINGTraffic only
Client123ProxyTarget
80M+Residential proxy IPs
190+Countries and regions
SESSIONSticky residential routing
TrafficOnly purchase model
01 / Product capability
Make location and session explicit routing parameters
Use this product when public data tasks require residential network identity and a defined country or region. The residential gateway matches an exit from the requested location and maintains it according to SESSION.
190+ countries and regions
Organize collection jobs around the target markets and available locations.
Country or region targeting
Choose the target location when extracting proxies.
Specified SESSION
Keep the same residential exit for pagination and multi-step requests.
Residential network identity
Requests leave through residential network resources.
Traffic-only purchase
No concurrency-thread or unlimited-thread package is offered for this product.
02 / Traffic billing
Purchase residential routing only by transferred traffic
Choose country, region, and SESSION when extracting proxies. These routing options do not change billing, and all transferred proxy data is counted against the traffic package.
Pay by transferred GB
There is no concurrency package, unlimited-thread package, or port-based purchase model for this product.
GBThe only capacity unit
View residential pricing
- Purchase model
- Transferred traffic
- Location
- Country / region
- Session
- Specified SESSION
- Resources
- 80M+ / 190+ locations
Planning note
Estimate packages from real response size
Measure representative successful responses, then combine average bytes, request count, and retry rate. Avoid loading large assets that the data task does not need.
03 / Workloads
For tasks that need location-aware residential identity
The core value is controlled residential geography and session continuity, not globally random rotation.
Regional public data research
Compare public search, trend, and localized content across countries or regions.
Ecommerce market collection
Collect public product, price, stock, and review data with SESSION for pagination.
Geographic diversity for AI data
Organize public data acquisition across multiple markets and languages.
04 / How it works
Put location and SESSION into proxy authentication
The application keeps a standard proxy configuration while the gateway handles residential matching and session routing.
01
Choose a location at extraction
Purchase does not lock a location; select the country or region required by the task.
02
Assign a SESSION
Use a stable identifier for pagination or multi-step workflows.
03
Connect to the gateway
Send requests through the assigned residential endpoint.
04
Monitor traffic and results
Track success rate, response size, retries, and package consumption by location.
Proxy service architecture123Proxy network
ApplicationCLIENT
AuthenticationAUTH
123ProxyROUTE
Public targetRESPONSE
Pool80M+
Coverage190+ locations
BillingTraffic only
05 / Specifications
Product boundaries and technical facts
Available locations, inventory, bandwidth, and package options are subject to the current console and pricing page.
- Proxy type
- Dynamic residential proxy
- Pool size
- 80M+ global residential proxy IPs
- Coverage
- 190+ countries and regions
- Location
- Country or region selected when extracting proxies
- Session
- Specified SESSION support
- Billing
- Transferred traffic only
- Protocols
- HTTP(S) / SOCKS
06 / Developer access
Keep geo and SESSION close to the job definition
Use standard proxy configuration and encode the target country or region and SESSION in the assigned authentication format. Record traffic, retries, and result quality by location.
Standard HTTP proxy configurationExplicit timeout and retry policyProduction monitoring by workload
Python
import requests
proxy = "http://customer_US_SESSIONID:YOUR_PASSWORD@residential.123proxy.cn:33000"
proxies = {"http": proxy, "https": proxy}
response = requests.get(
"https://target.example/data",
proxies=proxies,
timeout=20,
)
print(response.status_code)07 / FAQ
Questions to answer before production
Validate the product boundary, package model, target behavior, and capacity with representative requests.
Which purchase models are available?
Only traffic-based packages are available. There is no concurrent-thread or port-based unlimited plan.
Can I target a country or region?
Yes. Submit the supported location parameter in proxy authentication.
What does SESSION do?
SESSION attempts to keep the same residential exit for consecutive requests until the session expires or the exit becomes unavailable.
Can I target a city or state?
This page commits only to country or region targeting. Use the locations currently available in the console.
How is this different from Scraping Rotating Proxy?
Scraping Rotating Proxy uses mixed or pure-residential pools with broad region presets. Residential Rotating Proxy supports country or region targeting and SESSION, but is purchased only by traffic.
Validate the target locations with real URLs
Test residential matching, success rate, response size, and SESSION behavior before production rollout.