Static ISP Procurement

Static ISP bulk pricing: graduated tiers and the math behind them

The first version of the 140-IP order sheet used the wrong formula. This is what the corrected sheet looks like, and why the count changed too.

Static ISP proxies Bulk order math Updated 2026-06-12

Graduated pricing applies per bracket, not per order

Static ISP lines at Proxynade are priced by IP count with bandwidth included. The pricing is graduated: each tier bracket applies only to the IPs that fall within it. The basket starts at 5 IPs and steps down as the order grows: 5–24 at $2.00, 25–49 at $1.73, 50–99 at $1.50, 100–199 at $1.40, and 200+ at $1.30.

That distinction matters when building an approval sheet. A common mistake is to find the tier for the total quantity and multiply the full count by that rate. It produces the wrong number.

bulk-isp-028, copied from approval sheet
requested: 140 Static ISP IPs
bad math: 140 * 1.40 = 196.00

graduated math:
24 * 2.00  = 48.00
25 * 1.73  = 43.25
50 * 1.50  = 75.00
41 * 1.40  = 57.40
total       = 223.65
effective  = 1.5975/IP

The same graduated formula gives $167.65 at 100 IPs, $307.55 at 200 IPs, and $697.55 at 500 IPs. Those numbers end up in approval threads, renewal notes, and client cost splits, so they are worth computing correctly before the sheet leaves your hands.

Verify the count before pricing the tiers

The 140-IP request came from 118 active account lines, 12 warmup slots, and "some spare." I asked for the spare list. Six were documented failover lines with a designated backup role. Four had no owner, no client, and no replacement rule.

count accepted later:
118 active account lines
8 warmup lines
6 documented failover lines
4 unassigned lines, removed

approved order: 132 IPs
reason: every spare IP had an owner and a replacement rule

Moving from 140 to 132 saves the cost of 8 IPs at the 100–199 tier rate. The larger point is that ownerless reserve IPs do not become cheaper just because a higher tier is in play. They are waste at any price.

Static ISP fits persistent exits, not rotation

Static ISP makes sense when the workflow needs a fixed IPv4 exit IP tied to a specific account, dashboard, or long-running session: ecommerce seller tooling, client accounts, platform profiles where an IP change triggers a trust check against IP reputation lists. The unlimited bandwidth model means the cost is the monthly per-IP charge, not a GB meter.

It does not make sense for a scraper that can rotate freely, a one-week test, or a team that has not yet assigned accounts to IPs. In those cases, Volume Residential at $0.89/GB or Datacenter is likely cheaper for the actual work being done.

Unlimited bandwidth does not mean zero waste

Static ISP lines are not billed by the byte, but sessions that loop through login prompts, reload media on every check, or poll a dashboard every minute still consume capacity. The cost shows as idle IP count and unnecessary session wear rather than a line item on the bandwidth bill. The dashboard network logs show host, outcome, latency, and byte totals per session, which is enough to spot a loop.

Procurement checks before the order

  • Price the exact graduated basket, bracket by bracket.
  • Map every IP to a named account, workflow, or documented failover role.
  • Remove reserve lines that have no owner and no replacement rule.
  • Confirm a renewal owner exists before submitting.
  • Check whether a smaller order at a higher per-IP rate is still cheaper than unused IPs at a lower rate.

Static ISP bulk pricing FAQ

How does the graduated tier pricing work? Each tier bracket applies only to the IPs that fall within it. The first 24 IPs cost $2.00 each, the next 25 cost $1.73 each, and so on. The total is a sum across brackets, not a flat rate on the full count.

Does unlimited bandwidth mean I can ignore traffic volume? Billing does not charge per GB on Static ISP lines, but sessions that loop through login prompts or reload media still waste capacity. The cost shows up as idle IP count rather than a bandwidth overage.

When does a bulk Static ISP order make sense? When each IP maps to a specific account or workflow with a documented owner and replacement rule. If spare IPs have no assigned use, the smaller order is cheaper.

What should I verify before submitting a bulk order? Price the exact graduated basket, map every IP to an account or workflow, remove unassigned reserve lines, and confirm a renewal owner exists for the order.