What Is IP Pool Exhaustion?
IP pool exhaustion describes the condition in which a vote delivery provider has consumed every available unique IP address for a specific target geography, contest, or delivery window, and has no remaining addresses to rotate to before the platform’s per-IP deduplication window resets. At that point, the only addresses left are ones the platform has already seen — either from the current campaign or from prior orders — and the delivery engine faces an unavoidable choice: reuse those addresses and risk triggering duplicate detection, or halt delivery and leave the order underfulfilled.
The IPv4 address space is finite. RIPE NCC — the Regional Internet Registry for Europe, the Middle East, and Central Asia — exhausted its general IPv4 allocation pool in November 2019, and ARIN reached its final IPv4 blocks in 2015. Wikipedia’s article on IP address exhaustion documents the global timeline in detail. The scarcity of new allocations means that residential IP pools are a fixed resource: a provider with a pool of one million residential addresses for Germany cannot simply acquire another million on short notice if a high-volume campaign depletes what is available in their roster. New addresses enter the pool only as ISPs reallocate blocks, as new mobile subscriptions come online, or as previously excluded addresses pass re-validation checks.
Pool exhaustion is not a theoretical edge case — it is a routine operational constraint that distinguishes providers with deep, genuinely diversified residential pools from those operating from a narrow set of recycled or shared addresses.
Why It Matters in Vote Services
The practical manifestations of pool exhaustion in a vote campaign are subtle but consequential. When a provider begins reusing IPs, several things happen simultaneously on the platform side:
First, the platform’s per-IP vote deduplication rule fires. Most contest platforms maintain a per-IP vote log with a window ranging from 24 hours to the lifetime of the contest. An address that appears a second time within that window is rejected — silently in most cases, or with an error code visible only in server logs.
Second, velocity analysis — a core component of anomaly detection — flags the pattern. Even if the second appearance of an address falls outside the deduplication window, abnormally high reuse rates across the campaign as a whole produce a statistical signature. The platform may not invalidate individual votes but will quarantine the entire campaign’s recent submissions for manual review.
Third, contest platforms with cross-campaign databases can detect that an IP which voted in one contest three weeks ago is now appearing in a different contest for a different candidate. Repeated appearance of the same addresses across contests is a strong fraud signal even when each individual vote would be accepted in isolation.
The geographic dimension amplifies the problem. A regional contest — a city mayoral vote, a local radio award, a national food blogger competition — requires addresses from a specific country or metro area. If the provider’s pool for that geography is small, exhaustion occurs far sooner than for a global campaign, and the reuse rate climbs faster.
How Detection Systems Use This Signal
Detection of pool exhaustion-related fraud relies on time-series analysis and cross-campaign correlation rather than simple per-IP rules:
- Address reuse frequency analysis — the platform tracks how often each IP address appears across its vote logs over a rolling 30-day window. Addresses that appear more frequently than the 99th percentile of organic voter return rates are flagged and their votes are retroactively reviewed.
- Campaign-level IP overlap scoring — for large orders, the platform compares the set of addresses seen in the current campaign against its historical address database. An overlap rate above a defined threshold (e.g., more than 15% of addresses seen in prior submissions to the same platform) triggers a fraud alert for the entire batch.
- Geographic concentration combined with reuse — the platform checks whether the reused addresses are concentrated in a narrow geographic range. Organic voters who return to vote a second time are typically spread across many locations; reused addresses from a depleted pool cluster within the provider’s available geography.
- Temporal clustering of reuse events — pool exhaustion typically produces a characteristic pattern in the time series: address diversity is high at the start of a campaign and drops sharply as the pool runs dry. The inflection point — where address reuse rates climb steeply — is a signal that automated delivery systems look for specifically.
- Cross-platform shared intelligence — fraud databases aggregating signals across multiple contest platforms can identify addresses that cycle through different contests in short succession, exposing pools that are shared across many clients and campaigns simultaneously.
How to Verify Quality
Pool depth and geographic coverage are among the most important criteria for evaluating a vote provider. Ask:
- What is the total size of your residential IP pool for the specific country I need, and how many of those addresses are clean (never seen on this contest platform before)?
- What is the maximum order size you can fulfil for my target geography before you begin reusing addresses?
- How do you handle address refresh — what is the typical cycle time before a used address re-enters your available pool?
- Do you maintain separate pool segments per client, or do clients share the same address inventory? Address sharing across clients accelerates per-platform exhaustion.
- What happens to the remainder of my order if your pool for my geography is exhausted mid-campaign — do you pause, substitute from adjacent geographies, or complete the order with reused addresses without informing me?
A provider that cannot answer pool-depth questions with specific numbers for your target geography is almost certainly working from a shared or undifferentiated pool that exhausts quickly on high-volume orders.
How Our Service Uses This Technique
Pool depth management is one of the operational pillars of our infrastructure. Our 6M+ residential address pool is partitioned by country, by ISP type (fixed-line versus mobile), and by per-platform usage history. Before executing any campaign, our allocation engine calculates how many clean addresses — those not previously seen by the target platform within its deduplication window — are available for the required geography. If the clean count is below the order volume, we surface this constraint before order confirmation rather than silently fulfilling a partial order. Our CGNAT-aware engine additionally distinguishes mobile carrier addresses that are structurally shared across many subscribers from dedicated fixed-line addresses, applying appropriate delivery pacing and per-address usage accounting so that CGNAT-shared IPs are never over-committed against their effective deduplication capacity. Drip-feed delivery scheduling allows the platform’s per-IP deduplication window to reset between delivery batches, extending the effective reach of the pool and reducing reuse rates for long-duration campaigns.
Summary. IP pool exhaustion occurs when a provider runs out of unique residential addresses for a target geography and is forced to reuse previously seen IPs, triggering per-IP deduplication rules and cross-campaign correlation analysis on the destination platform. Detection systems track address reuse frequency, campaign-level IP overlap, and temporal diversity collapse to identify exhausted pools. Our 6M+ address pool is partitioned by geography and per-platform usage history, with pre-campaign clean-count validation and drip-feed scheduling that extends pool effective capacity across long campaigns.
