Why are plans split into ‘port-based’ and ‘bandwidth-based’? What’s the difference?

Port-based: ports are the primary resource unit. Best for running many workflows in parallel and for isolating traffic by task/account/customer for cleaner scheduling and troubleshooting.

What use cases are a port-based unlimited dynamic proxy plan best for?

High parallelism workloads: SERP monitoring, cross-site price checks, inventory polling, ad landing-page verification, and multi-region availability checks. Clear isolation: separate different business lines/scripts/clients by port to reduce interference and simplify tracking and incident triage.

What use cases are a bandwidth-based unlimited dynamic proxy plan best for?

Throughput-driven pipelines: content collection, image/resource downloads, long-running sync jobs, and batch processing.

Does ‘unlimited’ mean there are no restrictions at all?

Unlimited does not mean uncapped: common constraints include concurrent connections, per-connection speed, node capacity, short-term burst limits, and fair-use policies.

How can I quickly decide whether to buy port-based or bandwidth-based?

Quantify your needs first: number of parallel workflows, average response size per request, peak request rate, and acceptable latency. Validate with a small stress test: track success rate, latency, retry rate, and whether throughput saturates—or if queues form due to concurrency or speed limits.

Unlimited Dynamic Traffic Bandwidth Plan

Bandwidth tiers for steady throughput. Unlimited traffic with auto IP rotation and geo-targeting.

Bandwidth Ports

Customize 400+ Mbps bandwidth

$????

Get discounted pricing

Contact your account manager

We accept the following payment methods.：

Note: Due to differences in local regulations and network conditions, access or order placement may not work properly in some regions. We recommend using an international network environment.

See What Customers Are Saying

In cross-border eCommerce scraping, exit-IP drift caused constant verification and blocks. After moving to static IPs, egress stayed consistent, sessions stabilized, and retries dropped. With paced requests, our connection success rate improved materially fast.

Alex Walker

Across multiple ad accounts, rotating exits repeatedly triggered ‘abnormal login’ warnings and forced rechecks. Using fixed static IPs, risk alerts fell, logins stayed clean, and campaign delivery schedules became predictable again for our team.

Michael Carter

With staff spread across cities and stores, shared access often tripped security prompts when IPs changed. Keeping a consistent pool of static IPs made backend checks uniform, reduced challenges, and streamlined operations for everyone.

Emily Johnson

For price monitoring, sites are sensitive to bursty, frequent requests and quickly raise defenses. Pairing static IPs with time-sliced crawling produced steadier traffic, fewer alerts, and more complete datasets without sacrificing coverage over time.

Sophia Reed

Our platform requires a fixed egress IP for allowlisted access. After adopting static IPs, we stopped updating allowlists every week. Ops workload dropped, audits became simpler, and we rolled out role-based access with confidence.

Daniel Brooks

For multilingual localization testing, long-term regional consistency matters more than raw speed. With fixed static IPs, we could reproduce results across runs, isolate location issues faster, and resolve bugs without guessing the endpoint anymore.

Natalie Parker

In cross-border eCommerce scraping, exit-IP drift caused constant verification and blocks. After moving to static IPs, egress stayed consistent, sessions stabilized, and retries dropped. With paced requests, our connection success rate improved materially fast.

Alex Walker

Across multiple ad accounts, rotating exits repeatedly triggered ‘abnormal login’ warnings and forced rechecks. Using fixed static IPs, risk alerts fell, logins stayed clean, and campaign delivery schedules became predictable again for our team.

Michael Carter

With staff spread across cities and stores, shared access often tripped security prompts when IPs changed. Keeping a consistent pool of static IPs made backend checks uniform, reduced challenges, and streamlined operations for everyone.

Emily Johnson

For price monitoring, sites are sensitive to bursty, frequent requests and quickly raise defenses. Pairing static IPs with time-sliced crawling produced steadier traffic, fewer alerts, and more complete datasets without sacrificing coverage over time.

Sophia Reed

Our platform requires a fixed egress IP for allowlisted access. After adopting static IPs, we stopped updating allowlists every week. Ops workload dropped, audits became simpler, and we rolled out role-based access with confidence.

Daniel Brooks

For multilingual localization testing, long-term regional consistency matters more than raw speed. With fixed static IPs, we could reproduce results across runs, isolate location issues faster, and resolve bugs without guessing the endpoint anymore.

Natalie Parker

Residential Proxy IPs From Around the World

XoProxy provides residential proxy IPs across 190+ countries and regions to support your global business needs.

Explore All Regions

‘Unlimited’ typically means the plan is not primarily billed by transferred data (GB), making it suitable for long-running workloads and sustained request patterns.

Dynamic proxies provide available egress endpoints under the service’s allocation strategy, helping distribute requests, reduce pressure on a single exit, and improve workload continuity.

Even when data usage is not the billing unit, performance may still be affected by bandwidth, concurrency, node capacity, and fair-use policies; actual limits follow the plan details and Terms of Service.

Large customer customization

Global enterprise-level IP proxy professional solution reseller