IP pinning on IPv6 plans (-identifier-)

The -identifier- tag pins an exit IP deterministically: each identifier value works like an ID for one exit IP, so the same identifier always resolves to the same IP, with no session to start, hold, or expire. The pin holds across processes, machines, or restarts, with no session state to coordinate. For the full username grammar, see the Username tag scheme.

#What -identifier- does: a static IP from the proxy pool

-identifier-<value> selects an exit IP by hashing the identifier value over the IPv6 ranges that match your plan and geo tags. Because the mapping is computed from the identifier rather than stored, the result is stable and stateless: the same identifier on the same plan with the same geo tags maps to the same IP, and the pin survives even when no session exists and across service restarts.

The client area generates each identifier value, for example mumcgy8tafa7dj0. The value works like the IP's ID, so copy it exactly as issued instead of writing your own. To get more stable IPs, generate more lines in the client area: each line carries its own identifier.

This tag is also what powers the client area's FOREVER option on the IPv6 plans: the generator emits an identifier-tagged username (no session/time tags), which holds the IP indefinitely with no window to expire.

The examples use the username format the client area generates: your service username (USERNAME below), then the generated identifier. Both IPv6 plans exit over IPv6, so the examples check the exit IP with the IPv6 echo endpoint api6.vipv6proxy.com:

# Datacenter IPv6: same identifier => same exit IP, every time
curl -x "http://USERNAME-identifier-mumcgy8tafa7dj0:PASSWORD@gw-2312.coldproxy.com:30000" \
  https://api6.vipv6proxy.com/api/checker/my-ip

# Residential IPv6: the same pattern with that service's username and identifier
curl -x "http://USERNAME-identifier-mq8hhadw1mbdj50:PASSWORD@gw-2312.coldproxy.com:30000" \
  https://api6.vipv6proxy.com/api/checker/my-ip

#How it differs from sticky sessions

Both approaches give you a stable IP, but they work differently and suit different needs:

Sticky sessions are the right choice for a bounded multi-step flow that should release the IP afterward, and they are how you hold an IP on the Residential IPv4 plans; see Sticky vs rotating sessions. On the IPv6 plans, -identifier- is the right choice when you want to keep the same IP indefinitely with no session bookkeeping.

#When to use it

Use -identifier- on Residential IPv6 or Datacenter IPv6 when you need to:

• Give each worker process or host its own generated username, so each keeps a consistent, stable IP without sharing session state.
• Re-attach to the same IP after a restart or redeploy without re-establishing a session.
• Keep a stable IP for one job (a workspace, a region task, a long-running job) for legitimate localization, QA, monitoring, or authorized testing.

On Datacenter IPv6, choose one of the listed locations in the client area generator, and the generated username carries the geo tags together with the identifier. Residential IPv6 covers the USA only (listed city location: Ashburn, USA), so this city example uses Datacenter IPv6:

# Datacenter IPv6: generated username pinned to Dallas, one of the listed US locations
curl -x "http://USERNAME-country-us-city-dallas-identifier-mumcgy8tafa7dj0:PASSWORD@gw-2312.coldproxy.com:30000" \
  https://api6.vipv6proxy.com/api/checker/my-ip

#Related reading

• Username tag scheme — the full tag grammar
• Sticky vs rotating sessions — session-based IP stability on every plan
• Residential IPv6 and Datacenter IPv6 — setup guides for the plans that support -identifier-
• Geo-targeting — pin within a target location
• IP rotation: rotating and sticky proxies explained
• Glossary: sticky session, rotating proxy