How Many US IPs a Stateside Line Rotates Through in a Campaign
Published
A client asks how many different addresses a verification team will appear from over a month-long campaign, and the honest answer is not the one most proxy advertising gives. One Stateside Proxies line has one SIM in one device, and when you rotate it the carrier's regional gateway hands it another public address from a finite pool shared with that region's real phones. Over a campaign that is a few hundred to a few thousand distinct addresses per carrier per metro, not millions. This guide explains where the addresses come from, why the same one can come back, why that is harmless, and how a team can count the pool behind its own line in an hour.
Where the addresses come from
A phone or modem has a private address inside the carrier's network. The gateway for its region translates that into a public address shared with many other devices. Each carrier runs a modest number of gateways per region, each with a block of public addresses, and that block is the pool behind a line. A Chicago line draws from the gateways serving Illinois; move it to Miami and it draws from Florida's. The pool belongs to the carrier and the metro, not to the line.
What rotation does
Rotation drops the device's data session and brings it back. The gateway assigns whatever public mapping is free, almost always different from the one just released. It takes a few seconds. The carrier can also re-map a session on its own, which is why an address left alone for many hours sometimes changes without anyone asking.
The honest number
Hundreds to a few thousand distinct public addresses per carrier per metro over a long run of rotations. T-Mobile gateways tend to show the widest set and the tightest match to the metro; AT&T hubs serve wider regions; Verizon gateways can place the address in another city of the same state. Claims of millions describe residential pools spread across many homes and many vendors, which is a different product. For verification and research, which rotate between tasks rather than on every request, all three carriers are deep enough.
Repeats and why they do not matter for marketing work
A finite pool means an address you held earlier can return, sooner in a quiet metro at night and much later in a busy one by day. For ad verification and research that is harmless: the address is still the carrier's, still cellular, still in the metro, and a publisher sees a phone that happens to share a public address with one it saw before, which is normal on a carrier network. If a specific check requires a guaranteed-new address, rotate, look it up, and rotate again if it matches a recent one.
Counting your own pool
A team can measure instead of trusting: rotate on a timer, look the address up after each rotation, count the distinct results. An hour gives a first picture, a day a fair one. The rotation link from the line's card and any IP lookup page are all it takes, and no programming is needed if someone is willing to click.
- In the dashboard, open the line's card and take its rotation link from there.
- Open the link, wait twenty seconds, then load an IP lookup page through the line and note the address, carrier and city.
- Repeat once a minute for an hour, or automate it with a short script if someone on the team writes them.
- Count the distinct addresses and note when the first repeat appeared.
- Repeat in another metro after a free move and compare.
What this means for a campaign plan
For planning, the useful question is not how many addresses exist but how many your work really needs. A verification team that rotates between sessions uses a handful of addresses a day and will never exhaust a pool. A research task that needs a new address for every page is a different job, and it is better spread over residential data than forced through one line. Where a client contract specifies a number of distinct addresses, count them with the method above and report what you measured, rather than quoting a figure from anybody's marketing, including ours. A measured figure, with the carrier, the metro and the date beside it, is also something a client can check for themselves, which tends to end the conversation. Date every count you keep.
Frequently asked
How many addresses will a month of verification use?
As many as you rotate to, from a pool of hundreds to a few thousand per carrier per metro. Most teams rotate between sessions and see a few dozen a week.
Does rotating change the metro?
No. Every address comes from the same carrier gateway for the same region. Moving metros is a separate, free action in the dashboard.
Is a repeat a problem?
Not for verification or research. The address is still the carrier's and still in the metro; publishers see ordinary carrier traffic.
Which carrier gives the most addresses?
T-Mobile shows the widest set in our observations. Count your own line with the steps above rather than relying on any claim, ours included.
