Proxy plans now up to 15% cheaper
View pricing

Datacenter Proxies on IPv6

One order gives you every supported Datacenter IPv6 location, each with its own private /48, and unlimited traffic at the Mbps speed you choose. Built for fast public-data jobs, APIs and automation on targets that use IPv6 or a supported CDN.

Unlimited traffic at your Mbps speed

A dedicated /48 in each location

Reach supported CDN sites over IPv6

Automatic setup (up to 10 minutes)

Datacenter Proxies on IPv6 Datacenter Proxies on IPv6
  • 45+IPv6 locations
  • /48Per location
  • Sticky to FOREVERSessions
  • 99.9%Network success rate
  • HTTP/HTTPS/SOCKS5Protocols
From $3.80 / day at 15 Mbps

Daily from $3.80 · Weekly from $24.99 · Monthly from $58.99 — up to $849.99/mo at the top speed tier

Speed tiers run from 15 Mbps to 250 Mbps. Every tier includes unlimited traffic and every supported location. Start with a day to test your targets.

Compare speed tiers

When should you choose Datacenter IPv6 proxies?

Choose Datacenter IPv6 when speed and volume matter more than residential reputation. You pay for an Mbps speed tier and a period, not for gigabytes: no per-GB charge, no usage threshold and no throttling after heavy use. One order covers all 47 supported locations in 25 countries, each with its own private /48. Your targets need to use IPv6 or a supported CDN; Cloudflare, Akamai, Fastly, and Amazon CloudFront are examples, not the full supported set.

Supported locations included
Private /48 per supported location
Sticky 5 seconds to FOREVER or rotating
1 to 5,000 unique ports
HTTP/HTTPS/SOCKS5 (UDP via SOCKS5)
Up to 50 whitelisted IPs
CDN-aware IPv6 reachability

Volume without a traffic bill

Deep crawls, retries and heavy pages use no GB budget. Your tier sets the speed; traffic is unlimited for the period you buy.

Many regions, one order

Collect from North America and Europe to Asia-Pacific, South America, Africa and the Middle East without buying locations one at a time.

Sessions that fit the job

Hold one IPv6 address from 5 seconds to FOREVER for a multi-step flow, or rotate addresses for broad collection.

Common workflows for this plan

Use these related use cases if you want to see how this plan fits a real job before checkout.

Web scraping

Run faster collection jobs when the target is comfortable with datacenter infrastructure and IPv6 traffic.

See the web scraping use case

Competitor analysis

Use the included supported locations and higher throughput for repeated checks against public pricing, messaging, and catalogue changes.

See the competitor analysis use case

Which locations does Datacenter IPv6 cover?

Datacenter IPv6 covers 47 supported locations in 25 countries, all listed below. One order includes all of them, and each location has its own private /48 subnet.

25 countries with supported Datacenter IPv6 locations
All supported locations included in one order
Private /48 per supported location
Sticky 5 seconds to FOREVER or rotating

How do Datacenter IPv6 proxies work?

You buy speed and time instead of traffic, then choose where each request exits. Every supported location is already in your order.

  1. Pick a speed and a period

    Choose an Mbps speed tier and a daily, weekly or monthly period. Traffic is unlimited at that speed for the whole period, and you can move to a faster tier later with the Upgrade Speed option in your account.

  2. Pay and connect

    Datacenter IPv6 setup starts automatically after payment clears. Allow up to 10 minutes before connecting; you can connect as soon as setup is complete.

  3. Choose the exit location

    With User:Pass login, add a country to your proxy username, plus one of its listed cities to narrow the exit. With IP Auth, use SuperPorts to give a range of ports its own country and a timed sticky session instead.

  4. Hold or rotate the address

    Keep one IPv6 address from 5 seconds to FOREVER, or rotate addresses when the job needs variety.

Keep your IPv6 workflows moving across supported CDN sites

Reach supported CDN-fronted sites with Datacenter IPv6, even when the domain has no published IPv6 address (AAAA record). CDN-aware reachability is included, so you can keep more of your monitoring, QA and public-data work on IPv6.

