Static ISP pool sizing starts with a question most teams ask in the wrong order: how many IPs should we buy? The better order is: how many identities must never change address, how quickly do addresses die, and how much slack absorbs that loss without a support ticket. Static ISP proxies are billed per address every month, so each IP you hold needs a named owner — an account, a session group, or a workflow that would break if the exit changed overnight.

Get the number wrong in either direction and the cost is real. Too few addresses and your automation queues behind a checkout flow that holds one login at a time; too many and a third of the invoice pays for idle numbers that look impressive on a dashboard and do nothing. Below is the formula, two worked examples, the crossover point where rotating residential is genuinely cheaper, and the mixed architecture most mature teams end up running.

What a static ISP address is actually for

  • Identity continuity. A static ISP address is residential-quality — registered to a consumer ISP, hosted in a datacenter — but it stays yours for as long as you pay. That permanence is the product.
  • Accumulated trust. Marketplaces, ad platforms and messenger apps build a reputation file per account, and that file is quietly welded to the address the account logs in from.
  • Predictable concurrency. One static address realistically supports one strong session at a time. Pushing five accounts through it is a flag, not a saving.
  • Auditability. When a client asks which exit their account used last Tuesday, a tagged static pool answers in one line. A rotating pool answers with a log query and a shrug.

Static ISP pool sizing: the formula

The working formula is short, and the honest version has three terms rather than two:

Pool = (Active identities x peak sessions each) + (Replacement headroom 15-25%)

Most teams count identities and forget that one identity can hold several parallel sessions. Collect six numbers before you buy anything:

  1. Active identities — accounts that never rotate. Count reputation files, not people: one operator with three seller accounts is three identities.
  2. Peak concurrent sessions per identity — if three internal workflows touch the same account at 09:00, that identity needs three exits or a queue.
  3. Session lifetime — a 40-minute checkout session and a 30-day always-on session create completely different replacement pressure.
  4. Observed churn — how many exits were blocked, geo-mismatched or degraded in the last 30 days? Your own logs set headroom better than any blog percentage.
  5. Contract terms — a provider that guarantees replacement within 24 hours needs less spare capacity than a best-effort block.
  6. Growth plan — new accounts per month, because ordering twice in a quarter usually costs more than sizing once with room to grow.

Comparison

WorkloadStatic IPs neededRotating residential fit
Always-on accounts (marketplace, messenger, ad)1 per identity plus 20% headroomPoor — a changed exit triggers re-verification
Burst sessions (checkout, booking, review)1 per concurrent session, reused across the dayFair — only when sessions are disposable
Public scraping and price monitoring0-2 for control trafficStrong — cheaper per unit of work

The mixed strategy that beats a pure static pool

After the first invoice shock, most teams split the workload. The static core holds only identities: seller accounts, ad accounts, messenger sessions, anything with a reputation file worth protecting. Everything else — public scraping, price monitoring, bulk research, one-off verification — goes through a rotating residential layer billed per gigabyte. The split is not a matter of taste; it is a question of which traffic punishes address changes. A static IP is justified when a rotation would cost you an account, a review, or a client. When rotation costs you nothing measurable, paying a monthly fee for permanence is simply the more expensive way to buy the same page. Keep that static core small, documented and reviewed monthly, and let the rotating layer absorb every workload that does not care where its exit sits.

How to size your static ISP pool (step by step)

  1. Freeze the identity list. Export every account that must keep its exit for more than a week and give each one an owner.
  2. Size by identity, then by concurrency. Forty client accounts that never rotate at 20% headroom: 40 x 1.2 = 48 IPs.
  3. Add burst capacity. Twelve always-on accounts plus 20 parallel checkout sessions, 20% headroom: (12 + 20) x 1.2 = 39 IPs.
  4. Order in blocks, not singles. Contiguous blocks make replacement and tagging far easier, and providers price them better.
  5. Tag every address. Purpose, owner, order date, replacement due date. An untagged static IP is how a bill quietly doubles.
  6. Re-measure monthly. Compare blocked exits and idle addresses; trim or extend on evidence, not on a hunch.

Common mistakes

  • Sizing by account count only. Parallel sessions and duplicate identities are what actually exhaust a pool.
  • Buying zero headroom. When an ISP reclaims a block or an address gets banned, you either swap it or rebuild the identity. The second option costs far more.
  • Using static IPs for volume scraping. Flat per-IP pricing loses badly to per-GB rotating residential when the workload does not punish rotation.
  • Skipping verification. A static address can still degrade or leak; how to test a proxy covers the checks worth running, and you should repeat them after every replacement.

FAQ

How many static IPs do I need for 40 accounts?

Forty always-on identities with 20% headroom gives 48 addresses. If each account also runs two parallel sessions at peak, the real requirement is closer to 96 — or 48 addresses plus a queue that serialises the second session.

Why 15-25% headroom if the addresses are static?

Static describes the contract, not immortality. ISPs reassign blocks, targets block addresses, and some addresses arrive already tainted. Headroom is the difference between swapping an exit in ten minutes and rebuilding a warmed account for two weeks.

Is static ISP cheaper than rotating residential?

Only per identity. Static is a flat monthly fee and rotating is metered per gigabyte, so for public scraping, monitoring and one-off research the rotating pool usually wins by a wide margin. The rotating vs sticky guide explains how to model that cost against a real request mix instead of a price table.

How should I organise and tag static IPs?

Use a naming scheme that encodes purpose, owner and order date, for example shop-eu-01-acct-0042. Keep the mapping in a spreadsheet or database your team can query, and treat an untagged address as a defect to fix before the next invoice.

Pool sizing is not a one-time purchase decision; it is a monthly reconciliation between identities, churn and cost. Start with the formula, verify every new exit before it touches a logged-in account, and revisit the rotating layer whenever the workload changes shape. If you would rather skip the block negotiation, FTProxy residential proxies offers static ISP addresses with documented replacement terms and per-address tagging built in.