Vaultproxies
IPv6 datacenterOur own /40

Unlimited IPv6, no meter running.

$3.00 a day, flat, with no bandwidth cap and nothing to top up. The same /40 subnets we announce on our own AS218876 from our gates in the US and Europe. Pick a subnet per line to pick the country, 2⁸⁸ addresses per /40 to rotate through, no thread limit on our side, and full UDP so QUIC and HTTP/3 just work. Need another country? Add a private pool geolocated to any country.

2⁸⁸
Addresses per /40
AS218876
Our own ASN
24h
Max sticky
US · EU
Locations
Two plans
Starting price
$3.00/ day
No bandwidth cap and no meter. Or $0.15 / GB if you would rather pay for what you use.
No GB counter, ever
No thread or connection limit
HTTP :30 · SOCKS5 :31 · full UDP
1 Gbps port, no thread limit
Sample exit addresses
2a10:fa81:17a3:9f2c::e41b
US gate · a US subnet · AS218876
2a10:fa81:16b7:4d81::a92f
EU gate · a Netherlands subnet · AS218876

Read this first: the pool is IPv6-only

Every address here is IPv6, so your destination must publish an AAAA record. An IPv4-only target simply cannot be reached on this product - there is no v4 fallback. Most large sites are dual-stacked and will be reached over v6, but check yours before you buy: if your targets are IPv4-only, Datacenter Per GB or Residential is the plan you want. One request against https://ipv6.icanhazip.com tells you where you stand.

Subnets and locations

Our own /40s, by country.

Every subnet is our own prefix, announced on AS218876 and labelled with its country in our public geofeed. You pick one per line, so the subnet you pick is the country you leave from.

What a /40 is

A /40 is one block of 2⁸⁸ IPv6 addresses:

309,485,009,821,345,068,724,781,056

Each line rotates inside its subnet, so a new address on every request does not realistically repeat, however long the job runs.

Threads
No limit on our side. Open as many concurrent connections as your job needs, on either plan.
Protocols and ports
HTTP on :30, SOCKS5 on :31, same credential. UDP rides SOCKS5, so QUIC and HTTP/3 work.
Rotation
Rotating by default: a different address from your subnet on every request.
Sticky sessions
-sess-<id>-life-<seconds> holds one address for up to 24 hours, then rotates. -end-die stops it instead.

How location works. A subnet's country comes from our published geofeed, which IP databases read on their own schedule, so a change can take a few days to show everywhere. The exit server is the gate that announces the subnet (our gates in the United States and Europe), so latency is measured from there, not from the country on the label.

Several countries at once

One plan, a line per country.

Each line is pinned to one subnet by adding -subnet-<id> to the username. Generate one line per subnet and run them side by side on the same plan. The dashboard generator lists every subnet you can use and writes the token and the right gate host for you.

  • Same username and password on every line
  • A subnet lives on one gate: use that gate's host
  • No token: the gate's default subnet
  • Combines with -sess- and -life- for sticky lines
Pythonone line per subnet
# One plan, one line per country. Same password on every line.
# -subnet-<id> picks the subnet; each subnet lives on one gate, so the
# line dials that gate's host.
US = "http://USER-subnet-<id>:[email protected]:30"
EU = "http://USER-subnet-<id>:[email protected]:30"
Why this pool

Our prefix, our ASN.

Our own /40 subnets on AS218876, announced by us and served from our gates in the US and Europe.

2⁸⁸ addresses per /40

Every subnet is a /40, 2⁸⁸ addresses, and each line rotates inside its own. Rotation is effectively infinite: an address does not realistically repeat, however long the job runs.

Announced on AS218876

Every subnet is our own BGP-announced prefix, labelled with its country in our public geofeed. The gate binds a source address out of it and connects straight to your destination.

No thread limit

Open as many concurrent connections as your job needs, on either plan. There is no cap on threads or sockets to work around.

Full UDP

QUIC and HTTP/3 work. UDP egresses from the same pool address as your TCP connections, so a sticky session stays coherent across both.

Pricing

Two ways to buy the same pool.

Same prefixes, same gates, same rotation. The only difference is how the meter runs.

Best value
Flat rate

Unlimited

$3.00/ day
  • Minimum 1 day, up to 365
  • No bandwidth cap at all
  • No thread or connection limit
  • Rotating, or sticky up to 24h
  • HTTP :30 · SOCKS5 :31 · full UDP
Metered

Per GB

$0.15/ GB
  • Minimum 1 GB per top-up
  • Bandwidth never expires
  • Same /40s, same direct path
  • Cheaper under ~20 GB a day
  • See the per-GB plan

Per-GB bandwidth sits on your account until you use it, there is no expiry clock. Unlimited bills by the day, from one day up.

Per GB or unlimited?
$3.00 a day unlimited is 20 GB a day at $0.15/GB.

Below 20 GB a day, per GB costs less. Above it, unlimited does: at 100 GB a day, per GB is $15.00 a day ($450.00 per 30 days) against $3.00 a day ($90.00) unlimited.

