IPv6 Proxies for Claude
Anthropic's assistant, available as claude.ai, desktop and mobile apps and the Claude API. claude.ai answers with 1 AAAA record, so QuanticData IPv6 proxies reach it: rotating or static sessions on /48 and /64 subnets, country in the username, from $0.20/GB down to $0.083/GB on 3 TB — for the public, high-volume side of Claude, not for its accounts.
From $0.20/GB · Rotating or static sessions · HTTP, HTTPS and SOCKS5
Does Claude accept IPv6? What we measured
On 20 September 2026 we looked up claude.ai from two public resolvers, 1.1.1.1 and 8.8.8.8: both answer with 1 AAAA record, the first one 2607:6bc0::10, and both agree. Claude was not in our September census of 102 domains, so this is the same DNS check run on its own host. The hosts behind it: api.anthropic.com (1 AAAA), console.anthropic.com (1 AAAA).
This is a DNS check, not a connection test: an AAAA record means an IPv6 exit can reach the host, and nothing more. What the platform serves to a given client is decided by its own rules, its rate limits per prefix and its anti-automation, which is why every page in this family says which jobs fit and which do not.
Why IPv6 proxies for Claude
Anthropic is dual-stack across the board: claude.ai, api.anthropic.com, console.anthropic.com and www.anthropic.com each publish an AAAA record. An IPv6 exit therefore reaches the API, the console and the web app. As with every assistant, the web app is a login and a login is not an IPv6 job; the API is where an IPv6 exit is cheap, correct egress for a service that calls it from a fixed place or a chosen country, with limits that are per key and tier rather than per address.
The larger case is Claude Code and the agents people build with the API and MCP servers: tools that fetch pages, search and read documentation as part of a task. Those fetches are ordinary web traffic, hundreds of them per session, and the ones bound for dual-stack sites can leave from an IPv6 exit at $0.083 to $0.20 per gigabyte. On this site the same account also carries residential exits for the IPv4-only sites, and the MCP server exposes search and scrape tools that bill per successful result — so an agent can pick the cheapest path per request.
What to run on IPv6 for Claude, and what not to
Four jobs people bring to Claude, and the network each one belongs on. "Yes" means a rotating IPv6 exit is the right and cheapest tool; "Partly" means IPv6 carries part of the job; "No" means residential or mobile, and the reason is in the notes.
| Job | IPv6? | Notes |
|---|---|---|
| Web fetches of agents built on the API or MCP | Yes | Dual-stack destinations over IPv6, IPv4-only ones over residential, on one account. |
| API egress from a fixed service | Partly | api.anthropic.com resolves over IPv6; limits are per key and tier, so IPv6 only sets egress cost and country. |
| Monitoring public Anthropic pages | Yes | Pricing, model and documentation pages: public, light, cheap to sample. |
| claude.ai accounts and Claude Code sessions | No | A login wants a stable household or phone address on a sticky session. |
When IPv6 is the wrong network for Claude
claude.ai and Claude Code sessions, which are logins and belong on a sticky residential session in the account's country, within Anthropic's usage policy. IPv6 is for API egress and for the web fetches of the agents you build.
The same account carries the other networks: mobile proxies for Claude (carrier IPs, sticky up to 24 hours, from $5 for 1 GB) and residential proxies for Claude (home-ISP IPs in 200+ countries, from $1.00/GB, with a free 100 MB trial). A proxy changes where your requests appear to come from; it does not change your Anthropic account, its usage limits or the acceptable-use policy. Whether the service is offered in a given country is between you and Anthropic.
Which session to use for Claude on IPv6: rotating or static
Rotating for data, static when a flow must keep one IP. Sticky for anything logged in (claude.ai profiles, agents that hold a session on a third-party site); rotating for API-driven retrieval where every fetch is independent. On the IPv6 network the username carries the country; leave the session out for a fresh address on every request, or set a static session in the endpoint generator when a flow must keep one. Host, port and password are in your dashboard after purchase.
# PROXY_HOST and PORT are shown in your dashboard
# no session in the username: a fresh IPv6 address on every request
curl --proxy "http://PROXY_HOST:PORT" \
--proxy-user "USER-country-us:PASS" \
--connect-timeout 10 --max-time 30 \
-A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/128.0 Safari/537.36" \
"https://www.anthropic.com/pricing"
# check the exit: the address in the answer is an IPv6 one
curl --proxy "http://PROXY_HOST:PORT" --proxy-user "USER-country-us:PASS" https://api64.ipify.orgPacing by /64. Nothing to pace on Anthropic's side; API limits are per key. Pace the agent's fetches per destination — rotating exit per request, a low rate per /64 on each target site.
Best countries for Claude IPv6 proxies
The exits most often asked for with Claude. Every IPv6 country page lists the username code and what that market is used for; 18 countries are available on the IPv6 network.
IPv6 proxy pricing for Claude
Per GB, each pack valid 30 days, unlimited concurrent sessions, country targeting included, no port fees. Pay from balance, card, PayPal or crypto. The free trial is on the residential pool (100 MB, 5 days, no card).
The same pool at every tier — a small Claude test costs exactly $20. Full ladder and terms on the pricing page; the honest comparison with IPv4 is on the IPv6 proxies page.
Set it up for Claude
QuanticData IPv6 proxies are standard HTTP and SOCKS5 endpoints: a host, a port, a username and a password, shown in your dashboard the moment a pack is active. Below, a request to a public Claude page through the IPv6 gateway with a rotating exit, in curl and in Python.
import requests
# host and port from your dashboard; country in the username
proxy = "http://USER-country-us:PASS@PROXY_HOST:PORT"
r = requests.get("https://www.anthropic.com/pricing",
proxies={"http": proxy, "https": proxy},
headers={"User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/128.0 Safari/537.36"},
timeout=30)
print(r.status_code, len(r.content))SOCKS5 works with the same username on the SOCKS5 port (socks5h:// in Python's proxies, --socks5-hostname in curl), so the hostname is resolved at the exit — which is what you want, because the exit is the one with IPv6 connectivity. Test with https://api64.ipify.org: the answer should be an IPv6 address in the country you set.
FAQ
IPv6 Proxies for Claude: does it accept IPv6, which session, IPv6 or residential, price, free options.
Something else? Ask us →Does Claude accept IPv6 proxies?
QuanticData checked: claude.ai publishes 1 AAAA record (DNS from 1.1.1.1 and 8.8.8.8 on 20 September 2026), so an IPv6 exit reaches Claude. That is a DNS fact, not a promise of access: Claude still decides what it serves, and this page lists the jobs that fit — web fetches of agents built on the api or mcp and monitoring public anthropic pages — and the ones that do not.
Can Claude Code or an MCP agent use an IPv6 proxy for its web fetches?
QuanticData thinks this is the best use of IPv6 around Claude: we found api.anthropic.com and claude.ai dual-stack, and the page fetches an agent makes are ordinary HTTP traffic that can leave from an IPv6 exit when the destination is dual-stack — 45 of the 102 major sites in our census are. IPv4-only destinations and any login go through residential on the same account, and the QuanticData MCP server offers search and scrape tools billed per result for the pages that need rendering.
Which IPv6 proxy session should I use for Claude: rotating or static?
QuanticData recommends rotating for data collection, and a static session only when a flow must keep one address on Claude. Sticky for anything logged in (claude.ai profiles, agents that hold a session on a third-party site); rotating for API-driven retrieval where every fetch is independent. On the IPv6 network a request with no session in the username gets a fresh address from the pool; a static session is set in the endpoint generator in your dashboard. Pace by /64, not by address: Nothing to pace on Anthropic's side; API limits are per key. Pace the agent's fetches per destination — rotating exit per request, a low rate per /64 on each target site.
IPv6 or residential proxies for Claude?
QuanticData's answer for Claude is IPv6 for web fetches of agents built on the api or mcp and monitoring public anthropic pages — rotating exits at $0.20/GB down to $0.083/GB — and residential or mobile for claude.ai accounts and claude code sessions. The two live on the same account, so a pipeline can send each request to the network that fits it. claude.ai and Claude Code sessions, which are logins and belong on a sticky residential session in the account's country, within Anthropic's usage policy.
How much do IPv6 proxies for Claude cost?
QuanticData charges the same for every platform: $20 for 100 GB ($0.20/GB), $40 for 250 GB, $70 for 500 GB, $110 for 1 TB and $250 for 3 TB ($0.083/GB), each valid 30 days, with unlimited concurrent sessions and no per-port fees. Country targeting — the United States, the United Kingdom and India are the exits most asked for with Claude — costs nothing extra. Pay from balance, card, PayPal or crypto.
Is there a free IPv6 proxy for Claude?
QuanticData does not give away IPv6 bandwidth: the smallest pack is $20 for 100 GB. What is free is the residential trial — 100 MB on Residential Basic for 5 days, no card — enough to check that your Claude workflow behaves through a proxy before paying for IPv6 volume. Public "free IPv6 proxy" lists are shared addresses that the platforms already know and that disappear within days; nothing built on them keeps working.
Get IPv6 proxies for Claude in minutes
Free account, pick a pack, credentials in your dashboard. IPv6 starts at $20 for 100 GB.
Buy IPv6 bandwidth Create a free account