Static IPv6 proxies

Static IPv6 proxies come from datacenter networks and provide fixed IPv6 exit addresses for IPv6-enabled target services. IPv6 describes the address protocol; it does not establish residential origin or compatibility with every website.

Check compatibility first

• Target service: The actual domain or API endpoint must support IPv6. Endpoints on the same platform can differ.
• Client: Enter the IPv4-formatted host, protocol-specific port, and credentials from your dashboard.
• Connection versus exit: The client connects using IPv4-formatted details; the target sees the assigned IPv6 exit. Do not replace the connection host with the exit address.

Review current specifications on the product page and in your dashboard, and validate with the actual target. For IPv4-only targets, consider another suitable product.

Suitable workloads

Use cases include access to IPv6 services, dual-stack app testing, and IPv6-compatible batch jobs. Choose location, quantity, bandwidth, and rental period based on the workload. Current pricing and availability appear on the purchase page.

Setup and verification

Open the IPv6 product list in your dashboard. Once deployment is complete, select a supported protocol and copy the connection details. Enter the IPv4-formatted host, matching port, and credentials in your app. Save, verify the IPv6 exit in that same app, then test the target service.

Follow getting started for the full workflow. Recheck the port when switching between HTTP and SOCKS5; do not use the IPv6 exit address as the connection host.

Connection troubleshooting

If an IPv6 exit lookup works but the target fails, check its IPv6 support and access rules. If lookup also fails, check connection settings and resource status first.

See connection troubleshooting in the FAQ and the IPv6 FAQ.