Static and Rotating describe how a proxy assigns IPs, not what protocol it speaks. The same SOCKS5 can be either static or rotating — the difference is whether it gives you the same IP every time or changes it. This single property determines pricing, antifraud survival, and how convenient multi-account work is.

What Static IP proxies are

Static IP (sometimes "sticky" or "dedicated") — the proxy returns the same external IP. Every request through 1.2.3.4:8080 exits as the same 5.6.7.8. That 5.6.7.8 is locked to you for the rental period (usually a week or month) and nobody else uses it while you pay.

ISP proxies belong here too — they look residential but are actually static (an IP rented from an ISP that has a residential ASN). And so do Datacenter Static proxies — the cheapest option, IPs from a data center.

What Rotating IP proxies are

Rotating (also "backconnect") — the proxy changes its outgoing IP. Most commonly: you connect to one gateway (gw.provider.com:7000) and the provider swaps the exit IP from a pool on every request, or every N minutes.

Sometimes rotation is "sticky": "sticky 10 minutes" means a session through one gateway uses one IP for 10 minutes before switching. That's useful for logins — log in, the IP doesn't switch, the cookie binds to a single IP.

How rotation works under the hood

Two architectural patterns dominate:

  • Backconnect gateway. One gateway IP, behind it a pool of thousands or millions of exit nodes. The provider handles distribution. Pretty much every residential network works this way (Bright Data, Oxylabs, Smartproxy, etc.).
  • List of IPs with client-side rotation. You get N static IPs, rotation happens in your code (random or round-robin). Less common, but gives more control.

Geo targeting on rotating networks is usually done via query params or separate ports: port 7777 = US, port 7778 = DE. Or via user suffix: user-country-us:password@gw:7000.

When to use Static

Multi-account. If you have 50 accounts on Instagram/TikTok/eBay — each one needs its own permanent IP. Antifraud watches stability — an account logging in from a new IP every time looks suspicious. One account = one Static IP, for years.

IP-bound logins. If a site remembers the user's "usual" IP and triggers a verification code on a new IP — Static is required.

SEO tools, ad accounts, banks. Anywhere the IP is part of the account's "identity."

When to use Rotating

Web scraping. Goal: collect data from thousands of pages without bans. A million requests from one IP per hour = ban. From a million different IPs — fine. Rotating residential pools are the industry standard for serious scraping.

SERP scraping (Google, Yandex). Rotation and residential are mandatory — otherwise CAPTCHA on the third request.

OSINT and availability checks. "Is our site visible from 50 different countries?" — best done via geo-targeted rotation.

Sneaker bots, drop pages. When you need 1,000 parallel requests from unique IPs — only rotation works.

How to detect the type in your list

Simple way — make 3–5 sequential requests through the proxy and compare outgoing IPs:

for i in 1 2 3 4 5; do
  curl --socks5 ip:port -m 5 https://api.ipify.org
  echo
done

Same IP every time — Static. Different — Rotating.

ProxyLab does this automatically: each check fires a few parallel probe requests and the Static/Rotating type shows up directly in the result.

Pricing: which is more expensive

Rough ballpark for 2026:

  • Datacenter Static — $1–3 per IP/month. Cheapest.
  • Rotating Datacenter — $5–15 per GB. Cheaper than residential, but Datacenter is detected immediately.
  • ISP / Static Residential — $2–8 per IP/month. Looks residential, priced like premium Datacenter.
  • Rotating Residential — $5–15 per GB. Most expensive, but most "trusted" by antifraud.
  • Mobile (4G) — $50–200 per IP/month or $30–100 per GB. Top tier, but the cleanest IPs available.

Pricing is usually monthly per IP for static, or per-GB for rotating.

Related: Datacenter / Residential / Mobile, Anonymity levels, SOCKS5 vs HTTP.