Proxy plans now up to 15% cheaper
View pricing

Datacenter IPv6

Set up a datacenter IPv6 proxy (/48) across 25 countries: authentication, endpoint, ports, and a working ipv6 proxy request example.

Products4 min readLast updated October 2026

This guide walks through datacenter IPv6 proxy setup on ColdProxy's speed-tiered datacenter network. You buy a Mbps speed tier, and one order includes all 47 supported locations across 25 countries, each with its own private /48 block; you pick the exit location (a country, or a city within it) per request, or use the All Country random option. Like Residential IPv6, it includes CDN-aware IPv6 reachability for supported CDN-fronted domains. The steps below cover authentication, the gateway endpoint and ports, and a working request example so you can connect over the same per-service gateway as every ColdProxy plan. The full product overview lives at /proxy/datacenter-ipv6/, and current pricing is on the pricing page.

What you are buying

Datacenter IPv6 is a speed-tiered datacenter proxy product. You choose a throughput tier in Mbps, and a single order includes all supported locations, each with its own private /48 IPv6 block; you select the exit location per request with username tags or SuperPorts, not at purchase time. Sticky sessions can be held from 5 seconds up to FOREVER, and billing starts at the daily level. The full location list is in Choosing a product.

What you are buying
Attribute Value
Billing model Mbps speed tier
Coverage 25 countries, 47 locations (+ All Country random option)
Included All supported locations in one order, private /48 per location
Sticky session range 5 seconds to FOREVER
Billing periods Daily, weekly, monthly
Routing CDN-aware IPv6 reachability for supported CDN-fronted domains
Protocols HTTP, HTTPS (TCP); SOCKS5 (TCP and UDP)
Authentication User:Pass and/or IP whitelist
Note

Targeting All Country assigns a random location from the supported set, useful when you do not need a specific country. For the residential IPv6 alternative and how to pick between them, read Residential IPv6 vs Datacenter IPv6 Proxies.

Check IPv6 reachability first

Warning

Datacenter IPv6 reaches targets that publish an AAAA DNS record, plus supported CDN-fronted domains (see CDN-compatible routing below). Many other sites are IPv4-only and cannot be reached over IPv6. Check your target with the free IPv6 Checker before buying: it should publish IPv6 addresses or be served by a supported CDN. If you are unsure, test on a daily plan first. The IPv6 Proxy Compatibility Checklist covers the full pre-flight check.

CDN-compatible routing

Datacenter IPv6 suits CDN edge testing and dual-stack QA: validating how a site behaves when served to IPv6 clients from a CDN such as Cloudflare, Akamai, Fastly, or CloudFront. For supported CDN targets without a published AAAA record, ColdProxy's included CDN-aware reachability keeps supported requests on IPv6, with no IPv4 fallback. Use the IPv6 Checker to check published IPv6 addresses and CDN signals; a detected CDN alone does not confirm ColdProxy support. Validate your exact target on a daily plan, and see IPv6 Proxies for CDN Testing for the full workflow.

Tip

Confirmed IPv6-compatible platforms include Google, YouTube, Facebook, Instagram, WhatsApp, Bing, Yahoo, Netflix, and LinkedIn. These are convenient endpoints when validating dual-stack behavior through a CDN.

Connection details: how to configure the datacenter IPv6 proxy

Datacenter IPv6 connects through its own per-service gateway:

Code
gw-2312.coldproxy.com

2312 is the service/package ID of the plan you purchased. Use any port in the 30000–34999 range (30000 in the examples). HTTP, HTTPS, and SOCKS5 run on the same gateway and are auto-detected. The canonical proxy string is:

Code
gw-2312.coldproxy.com:30000:USERNAME:PASSWORD

Most clients also accept USERNAME:PASSWORD@gw-2312.coldproxy.com:30000. See How to Connect and Authentication for the full reference.

Tip

Datacenter IPv6 setup starts automatically after payment clears. Allow up to 10 minutes, and connect as soon as setup completes. See Activation and setup times.

Connect example

Use an IPv6-capable echo endpoint to confirm an IPv6 exit:

Shell
curl -x "http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api6.vipv6proxy.com/api/checker/my-ip"
Python
import requests

proxy = "http://USERNAME:PASSWORD@gw-2312.coldproxy.com:30000"
proxies = {"http": proxy, "https": proxy}

resp = requests.get("https://api6.vipv6proxy.com/api/checker/my-ip", proxies=proxies, timeout=30)
print(resp.json())

Verify IPv6 reachability, the exit IP, and location with Proxy Checker and My IP.

Geo-targeting and sessions

Under User:Pass auth, the username tag scheme controls the exit location (a country, or a city within it, from the 47 supported locations) and the session. Sticky sessions can be held from 5 seconds to FOREVER. A timed sticky session turns on only when both -session- and -time- are present; the FOREVER hold is the -identifier- pin shown below, not a -time- value:

Shell
curl -x "http://user-country-de-session-481516-time-4h:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api6.vipv6proxy.com/api/checker/my-ip"

To pick a listed city, add a -city- tag inside its country. This request exits from Berlin, one of the listed Datacenter IPv6 locations in Germany:

Shell
curl -x "http://user-country-de-city-berlin:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api6.vipv6proxy.com/api/checker/my-ip"

For a deterministic, stateless IP pin that needs no session lifetime, use -identifier-. This is the username format the client area generates, where USERNAME is your service username and the identifier value stays as issued; see IP pinning on IPv6 plans:

Shell
curl -x "http://USERNAME-identifier-mumcgy8tafa7dj0:PASSWORD@gw-2312.coldproxy.com:30000" \
  "https://api6.vipv6proxy.com/api/checker/my-ip"
Warning

The literal tag prefixes are set per product; confirm the exact prefix tokens for your plan in the client area before production use. See the Username Tag Scheme page for the full grammar.

Note

If you authenticate by IP whitelist, requests are issued in IP:PORT form and location defaults to Worldwide. Use SuperPorts to bind country and session behavior to port ranges for IP-auth traffic.

Next steps

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