Datacenter IPv6 Connection Reference
Datacenter IPv6 uses dedicated, subscription-specific endpoints. Its public connection details are not the shared Residential IPv4 gateway: copy the exact encrypted endpoints shown for your subscription in the dashboard.
Connection contract
Section titled “Connection contract”| Setting | Value |
|---|---|
| Address family | IPv6 exits from infrastructure-hosted ranges |
| HTTP proxy | https://YOUR_ASSIGNED_HOST:443 |
| SOCKS proxy | socks5+tls://YOUR_ASSIGNED_HOST:YOUR_ASSIGNED_PORT |
| Authentication | The credentials or IP allowlist displayed for the subscription |
| Endpoint source | Dashboard subscription details |
| Direct public UDP associate | Not supported |
Plain SOCKS5 clients cannot connect directly to the encrypted SOCKS endpoint. Use a supported TLS-capable client or a local adapter/TLS wrapper as described in How to Connect.
Available locations
Section titled “Available locations”Datacenter IPv6 is available in ten cities:
- Amsterdam
- New York
- Los Angeles
- London
- Frankfurt
- Paris
- Tokyo
- Singapore
- Sydney
- São Paulo
Locations describe the published address geolocation. Confirm your assigned location in the dashboard and validate it against the destinations your application uses.
Compatibility first
Section titled “Compatibility first”Before scaling, confirm that the destination and client support IPv6, that the client uses the required encrypted proxy transport, and that the observed exit matches the assigned product. Treat target acceptance, concurrency, and retry limits separately from address allocation.