More room for your IPv6 work

A missing AAAA record need not stop your workflow

Your target may still be supported. Both ColdProxy IPv6 plans include the same CDN-aware reachability. Choose USA residential IPv6 or multi-location Datacenter IPv6 for the network and coverage your work needs, without giving up this benefit.

IPv6 connections

Your supported requests stay on IPv6, with no IPv4 fallback.

Included in both IPv6 plans

Residential IPv6 and Datacenter IPv6 provide the same CDN-aware reachability.

Keep work moving

Reach supported CDN-fronted targets for QA, monitoring, ad verification and public-data collection.

Check the sites you work with

Use the IPv6 Checker to see published IPv6 addresses and recognised CDN signals. Detecting a CDN alone does not confirm ColdProxy support.

Try your real workflow

Start with a daily plan to validate the exact domains and requests you need before committing to a longer period.

Keep supported traffic on IPv6

Use CDN-aware reachability for supported CDN-fronted domains alongside sites that publish IPv6 addresses. For other IPv4-only targets, choose a Residential IPv4 plan.

When should you choose this plan instead of another ColdProxy plan?

All three plans here include unlimited traffic at their Mbps tier. Choose Datacenter IPv6 for speed and every supported location in one order, each with its own private /48. Choose Residential IPv6 for USA residential IPv6 addresses, or Residential IPv4 when a stricter site needs residential reputation or a country outside this list.

This plan vs its nearest alternatives

Datacenter IPv6

Current page
Best fit
Fast public-data jobs, APIs, and speed-first automation on targets on IPv6 or a supported CDN that need supported Datacenter IPv6 locations, sticky sessions from 5 seconds to FOREVER or rotating sessions, or CDN-aware IPv6 reachability.
Billing
Daily, weekly, monthly
Why choose it
Choose this when the target publishes IPv6 addresses or is served by a supported CDN, and speed, included Datacenter IPv6 location coverage, and private /48 allocation matter more than residential reputation.

Residential IPv6

Best fit
Targets on IPv6 or a supported CDN that need USA residential IPv6 addresses, a /32 IPv6 subnet, sticky sessions from 5 seconds to FOREVER or rotating sessions, Mbps-tiered throughput, and CDN-aware IPv6 reachability.
Billing
Hourly, daily, weekly, monthly
Why choose it
Choose this when the target publishes IPv6 addresses or is served by a supported CDN, and you want USA residential traffic, a /32 IPv6 subnet, and long sticky or rotating sessions.

Residential IPv4 (Unmetered)

Best fit
Larger or ongoing residential jobs that need sustained throughput on an Mbps speed tier.
Billing
Hourly, daily, weekly, monthly
Why choose it
Choose this when the residential job runs steadily and you want throughput set by an Mbps speed tier, with no per-GB quota to track.
Compare all four plans

Why choose this Datacenter IPv6 plan

Speed-first IPv6 capacity you can plan around, with the controls your tools already expect.

Run it from your code

Your service comes with its own Customer Plan API to generate proxy lists, update whitelisted IPs, upgrade the speed and renew the plan.

Help around the clock

Get help 24/7 in English or Arabic through Telegram or support tickets.

A private /48 per location

Each location has its own private /48, a dedicated range instead of a shared pool.

Unlimited traffic at your speed

Traffic is unlimited for the whole period you buy. Your Mbps tier sets the pace, not a GB budget.

Works with the tools you run

HTTP, HTTPS or SOCKS5 (UDP via SOCKS5), User:Pass or IP Auth with up to 50 whitelisted IPs, and 1 to 5,000 ports.

Supported CDN sites over IPv6

Reach supported CDN-fronted domains over IPv6, even when the domain publishes no AAAA record.

Verify IPv6 routing and proxy output before rollout

Check whether the target publishes IPv6 addresses or its DNS points to a CDN, then confirm reachability, exit IP, and location before increasing Datacenter IPv6 usage.

