Direct Answer
A static proxy keeps the same IP for the whole session, so a login or multi-step flow stays consistent. A rotating proxy switches the IP across requests so each call looks like a different user. Static suits stateful, logged-in work; rotating suits high-volume, stateless requests like crawling many pages.
The Core Difference
Across the wider market, "static" and "rotating" are often sold as separate proxy products. With a dedicated mobile proxy they are simply a session mode on one endpoint: both run over the same host, port and credentials. What changes is how long one IP stays assigned to you:
- Static (sticky): one IP is held for the session, from a few minutes up to the whole job. State — cookies, a login, a shopping cart, a multi-step form — carries across every request because the server keeps seeing the same address.
- Rotating: the IP changes between requests, either on every call, on a timer, or on demand. Each request reads as a fresh visitor, which spreads a large request volume across many addresses instead of concentrating it on one.
The decision is almost always driven by one question: does the target need to remember you between requests? If yes, go static. If each request stands alone, rotation usually wins. The mechanism behind both is covered in depth in sticky sessions and IP rotation.
Static vs Rotating at a Glance
| Static (sticky) | Rotating | |
|---|---|---|
| IP per session | One, held | Changes per request / timer / on demand |
| State (login, cart, cookies) | Preserved | Broken on each switch |
| Best for | Logged-in flows, checkouts, multi-step forms | High-volume crawling of independent pages |
| Per-IP request rate | Higher (all traffic on one IP) | Lower (spread across IPs) |
| Typical use | Account-bound verification, session testing | SERP harvesting, product listings, catalogue crawls |
| Risk if misused | Single IP shows high request rate | Logged-in session drops mid-flow |
The split is clean: state-bound work needs a stable IP; stateless volume benefits from spreading load. Mixing them up is the most common cause of failed jobs — a rotating session that drops a login, or a static session hammering one IP far above a human rate.
When to Use Static (Sticky) Proxies
Use a static IP whenever the work depends on the server remembering you across requests.
- Logged-in or account-bound work. Anything behind a sign-in needs the same IP for the session — an IP change mid-session looks like the account jumped networks and tends to force a re-check.
- Multi-step flows. Checkouts, multi-page forms and any wizard where step 3 depends on step 1 need one consistent address from start to finish.
- Session-true testing. Verifying how a page behaves for a single returning visitor — personalised pricing, A/B variants, region-locked content — requires a stable identity.
- Authenticated API access. Where a token or session is tied to the originating IP, rotation invalidates it.
A real mobile IP makes static sessions especially robust: because the address is a high-trust German mobile IP shared by many genuine subscribers through CGNAT, a busy session reads as ordinary mobile traffic rather than a flagged single user.
Honest limit: with a static IP all your traffic sits on one address, so pace your requests to a human-plausible rate. A sticky session is not a licence to send thousands of requests per minute from one IP.
When to Use Rotating Proxies
Use rotation when each request is independent and you need to move at volume.
- Large-scale crawling. Fetching thousands of product pages, search results or public catalogue entries — none of which share a login — is the textbook case for rotation. Spreading requests across IPs keeps the per-IP rate low.
- SERP and rank tracking. Pulling search results across many queries reads more naturally when calls don't all originate from one address. See tracking Google.de SERPs with a German mobile proxy.
- Price and availability monitoring. Sampling many products or stores repeatedly benefits from fresh IPs per pass — practical detail in e-commerce monitoring with mobile proxies.
- Broad market and SEO research. Wide, shallow data collection across many pages, covered in market research and SEO analysis with mobile proxies.
Rotation does not increase raw throughput — a single request is no faster. What it does is keep a high-volume crawl healthy: lower per-IP request rate means fewer blocks and fewer retries, so the effective completion rate across a long run climbs even though individual requests are unchanged.
Honest limit: rotation breaks state. The moment your IP changes, any login or cart tied to the old address is gone. Never rotate inside a flow that must stay logged in.
How Rotation Is Controlled
With a mobile proxy, rotation is not magic in the background — you control it. Three common modes:
- On every request — each call gets a new IP. Maximum spread, only for fully stateless work.
- Time-based — the IP holds for a set interval (for example a few minutes), then changes. A middle ground: short stable windows within a larger rotating job.
- On demand — the IP stays fixed until you trigger a change yourself, typically via a rotation URL. This is the most precise: hold one IP for a flow, then rotate when that flow is done.
Because the same dedicated endpoint supports both sticky windows and on-demand rotation, one product covers both modes — you switch behaviour by how you call it, not by buying a second proxy. When rotation runs through a single gateway address that swaps the exit IP behind the scenes, that arrangement is a backconnect proxy. The transport stays your choice too: HTTP or SOCKS5, plus an OpenVPN config where you need the whole machine routed.
Choosing for Your Job
Work from the request, not the product:
- Does this request depend on a previous one (login, cart, token)? → Static. Hold one IP for the whole flow.
- Is each request independent and you need many of them? → Rotating. Spread the load across IPs.
- A bit of both — short stateful bursts inside a big job? → Time-based or on-demand rotation: sticky for the burst, rotate between bursts.
Most real scraping pipelines use both: rotating IPs to harvest a list of targets, then a sticky session per target where a flow has to stay consistent. A single dedicated mobile proxy handles that switch cleanly, which is why dedicated endpoints suit teams that run mixed workloads. For the wider proxy-type decision behind this, see mobile vs residential vs datacenter proxies.
Whichever mode you pick, use it for authorised work within each target's terms — public-data collection, your own accounts, testing you're permitted to run. Background on the legal frame: are mobile proxies legal and scraping legality in the EU.
FAQ
What is the difference between a static and a rotating proxy?
A static proxy holds one IP for the duration of a session, so cookies, logins and multi-step flows stay consistent. A rotating proxy changes the IP across requests, so each call appears to come from a different address. Static favours stateful work; rotating favours high-volume, stateless requests.
Are static proxies the same as sticky sessions?
Effectively yes, in practice. A sticky session is the mechanism that keeps one IP assigned to you for a set window (for example a few minutes up to the session's life), which is how a mobile proxy delivers static-style behaviour. Both terms describe holding one IP rather than rotating it.
When should I use rotating proxies for web scraping?
Use rotation when you fetch many independent pages that need no shared login or cart — product listings, search results, public catalogue pages. Spreading requests across IPs lowers the request rate any single address shows, which keeps a high-volume crawl stable.
Can one mobile proxy do both static and rotating?
Yes. A single dedicated mobile endpoint supports sticky sessions for stateful work and on-demand or time-based rotation for stateless work. You choose the mode per job by how you call the endpoint, without buying two separate products.
Does rotation make scraping faster?
Not directly — rotation does not raise raw throughput. It helps high-volume crawls stay healthy by keeping the per-IP request rate low, which reduces blocks and retries. Net effective speed often improves because fewer requests fail, but a single request is no faster.
Get Started
Need one endpoint that does both — sticky sessions and on-demand rotation? Browse real German mobile proxies at GermanProxy.io — dedicated or shared, HTTP/SOCKS5, fair-use 20 GB/day.
Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — compare German mobile proxy plans or start small with a shared 5G proxy.