An IP, a connection and a session differ
A TCP connection is a transport object. A proxy session may request affinity to an exit. Browser cookies and application login are separate state. Ten session identifiers do not prove ten distinct IPs, and ten allocated IPs do not promise ten concurrent sessions.
Sticky does not always mean strict
A sticky mode generally requests continuity for a period, but an unavailable exit can end it. Strict affinity requires an explicit service contract that fails rather than silently rotating. Do not infer strictness, maximum duration or fallback behavior from the word sticky.
Rotation belongs to the service
Rotation can happen per request, session or allocation depending on the service. Use only documented controls on the allocated endpoint. No public builder here provisions sessions or adds provider-specific username tokens. An allocated ISP set is not automatically a rotating residential pool.
Design recovery deliberately
Keep cookies isolated per workflow, set timeouts and bound retries. If stable identity is necessary, stop on continuity loss and restart the authorized workflow explicitly. Confirm session duration, concurrency and replacement policy before purchase rather than relying on a format example.