How we scaled our residential pool past 120M IPs

"120M+ IPs" is a number we put on the homepage, but pool size on its own is a vanity metric. What matters is how many of those IPs are actually online, consenting, and useful for a given country or city at any moment. Here's what actually went into growing the network this year without diluting quality.

Consent-based sourcing, not volume at any cost

Every residential IP in our pool comes from a user who explicitly opted in through InsideProxy's own SDK — never bundled silently into another app. That constraint slows growth compared to networks that don't ask, but it's the difference between a pool that survives an audit and one that doesn't.

Density over raw count

A pool with 50M IPs concentrated in 20 major cities is more useful in practice than 200M IPs spread so thin that any given city has a handful of exits. This year's growth was deliberately targeted at filling gaps — mid-size cities in the US and EU where density was thin — rather than just adding total count.

Faster churn detection

Residential IPs come and go as real devices connect and disconnect. We rebuilt the health-check layer this year to detect a dead exit within seconds instead of minutes, which matters more for reliability than pool size ever will — a smaller pool that always routes through live IPs beats a bigger one with stale entries.

What's next

The next phase is deeper ASN-level targeting inside the residential pool, so requests can be pinned to a specific carrier network, not just a city. That work is already underway and will ship as an addition to the existing targeting syntax — no changes required on your end to start using it once it's live.