Sticky sessions and why they matter

A sticky session keeps one outbound address for a while. A login wants that. Cookies, device checks, and risk engines assume the street did not jump between clicks. This page is that continuity note. It covers residential sticky time because that is the product people buy for profiles. A second sticky URL is not required.

Authorized work only. Sticky time does not authorize an account you do not own. It does not undo a disable. Rotating proxies break logins is the sibling. This page is the positive form: keep the path still.

The note lives under Proxies.

What "sticky" means on a provider dashboard

You get a session ID or a sticky hostname. For 10, 30, or 60 minutes (sometimes longer), requests through that credential should exit the same IP. After the timer, you may get a new IP. Some static ISP lines are sticky until you change the product. Those are not the same SKU.

I do not need two sticky URLs for one profile. One line, pasted once, is the setup. Proxies in an antidetect browser is how MaskWright attaches it. Proxy auth formats if the username carries the session ID.

Why logins care

A bank, an ads manager, a storefront admin: they see IP as one of several signals. Jumping from Frankfurt to Miami mid-session looks like a stolen cookie, a CGNAT mess, or a bot. It also looks like you rotated on purpose.

I am not going to claim a still IP "protects" an account. I am saying a moving IP under a cookie store is a hygiene failure you can avoid.

Check the exit IP at the start of work and after a reconnect. Geo matching should follow that still exit, not yesterday's city.

Leaks that undo sticky

DNS that still resolves on the house resolver. DNS leaks on Windows. IPv6 AAAA that bypasses the proxy. IPv6 leaks. WebRTC local candidates. A system VPN fighting the per-profile line.

Sticky on paper, house IP on the side, is worse than a honest household connection. Bring-your-own ethic: we do not sell the line, so we also do not pretend we can make a sloppy Windows network stack behave.

If the provider's "sticky" still hops every few minutes, that is a pool problem. Test it. Do not argue with a dashboard that says 30 minutes if your lookup page says otherwise.

How I set it in practice

Pick a session length longer than the sitting. If I work an ads account for two hours, a 10-minute sticky is a trap. Some providers let you pin until you drop. Prefer that for logins.

Do not refresh the session ID every launch unless you want a new IP. Launch the same profile with the same sticky credential.

When the sitting ends, close the profile. Do not leave a headed browser up overnight on a timer unless you meant to. Sticky time is for a person in the chair.

Numbers I actually use

A two-hour ads sitting gets a sticky length of at least that, preferably "until I drop." A 10-minute sticky on a 90-minute job is how people think they rotated by accident. I paste the same session ID every launch that day. I do not generate a new username each time unless I wanted a new IP.

When sticky expires mid-sitting, I finish the thought, close the profile, and start a new sitting with a fresh check of the exit. I do not keep clicking through a hop and hope the dashboard ignores it.

ISP static lines do not need this timer talk. If you bought still, do not encode rotate in the user field. Read the provider's sticky docs once. Then verify with two lookups an hour apart.

FAQ

Is sticky the same as a static ISP proxy?

No. Sticky is a timer on a pool. Static ISP is usually one address until you change the product. Different SKUs, different invoices.

How long should sticky be?

Longer than the sitting. If you do not know, start with the provider's longest login-oriented option and verify with a lookup page.

Can MaskWright force an IP to stay?

No. We send traffic through the line you pasted. The provider owns the pool. We do not broker.