IPv6 proxies come from next-generation subnets with a practically unlimited supply of addresses, which is why they cost several times less than IPv4. Every address is dedicated and static and works over HTTPS and SOCKS5. The one limitation: the target site must support IPv6, otherwise the connection will not be established.
ProxyFarm issues addresses from different /64 and /48 subnets so platforms do not see them as one block, and runs racks in Russia, the USA, Germany and the Netherlands.
IPv6 pricing per address
| Package | Price per IP | Total per month | Subnets | Best for |
|---|---|---|---|---|
| 10 addresses | 18 ₽ | 180 ₽ | one /64 | testing, small scraper |
| 100 addresses | 15 ₽ | 1 500 ₽ | 10 × /64 | Google and YouTube scraping |
| 1 000 addresses | 13 ₽ | 13 000 ₽ | 100 × /64 | SERP tracking, checkers |
| 10 000 addresses | 12 ₽ | 120 000 ₽ | multiple /48 | data teams, SaaS |
Rotation on a package: one entry port serves a new IPv6 on every request, +20 %. 15 % off for a quarter.
IPv6 blocks: /64, /48 and /36
If you need tens of thousands of addresses, buying a whole block is cheaper. The subnet is routed to your server through a tunnel or announced via BGP to your ASN, and you run your own proxy server (3proxy, Squid, gost) and generate as many addresses as you need. You can also take the block with our VPS where proxies are already configured, or with our rotation gateway: then you get a single address, gw.proxyfarm.ru:9100, and control everything through the login.
| Block | /64 subnets | Without rotation | Rotating with sticky sessions | Best for |
|---|---|---|---|---|
| /64 | 1 | 2 000 ₽/mo | 3 500 ₽/mo | one project, up to 5 000 working addresses |
| /48 | 65 536 | 6 000 ₽/mo | 9 000 ₽/mo | scrapers, checkers, anti-detect browsers up to 1 000 profiles |
| /36 | 268 million | 15 000 ₽/mo | 20 000 ₽/mo | SEO software, SERP tracking, multi-threaded automation, agencies |
| /32 | 4.3 billion | on request | on request | data teams, resale, own ASN |
- Without rotation: the block is routed to your server (GRE/SIT tunnel or BGP announcement), set up within 1 business day. VPS with a preconfigured proxy server: plus 900 ₽ per month.
- Rotating with sticky sessions: the block stays on our gateway, you get one proxy address, a login with parameters and up to 3 000 threads. Modes are described below.
- Subnet-aware rotation: platforms ban whole /64 blocks, so in /48 and /36 the addresses are drawn from different /64s.
- Geo: Russia, Netherlands, Germany, USA. Clean subnets registered to our legal entities in RIPE.
Single addresses and ready-made packages up to 10 000 pcs are in the table above, and the shared rotating pool without a dedicated block is on the rotating proxies page.
Rotating IPv6 with an address pinned to each profile
The rotation gateway runs on top of a dedicated /48 or /36 block or on top of the shared pool. You get one address, gw.proxyfarm.ru:9100, a login and a password, and set the mode right in the login. This is how your anti-detect browser, scraper or BAS works without proxy lists: one proxy for the whole project, yet every profile or thread has its own address.
| Login | What happens | Best for |
|---|---|---|
| user-rotate | new random IPv6 on every connection | scraping, checkers, SERP tracking |
| user-session-profile17 | address pinned to the session ID forever | anti-detect profiles, accounts, BAS threads |
| user-session-profile17-ttl-30 | address held for 30 minutes, then changes | long sessions with periodic change |
| user-list-200 | export of 200 static ip:port entries from the block | software that requires a proxy list |
Address pinning works without a database: the IPv6 is computed from the session ID within your block, so the same ID always yields the same address, even a year later. Each session lands in its own /64 subnet: platforms block IPv6 precisely by /64, so neighbouring profiles never affect each other.
| Gateway plan | Price per month | Pool | Threads | Traffic |
|---|---|---|---|---|
| Shared rotating IPv6 pool | 1 490 ₽ | 10 000+ addresses, shared /64s | up to 500 | unlimited |
| Dedicated rotating /64 | 3 500 ₽ | your own /64 | up to 300 | unlimited |
| Dedicated rotating /48 | 9 000 ₽ | 65 536 of your own /64s | up to 1 000 | unlimited |
| Dedicated rotating /36 | 20 000 ₽ | 268 million of your own /64s | up to 3 000 | unlimited |
Gateway geo: Russia, Netherlands, Germany, USA. You do not need an IPv6 stack on your side: you connect to the gateway over IPv4 and traffic exits with an IPv6 from the block.
How to connect IPv6 proxies in BAS and ZennoPoster
For BAS, ZennoPoster and browser automation the gateway looks like an ordinary SOCKS5 proxy with authentication, so your software needs no IPv6 support of its own.
- In the project settings add one proxy: gw.proxyfarm.ru:9100, type SOCKS5, password from the dashboard.
- In the login field insert the thread or account variable: user-session-{{thread_id}} or user-session-{{account_login}}. Each thread gets its own pinned address that survives restarts.
- For scraping tasks in the same project use the login user-rotate: a new address on every connection.
- Enable remote DNS (socks5h mode) in the proxy settings so DNS queries go through the gateway rather than from your IP.
- Check the exit address on the My IP page from a BAS thread: it should show an IPv6 from your block.
The number of threads is not tied to the number of proxies: 500 threads go through one gateway and each gets its own address. Older BAS versions that cannot use IPv6 on the exit side work just the same, because the IPv6 connection is opened by the gateway, not the client.
Where IPv6 proxies work and where they do not
Before buying, check the target site: the command nslookup -type=AAAA domain shows whether it has an IPv6 address. If there is no record, you need IPv4 proxies.
| Platform | IPv6 | What to take |
|---|---|---|
| Google, YouTube, Gmail | yes | IPv6 |
| Facebook, Instagram, Threads | yes | IPv6 or mobile |
| Wikipedia, GitHub, Cloudflare sites | yes | IPv6 |
| Yandex | partially | regional IPv4 |
| Avito, VK, Ozon, Wildberries | no | IPv4 or mobile |
| Telegram, WhatsApp | partially | IPv4 SOCKS5 |
Why different subnets matter
Platforms block IPv6 not by single address but by whole /64 blocks, because that is what an ISP assigns to a subscriber. If all your addresses come from one subnet, a single block takes out the entire package. That is why from 100 addresses we issue 10 per /64, and from 10 000 we spread them across different /48s and different datacenters.
Typical tasks
- Google and YouTube scraping. SERPs, suggestions, Google Shopping prices, comments.
- Checkers and validators. Email, domain and page availability checks at scale.
- Registrations and warm-up. On IPv6-enabled platforms one address per account costs 12 ₽ instead of 79 ₽.
- SEO tools. A-Parser, Key Collector for Google, ScrapeBox.
For high-volume jobs with no address binding, rotating proxies are more convenient: one port and a new IPv6 on every request.
IPv4 or IPv6: how to choose
IPv4 is universal and works everywhere; IPv6 is 5–7 times cheaper but works only where it is supported. Check the platform and estimate the volume: below 20 addresses the savings are negligible, from 100 addresses IPv6 saves tens of thousands of rubles a month. If in doubt, ask support in Telegram and we will suggest the right type for your platform.
FAQ
Which is cheaper: single addresses or a block?
Up to 1 000 addresses, singles or a package are cheaper. From several thousand addresses, and for tasks that need addresses from different /64s, a block wins: a /48 for 6 000 ₽ gives 65 536 subnets, a /36 for 15 000 ₽ puts practically no limit on the number of addresses. The rotating version with sticky sessions on our gateway costs 9 000 and 20 000 ₽.
Can an IPv6 be pinned to a profile forever?
Yes. Put a session ID in the login, for example user-session-profile17: that ID always returns the same address from your block. The address lives as long as the profile does and changes only if you change the ID.
Does the gateway work with BAS?
Yes. BAS sees an ordinary SOCKS5 proxy with a login and password. Insert the thread or account variable into the login and every thread gets its own pinned IPv6. Enable remote DNS in the proxy settings.
Why does an IPv6 proxy not work with a site?
The site has no IPv6 address. Check with nslookup -type=AAAA domain or in the proxy checker. Such sites need IPv4.
Are the addresses dedicated?
Yes, every address is issued to you alone and stays static for the whole term.
Can I get rotation?
Yes, on any package from 100 addresses: one entry port, a new address on every request or by timer. The surcharge is 20 % on top of the package.
How do I use IPv6 proxies if I have no IPv6?
You do not need it: you connect to our gateway's IPv4 address and traffic exits over IPv6. IPv6 support from your ISP is not required.
Do I need my own server for an IPv6 block?
No. Take a rotating block: it stays on our gateway and you get one proxy address with control through the login. Or take a block without rotation together with our VPS for 900 ₽ per month with the proxy server already configured. If you have a server, we route the block to it via tunnel or BGP.