How we count our pool

Figures on this page are read live from our own systems each time you load it.

We do not sell you a share of a pool

Most networks hand you an address drawn from a large shared bucket. Which address you get, whether you keep it, and who used it before you are decided by an allocator you cannot see.

VeilSocks works the other way round. When you start a plan you pick a country, region, city and carrier, and we rent a mobile line at that location for you. It is a real SIM on a real carrier network, held for a known window, and you can rotate its address yourself. A shared line carries a small, capped number of customers. A dedicated line carries exactly one.

That is why "how many IPs do you have" is the wrong question to ask us, and why we answer a more useful one instead: what will you actually be given, and who else is on it?

The live figures

Reading current figures…

The seven questions worth asking any provider

These are the questions that make two pool figures comparable. Ask them of us, and of anyone you are comparing us with. Our answers:

1. What is the measurement window?

Instantaneous. Every figure above is read when you load the page, from the same systems that serve traffic. Nothing is a rolling total, a monthly maximum, or a cumulative count of everything we have ever seen.

2. What counts as one unique resource?

One exit address on one line, for one continuous period. If a line rotates onto a new address, that closes one record and opens another — we do not count the same address twice because it came back, and we do not count one address as several because several customers used it.

3. What makes a resource eligible?

It must be a line we are currently paying for, at a location the upstream network reports as available, that has passed our own connection check and is not disabled by us. Locations we cannot buy at this moment are excluded from the coverage figures, even if we sold them last week.

4. What is the geographic scope?

Everything above is global across our whole network — there is no separate regional figure that looks better. The coverage table breaks it down country by country so you can see exactly where the number comes from.

5. Does the figure mean inventory, or what is available now?

Available now. Coverage is what you can buy at this instant. Sharing and exclusivity are measured over live lines and our recorded address history, not over a catalogue.

6. Is the same set available to every customer?

Yes. We do not run tiers where a plan, a zone or a support relationship unlocks a better set of addresses. The only difference between plans is how many customers share a line — four at most on a shared line, exactly one on a dedicated line.

7. Can you explain how the figure is collected?

Each number is served by our own API together with the definition used to produce it, so the method travels with the figure instead of living in a footnote. You can read it directly at /api/public/pool.

The three numbers that actually predict whether a proxy works

Pool size tells you very little about whether your account survives. These do, and they are the numbers you will rarely see printed:

How many customers are on your address

Every additional person behind an address is another chance that someone else's behaviour is what gets it flagged. We cap a shared line at four customers and publish the live average. A dedicated line is one. A network that draws from a bucket of millions cannot tell you this number, because it changes with every request and is frequently very large.

Whether anyone had it before you

An address with history arrives already carrying whatever the last person did with it. We keep a record of every address we have served from and who was on it, so exclusivity is something we measure rather than assert. The live figure is above.

How long you keep it

An address you lose mid-task is worse than a slower one you keep. Ours is held for the rental window you bought, not until an allocator decides otherwise, and rotation happens when you ask for it.

Check it yourself

None of this is worth anything if you have to take our word for it. So:

1. Read the raw figures. /api/public/pool returns everything on this page as JSON, each number with its definition attached.
2. Buy one gigabyte. That is the smallest order we sell, and it exercises the same provisioning path as the largest.
3. Check the address you are given. Confirm the carrier and location match what you asked for, and that it is a mobile carrier range rather than a hosting provider.
4. Hold it. Come back an hour later and confirm it is the same address.
5. Ask us who else is on it. We keep that record, and we will tell you.

What we do not publish, and why

We do not headline a total address count.

It is the easiest figure in this industry to inflate — widen the measurement window, count every address ever observed, add every location you can theoretically reach — and the hardest for a customer to check. A test can only ever show you what appeared under your own conditions, which means almost any headline number is unfalsifiable by design.

We would rather publish figures that get worse if we behave badly. Customers per address rises if we oversell. Exclusivity falls if we recycle addresses. Coverage drops if the upstream network shrinks. Every number on this page is one we would have to explain if it moved the wrong way — that is the point of choosing them.

Questions about any of this: support@veilsocks.com or Telegram.