Integrations and workflow compatibility

Connect ColdProxy Datacenter IPv6 proxies with APIs, collection tooling, and automation stacks that need supported location coverage, HTTP/HTTPS/SOCKS5 (UDP via SOCKS5), private /48 allocation, and CDN-aware IPv6 reachability.

Designed for APIs, collection tooling, and speed-first automation
HTTP/HTTPS/SOCKS5 protocol support (UDP via SOCKS5)
Private /48 per supported Datacenter IPv6 location
CDN-aware IPv6 handling for supported CDN-fronted targets
A better fit when throughput matters more than residential reputation
SuperPorts give IP Auth traffic location and sticky sessions per port range
Selenium
Puppeteer
Playwright
Scrapy
SwitchyOmega

Connect the tools you already use

Use ColdProxy with the platforms your team already trusts instead of rebuilding the workflow around one proxy vendor.

Explore integrations

Questions about Datacenter IPv6 proxies

Answers on traffic, locations, sessions, protocols, CDN reach and when a residential plan is the better choice.

View all

Your traffic runs through datacenter IPv6 addresses instead of residential ISP networks, so the plan suits speed-first work, with every supported location in one order and a private /48 in each. Like the speed-tier residential plans, it has unlimited traffic at your Mbps tier. Choose a residential plan when a site needs consumer ISP reputation.

Yes. You pay for an Mbps speed tier and a period, not for gigabytes. There is no per-GB charge or quota, no usage threshold and no throttling after heavy use; your tier sets the maximum speed.

Pick the tier by the speed your job needs, not by how much data it moves: traffic is unlimited on every tier. Compare the tiers on Datacenter IPv6 pricing. If you are unsure, start lower on a daily plan. When speed becomes the limit, move to a faster tier with the Upgrade Speed option in your account; an upgrade can restart the proxy server in the background, so re-check your proxies before you resume the job.

With User:Pass login, add the country to your proxy username, plus one of its listed cities to narrow the exit; each request then exits from that location. With IP Auth, requests default to Worldwide, and you bind a country to a range of ports with SuperPorts instead. The Datacenter IPv6 setup guide shows both. Every listed location is already in your order.

Yes. ColdProxy's Datacenter IPv6 plan supports sticky sessions from 5 seconds to FOREVER or rotating sessions, so the right choice depends on whether the workflow needs continuity or changing IPv6 addresses.

Yes. Datacenter IPv6 supports HTTP and HTTPS over TCP, and SOCKS5 over TCP or UDP, with User:Pass or IP Auth, up to 50 whitelisted IPs and 1 to 5,000 unique ports. IP Auth requests carry no username, so SuperPorts give a range of ports its own location and sticky session instead.

CDN-aware reachability keeps your requests on IPv6 for supported CDN-fronted sites, even without a published AAAA record. It is included in both IPv6 plans, with no IPv4 fallback. Use a daily Datacenter IPv6 plan to validate your exact targets.

Check that the target publishes IPv6 addresses or is served by a supported CDN; Cloudflare, Akamai, Fastly, and Amazon CloudFront are examples, not the full supported set. ColdProxy's free IPv6 Checker shows the target's IPv6 addresses and whether its DNS points to a recognised CDN; a recognised CDN is not always a supported one. If you are unsure, test on a daily plan before you commit to a larger workflow.

Datacenter IPv6 covers 47 supported locations across 25 countries, and one order includes all of them.

Yes. Each supported location in your order has its own private /48 subnet.

This plan is usually strongest for APIs, high-throughput public-data collection, competitor monitoring, and speed-first automation on targets that publish IPv6 addresses or are served by a supported CDN, when the workflow already works well on datacenter infrastructure.

Not usually. Start with Residential IPv4 when the site is stricter or when residential reputation matters more than pure speed and supported location routing.

Need a tailored proxy plan for a large project?

Need a different speed or traffic allowance? Contact us through the channels on our website so we can assess whether a custom plan is possible.

Contact Our Sales TeamTelegram & ticket support · English and Arabic