Pool size is not the selection criterion
IPv6 blocks are large. That is accurate and mostly irrelevant for proxy selection. The exit address is one variable. The others — whether the target serves content over that version, whether the geolocation database maps the address to the right country, whether the site's CDN paths and image hosts respond — those determine whether a request produces usable output.
A request that returns HTTP 200 on the main HTML but pulls images from a CDN that drops IPv6 connections gives you a broken page. The status code looked fine. The billed bytes went out. The result was not.
Most public targets still prefer IPv4
Dual-stack adoption varies by target. Major CDNs and large platforms tend to accept both versions, but regional retail sites, smaller news publishers, and specialized data targets often serve IPv4 only — or route IPv6 requests through different infrastructure: different server, different cache, sometimes a different page variant.
The practical test is direct: hit the target URL through an IPv4 proxy, then through an IPv6 proxy if one is available, compare content length and final URL, and check whether dependent objects loaded. A colon-separated address from an IP-echo endpoint tells you which version the connection used.
| Signal | What to check |
|---|---|
| HTTP status | 200 over IPv4 and IPv6, or only one? |
| Final URL | Same path, or redirected to a different region? |
| Content length | Same page shape, or stripped mobile variant? |
| Object loads | CDN assets and images responding on both versions? |
| Geolocation result | Country and city match the target market? |
IPv6 geolocation databases have gaps
Country-level geolocation for IPv4 is well-covered. City and ISP-level records are better still. IPv6 coverage lags behind in most databases, particularly for residential prefixes outside North America and Western Europe. If the job requires country precision — retail price checks, search result audits, regional ad verification — the IPv4 residential route carries less risk of landing in the wrong market.
On Proxynade's residential plans, country targeting routes through the expanded username token: country-<cc> selects the exit country at the gateway level regardless of which IP version the selected exit carries. If a specific country's residential pool only has IPv4 exits, a request targeting that country uses IPv4.
When IPv6 is the right call
IPv6 makes sense when the target is confirmed IPv6-native or dual-stack and you have verified the content is identical across both versions. It also applies when testing your own dual-stack infrastructure, or when a specific target applies stricter rate limits to IPv4 ranges because IPv4 datacenter blocks are more heavily fingerprinted.
Those are specific conditions. For general public-web collection with country or city targeting requirements, IPv4 residential is the default worth starting with.
Proxynade plan coverage
All plans bill per transferred GB. Volume Residential is $0.89/GB with country, region, and city targeting. Premium Residential is $5.00/GB and adds ISP and ASN targeting alongside stronger route quality. Datacenter is available for lower-latency jobs where residential routing is not required. Static ISP proxies are pay-per-IP with unlimited bandwidth.
The dashboard network logs show host, outcome, latency, and byte totals for each request. If a route is producing retries, redirects to the wrong market, or high byte spend relative to usable rows, the logs surface that directly. IPv6 does not change the billing model — bytes transferred are bytes transferred regardless of exit version.
Verify the exit version before assuming
To confirm which IP version a proxy connection is using, route a request to an IP-echo endpoint and read the returned address format. The Python Requests proxies parameter accepts a scheme-keyed dict with the proxy URL.
# Python — checks exit IP version through the gateway
import requests
proxies = {
"http": "http://proxynade.net:2555",
"https": "http://proxynade.net:2555"
}
auth = ("PROXY_USER", "PROXY_PASS")
r = requests.get("https://ifconfig.me/ip", proxies=proxies, auth=auth, timeout=10)
print(r.text.strip())
# dotted-quad → IPv4 exit (e.g. 203.0.113.7)
# colon-delimited → IPv6 exit (e.g. 2001:db8::1)PROXY_USER carries the routing options in the expanded format: base username plus plan token (volume, premium, or datacenter), optional country-<cc>, and optional lifetime-<minutes> rotation window. Datacenter lines skip the lifetime token.
IPv4 vs IPv6 proxy FAQ
Do most proxy targets support IPv6? No. Most public web targets still accept IPv4 only, or serve different content over IPv6. Test the specific target before assuming IPv6 routes will work.
Is IPv6 cheaper as a proxy type? IPv6 datacenter addresses are cheaper to acquire than IPv4, so some providers pass that along. Proxynade's pricing is per-GB transferred, not per IP version.
When should I use IPv6 proxies? When the target is confirmed dual-stack or IPv6-only, or when testing your own IPv6 infrastructure. For most public-web collection jobs, IPv4 is the safer default.
Does geolocation work the same for IPv4 and IPv6? Not always. IPv6 geolocation databases are less complete for many regions, so country and city targeting can be less precise over IPv6 than over IPv4 residential routes.
How do I tell which IP version a proxy connection uses? Hit an IP-echo endpoint (e.g. ifconfig.me) through the proxy and read the returned address. A colon-separated address is IPv6; dotted-quad is IPv4.
Route selection checklist
- Test the target URL over IPv4 first; confirm status, final URL, and content shape.
- If IPv6 is available, run the same test and compare content length and object loads.
- Check that geolocation lands in the target market, not just the right country.
- Log billed bytes alongside usable rows — retries inflate byte spend without adding data.
- Use the dashboard network logs to confirm which exits are producing clean responses.