Unmetered traffic
Transferred GB is not accumulated within the active port package.
Unlimited residential ports
Unlimited traffic and concurrency on every residential port
Each port includes unmetered traffic and no concurrent-thread limit. Residential exits rotate on a fixed 3–30 minute cycle. Region selection applies to the package and cannot be configured separately for every port.
Unmetered traffic per portUnlimited concurrency per portFixed 3–30 minute rotationRegion set at package level
Unlimited residential portsready
PORT-BASED RESIDENTIAL123PROXY NETWORK
PRODUCT PROFILEPersistent residential capacity by portPackage policy controls location and rotation
READY
PORTUnmetered traffic
CONCURRENCYUnlimited per port
ROTATIONFixed 3–30 min
REGIONPackage-level
Client123ProxyTarget
UnmeteredNo per-GB billing
UnlimitedConcurrency per port
3–30 minFixed exit rotation
Package-levelShared region setting
01 / Product capability
Port-level unlimited use, package-level routing policy
Each port carries a workload without GB or thread metering. Bandwidth remains the throughput boundary, while all ports in the package share the selected region and fixed rotation cycle.
Unlimited concurrency per port
The service does not cap in-flight request threads on each port.
5–100Mbps options
Choose sustained bandwidth according to workers and completion targets.
Fixed 3–30 minute rotation
Every port rotates its residential exit on the selected fixed cycle.
Region selected at extraction
All ports share the package location selected when extracting proxies.
Port-based workload isolation
Assign ports to projects or worker nodes while keeping package policy consistent.
02 / Plans & capacity
Allocate ports by worker, then select sustained bandwidth
Standard packages are purchased by port and period. Count simultaneously active workers, then measure real peak throughput to choose port quantity and bandwidth.
Purchase by port and period
Traffic GB and in-flight threads are not metered. Region and rotation cycle remain package-level controls.
PORTUnmetered traffic and unlimited concurrency
View port pricing
- Purchase unit
- Ports / service period
- Bandwidth
- 5–100Mbps
- Rotation
- Fixed 3–30 minutes
- Region control
- Package-level
Planning note
Unlimited use does not mean unlimited throughput
Port bandwidth, target response time, retries, client performance, and page resource volume still determine completed work.
03 / Workloads
For always-on residential and bandwidth-heavy tasks
Port packages are easier to budget when workers stay online, response bodies are large, or browser sessions generate sustained traffic.
Browser automation workers
Assign a residential port to each long-running browser worker.
Long-term regional monitoring
Collect public regional pages without accounting for every transferred GB.
Large-response public data
Use predictable port costs for pages and assets with larger response bodies.
04 / How it works
Ports carry tasks while residential exits rotate
Purchase the package without selecting a region. Choose one package region and a fixed rotation cycle when extracting proxies, then assign ports to workers.
01
Set region at extraction
Choose one supported region for all ports in the package when extracting proxies.
02
Choose a rotation cycle
Select a fixed value between 3 and 30 minutes.
03
Assign task ports
Map ports to projects or workers; each port has unlimited concurrency.
04
Monitor bandwidth
Add ports or bandwidth when sustained utilization approaches the package limit.
Proxy service architecture123Proxy network
ApplicationCLIENT
AuthenticationAUTH
123ProxyROUTE
Public targetRESPONSE
Per portUnmetered / unlimited threads
RotationFixed 3–30 min
RegionPackage-level
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
- Rotating residential proxy ports
- Billing
- Port and service period; unmetered traffic
- Concurrency
- Unlimited concurrent threads per port
- Bandwidth
- 5–100Mbps package options
- Region
- Package-level; not configurable separately per port
- Rotation
- Fixed 3–30 minute exit rotation
- Protocols
- HTTP(S) / SOCKS
06 / Developer access
Bind each worker to a clearly owned proxy port
Use standard HTTP(S) or SOCKS proxy configuration. Track the assigned port, package region, rotation cycle, and bandwidth utilization for every production worker.
Standard HTTP proxy configurationExplicit timeout and retry policyProduction monitoring by workload
Python
import requests
proxy = "http://customer-port-08:YOUR_PASSWORD@unlimit.residential.123proxy.cn:10253"
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.
Does unmetered traffic also mean unlimited bandwidth?
No. Traffic is not billed by GB, but every port has a selected bandwidth specification.
How often does the IP rotate?
Each port rotates on the fixed package cycle selected between 3 and 30 minutes.
Is concurrency limited per port?
No. Each port has unlimited concurrent threads, although bandwidth and target response still limit throughput.
Can every port use a different region?
No. Purchase does not lock a region. The region selected when extracting proxies is shared by all ports in that package.
Is it suitable for browser automation?
Yes. Unlimited concurrency per port fits browsers that load HTML, images, CSS, JavaScript, fonts, and APIs in parallel.
Turn long-running residential traffic into predictable port cost
Estimate active workers, target region, rotation cycle, peak bandwidth, and service period before purchasing.