Traffic per dayPer GBUnlimitedCheaper
5 GB$0.75 / day$3.00 / dayPer GB
20 GB$3.00 / day$3.00 / daySame
100 GB$15.00 / day$3.00 / dayUnlimited
500 GB$75.00 / day$3.00 / dayUnlimited
Drop-in

One endpoint, both protocols.

Standard user:pass auth against one host per region. Rotation is the default; session behaviour is spelled out in the username, so nothing about your client has to change.

  • gate-us.vaultproxies.com:30 · :31 · US gate
  • gate-eu.vaultproxies.com:30 · :31 · EU gate
  • -subnet-<id> · pick the subnet, so the country
  • -sess-<id>-life-<seconds> · up to 86400
  • -end-die · stop instead of rotating
Pythongate-us.vaultproxies.com · gate-eu.vaultproxies.com · :30 :31
import requests

# One endpoint, both protocols. HTTP on :30, SOCKS5 on :31.
# The gate binds a source address out of one of our own /40 subnets,
# announced on AS218876, and connects straight to your target.
HTTP   = "http://USER:[email protected]:30"
SOCKS5 = "socks5h://USER:[email protected]:31"

# Pick the country with -subnet-<id> (see Subnets and locations above).
# Each subnet lives on one gate, gate-us or gate-eu: dial that gate's host.
# Same credential, same ports. No token: the gate's default subnet.
PICKED = "http://USER-subnet-<id>:[email protected]:30"

# Rotating by default: a different source address on every request.
# Note the target: it must publish an AAAA record.
r = requests.get("https://ipv6.icanhazip.com",
                 proxies={"http": HTTP, "https": HTTP})
print(r.text.strip())   # -> an address out of the US gate's default /40

# Sticky: hold one address for -life- seconds, up to 86400 (24h).
# When the timer runs out the session rotates to a fresh address and
# keeps working. That is the default: end-rotate.
STICKY = "http://USER-sess-a1b2c3d4-life-3600:[email protected]:30"

# -end-die stops the session at expiry instead of rotating. The
# credential is refused once the timer is up, so nothing silently
# continues from a different address mid-sequence.
ONESHOT = "http://USER-sess-a1b2c3d4-life-600-end-die:[email protected]:30"

# The same tokens work on SOCKS5 on :31, and UDP is carried end to end,
# so QUIC and HTTP/3 leave from the same address as your TCP connections.
200 OK · our /40 · AS218876Our /40
What it's good for

When the target speaks v6.

Dual-stacked CDN targets

Sites behind Cloudflare, Fastly, Akamai or Google commonly publish AAAA records. Where they do, the endpoint is reachable over v6 and the whole pool is in play.

All-day scraping

A scraper that runs continuously is exactly what the flat daily rate is for, past roughly 20 GB a day it costs less than metering the same traffic.

High-frequency polling

No thread or connection limit, so an inventory watcher or price monitor can fan out as wide as your machine allows.

Sequenced jobs

Hold one address with -sess- for as long as the sequence takes, and use -end-die so it stops rather than continuing from a different IP.

Very wide rotation

2⁸⁸ addresses in each /40 subnet. Per-request rotation across a pool that size means repeats are not a practical concern.

QUIC and HTTP/3 work

UDP is carried end to end, so v6 services that only speak QUIC, and HTTP/3 endpoints generally, are reachable from the same session.

Pick the right tool

IPv6 Datacenter vs. the rest.

The deciding question is not price, it is your target list. If your destinations publish AAAA records and do not score you on ASN reputation, this is the lowest per-gigabyte plan we sell and the widest pool we have. If either of those is false, another plan fits better, so here is the honest map.

IPv6 Datacenter
Pick when
IPv6-capable targets, high throughput, no thread limit, QUIC / HTTP/3, sticky up to 24h
Trade-off
IPv6-only, an IPv4-only destination cannot be reached, and the addresses read as datacenter
IPv6 Residential
Pick when
US IPv6 targets that judge you on how consumer the address space looks
Trade-off
US only, rotating only, no targeting, a higher per-GB price and no flat daily option
Datacenter
Pick when
The same throughput profile against IPv4-only targets and public APIs
Trade-off
Easily fingerprinted on protected commerce and social sites
Residential
Pick when
Targets that block datacenter ASNs outright, or when you need country / city targeting
Trade-off
Higher per-GB cost

Estimate your bill

Drag the slider. Billed per day, 1 day minimum.

Days running
7days (168h)
11530
Estimated total
$21.00
$3.00 / day·unlimited bandwidth

Billed by the day. Final amount is confirmed at checkout.

FAQ

IPv6 Datacenter, straight up.

How a request leaves, how sessions behave when the timer runs out, and the one target type this pool cannot reach.

Every byte. There is no bandwidth cap, no fair-use meter and no throttle on this plan: you pay for the days the plan is active, not the traffic that moves. The pool, the gates and the prefixes are identical to the per-GB plan, so nothing about performance changes when you switch, only the meter.

Point it at your own targets.

Start at $0.15 a gigabyte with a 1 GB minimum, or $3.00 for a day of uncapped bandwidth. If a target turns out not to be IPv6-capable you will know inside one request.