Referral Program
HomeProxy TypesIPv6 Proxies
IPv6

IPv6 proxies

The cheapest addresses we sell, and the narrowest in scope. An IPv6 proxy reaches a site only when that site answers over IPv6, so the first question is never the price. It is whether your target publishes an AAAA record.

What you get

$0.20 per IP per month, the lowest price in our catalogue
17 countries
Pools that do not run out: one /64 holds more addresses than all of IPv4
HTTP and SOCKS5 on the same credentials
Issued within a minute of a top-up

Connection strings

Same host, same credentials and the same suffix grammar as the rest of our types. The difference is on the other end of the wire, not in the string.

Endpoint

proxy.sotaproxy.com
login_c_COUNTRY:password@proxy.sotaproxy.com:PORT

Any IPv6 address in Germany

curl -x login_c_DE:password@proxy.sotaproxy.com:10000 https://api64.ipify.org

SOCKS5 instead of HTTP

curl -x socks5://login_c_DE:password@proxy.sotaproxy.com:10001 https://api64.ipify.org

Check what the target actually sees

curl -x login_c_DE:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json

Use api64.ipify.org rather than api.ipify.org when testing: the first answers over both protocols, the second is IPv4 only and will make a working IPv6 exit look broken.

Checks worth running before you buy

Does the target answer over IPv6 at all

dig AAAA www.google.com +short
dig AAAA www.amazon.com +short   # empty output means IPv4 only

Does the exit work and where is it

curl -s -x login_c_DE:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json

Compare the same page over both protocols

curl -s -o /dev/null -w "ipv6 %{http_code} %{time_total}s
" -x login_c_DE:password@proxy.sotaproxy.com:10000 https://www.google.com/
curl -s -o /dev/null -w "ipv4 %{http_code} %{time_total}s
" -x login_c_DE_v4:password@proxy.sotaproxy.com:10000 https://www.google.com/

All integrations: Python, Scrapy, Selenium, Playwright and more

Countries

IPv6 is available in 17 countries. The list is shorter than our IPv4 coverage because it follows what the upstream networks actually announce over IPv6, and that is a smaller set than the countries where hosting exists at all:

AustraliaBrazilBulgariaCanadaCzechiaFranceGermanyIndiaJapanNetherlandsPortugalRomaniaSingaporeSpainTurkeyUnited KingdomUnited States

Country targeting is reliable. City targeting on IPv6 is not, and we would rather say so than sell you a city you will not actually land in.

What goes wrong, and what it means

Network unreachableThe target has no IPv6 at all

Check with dig AAAA. If empty, move the job to IPv4.

403 on the first requestThe prefix is already classified on the far side

Another type will serve you better here; the address itself is not the problem.

Works in curl, fails in the browserThe browser chose IPv4 for the same hostname

Force the protocol in the client, or test with a hostname that is IPv6 only.

Slow first byte, fast transferThe route to the target over IPv6 is longer than over IPv4

Normal on some networks. Compare against the same target over IPv4 before blaming the pool.

The limits, stated plainly

  • Reaches only targets that publish an AAAA record. There is no way around this and no fallback.
  • Bans land on prefixes, not addresses. A single /64 decision on the far side can retire thousands of your addresses at once.
  • Geolocation resolves to country reliably and to city poorly.
  • Some corporate networks and older home routers drop IPv6 entirely, so a client on such a network cannot use these endpoints.
  • Browsers prefer IPv4 when both are available, so a browser test can silently go out over the wrong protocol and tell you nothing.

Typical use cases

Position checks in Google search, which has answered over IPv6 for yearsCollecting metadata from YouTube and other Google properties at volumeAny target you have already confirmed serves IPv6 and where you need many distinct addresses cheaplyLoad testing your own services over IPv6Jobs where the price per address decides whether the job runs at all

Common questions

How do I know whether my target supports IPv6?

One command: dig AAAA example.com +short. If it prints an address, the site answers over IPv6 and our addresses will reach it. If it prints nothing, no IPv6 proxy in the world will help, and you need IPv4.

Why is IPv6 so much cheaper than IPv4?

Because the price of IPv4 is the price of scarcity. There are about four billion IPv4 addresses and they ran out years ago, so they are traded and leased. IPv6 has no scarcity, so what you pay for is the routing and the maintenance, not the address.

If one address gets banned, do I lose the whole pool?

That is the real risk, and it is the honest reason IPv6 is not a universal replacement. Sites rarely ban a single IPv6 address, because handing out a fresh one is trivial. They ban a prefix, usually a /64 and sometimes a /48. One decision on their side can retire a very large number of your addresses at once.

Can I run account work on IPv6?

Usually not. Platforms that care about accounts read address class first, and consumer devices in most countries still reach them over IPv4. An IPv6 address from a hosting range is easy to classify and is treated accordingly.

Is there an automatic fallback to IPv4?

No. If you connect through an IPv6 endpoint and the target has no IPv6, the connection simply fails. Decide per target, not per project.

How precise is the geolocation?

Less precise than IPv4. Country resolves reliably; city often does not, because IPv6 allocations are newer and geolocation databases have had less time and less traffic to place them.

Start with IPv6 Proxies

No monthly minimum. Get credentials in minutes.

Use code WELCOME10 - 10% off any proxies on your first order

Create Account