Per IP versus per GB: choose the thing the plan actually meters

A per-IP plan charges for access to a number of addresses. A per-GB plan charges for traffic. Neither unit can be converted honestly into the other without knowing both the required address count and the traffic those addresses will use. The billing unit is therefore the first comparison choice, not a formatting detail beside the price. Dataset snapshot, all evidence retrieved 2026-07-25

Two similar totals that buy different things

Oxylabs sells shared datacenter proxies in both units. oxylabs-datacenter-shared-pay-per-ip-10-ips costs $12 per month for 10 IPs at $1.20 per IP. The row has no published per-GB allowance, so it is not comparable per GB. Oxylabs datacenter pricing, retrieved 2026-07-25T15:31:32Z

On the same vendor page, oxylabs-datacenter-shared-pay-per-gb-20-gb costs $11.80 per month for 20 GB at $0.59 per GB. That row does not promise a purchased count of 10 IPs. Oxylabs datacenter pricing, retrieved 2026-07-25T15:31:32Z

The checkout totals are close, but the receipts answer different questions. The $12 row is useful when the buyer’s requirement is 10 addresses and the unpublished traffic allowance is acceptable only after direct confirmation. The $11.80 row is useful when the requirement is 20 GB and the rotating pool supplies whatever addresses the product permits. Dividing the per-IP total by an assumed number of gigabytes would invent a rate the vendor does not sell. Oxylabs datacenter pricing, retrieved 2026-07-25T15:31:32Z

Most rows are not explicit per-GB offers

Of 710 plan rows in the current snapshot, 267 use the per_ip pricing model. Only 74 are explicit pay-as-you-go or tiered per-GB rows, and another 104 are monthly bandwidth plans. The remaining models are unlimited bandwidth, concurrency, configurable, or quote-only. In total, 532 rows are outside those three traffic-priced models. Dataset snapshot, all evidence retrieved 2026-07-25

This is why a single “price per GB” league table cannot represent the market. A per-IP plan may include a traffic allowance, fair-use ceiling, or no published bandwidth term. A traffic plan may expose a large rotating pool without selling any fixed IP count. Unknown fields stay unknown under both models. Dataset methodology and plan evidence, retrieved 2026-07-25

Start by naming the scarce resource in the job. If the job needs a fixed number of addresses, compare qualifying per-IP receipts. If it needs a known traffic volume from a rotating pool, compare qualifying traffic receipts. If it needs both, require both values to be published and reject any row that cannot prove one of them. Dataset methodology and plan evidence, retrieved 2026-07-25