dropstride.
PLAN FROM YOUR ACTUAL TRAFFIC

What can 1 GB cover?

Enter measurements from your client. Account for extra attempts, traffic overhead and a reserve before planning your per-IP workload.

Average bytes sent per attempt; 1 KB = 1,000 bytes.

Average bytes received, including relevant assets.

10% means one extra attempt per ten original operations.

Reserve for bytes missing from your input measurements.

Leave some of the 1 GB allowance unplanned.

Count the original operations, before extra attempts.

ESTIMATE FOR ONE PROXY6,926 operations

Within your allowance after the selected reserve.

Planned transfer
115.5 MB
Full allowance used
11.55%
Per original operation
115.5 KB

Your planned workload fits the estimated budget.

This is arithmetic from your inputs, not measured service usage or a promise of completed requests.

The formula behind the estimate

Bytes per operation = (request KB + response KB) × 1,000
                      × (1 + extra attempts / 100)
                      × (1 + overhead / 100)
Available bytes = 1,000,000,000 × (1 − reserve / 100)
Estimated ceiling = floor(available bytes / bytes per operation)

With the example inputs, 100 KB of combined request and response traffic becomes 115.5 KB per original operation after 10% extra attempts and 5% overhead. Reserving 20% of the allowance leaves 800 MB, enough for an arithmetic ceiling of 6,926 operations. Actual traffic can vary.

Measure both directions and the whole task

Use representative combined traffic from your actual client. A page body alone omits requests, assets and protocol overhead. Include monitoring and failed attempts in your workload. If the measurement already includes a factor, set its additional percentage to zero to avoid counting it twice.

The extra-attempt input counts additional attempts per original operation. It is not a probability of repeated failure. Response sizes can change, and a failed attempt may use a different amount of data from a successful one.

Separate allowance from time

Each Dropstride IP includes 1 GB, meaning 1,000,000,000 bytes of combined traffic. It stops at that limit or the 24-hour rental expiry, whichever comes first. This calculator does not estimate request speed, retailer acceptance or how many tasks will finish before expiry.

Allowances are per proxy and cannot be pooled. Use the same calculation separately for each workload. Read how metering and expiry work and compare daily and monthly rental commitments.