Most questions we get about US static residential proxies are variations of three: are these really AT&T and Verizon addresses, can I pick the state, and which one is "best" for my accounts. The short answers are yes with a caveat, partly, and it depends on what you log into. The long answers are below, along with the jobs a static IP is simply the wrong tool for.
What a US static residential IP actually is
A static residential proxy, also sold as an ISP proxy, is an IP address that a consumer internet provider has registered as part of its residential range, but which is routed to a server in a datacenter rather than to a house. The address never changes for as long as you rent it. To any site that looks it up, the ASN and the WHOIS record say "residential broadband customer of ISP X". To your scraper or browser, it behaves like a datacenter proxy: fast, always on, and unlimited in how much data you can push through it.
That combination is the whole product. You get the trust of a household address with the reliability of a server, and you give up the one thing rotating residential proxies have: a fresh IP whenever you want one. For a deeper comparison with the rotating kind, see static residential proxies explained.
Are they really from AT&T or Verizon?
Yes, in the sense that matters to most detection systems, and no, in the sense that a purist would mean.
The IP is genuinely registered to a US consumer ISP. The large national networks are the ones you see most often in static residential pools: AT&T, Verizon, Comcast (Xfinity), Charter (Spectrum), Cox, plus regional providers such as Frontier or Lumen. When a website checks the ASN, it sees that ISP. When it checks a geolocation database, it sees a US city in that ISP's footprint. That is why these addresses pass checks that a datacenter IP fails on arrival.
What is not true is that a cable modem in someone's living room is forwarding your traffic. The address is announced from datacenter hardware under a commercial arrangement with the ISP. Some detection vendors maintain lists of ranges known to be leased this way, so a static residential IP is not invisible; it is trusted by default, which is different. On most platforms that default is what you are paying for.
You usually cannot choose the ISP. You choose the location, and the pool assigns an address from whichever ISPs serve it. If a specific ISP matters, for example matching the carrier your customers actually use, ask before you buy rather than assuming.
Can you target a specific US state?
Partly, and the way it works is worth understanding before you rely on it.
Static residential inventory is organised by city, not by state. In our own checkout you pick the country and then a city from the available inventory, and the state follows from the city: a Dallas address is a Texas address. So if the requirement is "a Florida IP", pick Miami or another Florida city. If the requirement is "any US IP", leave the city unset and let the pool choose.
Two limits apply everywhere, not just with us.
- Inventory is uneven. Large metros have hundreds of addresses; smaller states may have few or none at a given moment. If you need a specific low-population state, check availability before committing to a workflow that assumes it.
- Geolocation is what the databases say, not what the map says. A site decides where your IP is by looking it up in MaxMind, IP2Location or a similar database. Those databases are usually right about the state and sometimes wrong about the city, and they disagree with each other. Verify with more than one lookup before you build state-level logic on an address.
If you need to change state often, or you need many states at once, a static IP is the wrong shape. Our rotating datacenter proxies target by country, state and city on every request, and premium residential offers city targeting across a 130M+ pool of real household addresses. Static residential is for holding one location, not for touring them.
Which one is "best" depends on what you log into
There is no best static residential proxy in the abstract. There is a best fit for a workflow.
| What you are doing | Right tool | Why |
|---|---|---|
| Managing accounts on marketplaces, social platforms or ad networks | Static residential | Platforms expect one user at one stable address. An IP that changes daily is the signal that triggers a review. |
| Checking localised prices or search results across many US cities | Rotating residential with city targeting | You need many locations, not one, and you need them to look like shoppers. |
| Retail drops and limited releases | Static residential, several IPs | Residential trust plus datacenter speed, and each IP holds its own session and cart. |
| Ad verification across regions | Rotating residential or mobile | You are checking what real users in many places see; one static address shows you one place. |
| High-volume scraping of protected sites | Rotating residential | A single IP hits per-IP rate limits long before it finishes the job. |
| APIs and public data | Static datacenter | Nobody checks reputation, so pay datacenter prices. |
What static residential proxies can't do
These are the cases where people buy static IPs and then write to support. Save yourself the ticket.
- They do not rotate. If a target blocks your address, that address stays blocked. You buy another one; you do not get a new one for free. Plan for burn on hostile targets.
- One IP is one identity. Running twenty accounts through a single static residential IP links them to each other. The whole point of the product is a stable one-to-one mapping between an address and an account. Buy one per identity.
- Per-IP rate limits are your ceiling. Unlimited bandwidth from the provider does not stop the target counting your requests. Scraping tens of thousands of pages an hour from one household-looking IP is exactly what looks like a bot.
- Geolocation can drift. An ISP occasionally re-homes ranges, and databases update on their own schedule. If a platform suddenly thinks your Chicago IP is in Ohio, that is why.
- They are not anonymity tools. The proxy hides your origin IP from the site. It does nothing about your browser fingerprint, cookies or account history, which is what actually identifies you on the platforms that use static residential proxies most.
Pricing and terms
Our static residential proxies cost $3.90 per IP per day, $7.90 for 30 days, $15.00 for 60 days and $21.00 for 90 days. Bandwidth is unlimited, the address never rotates, and both HTTP(S) and SOCKS5 are supported. The pool covers 31+ countries, with the US the largest. A day plan is the cheapest way to check that a given city and ISP work for your target before you commit to a month.
Before you buy: a five-point check
- Look up the IP before you use it. Confirm country, city and ASN with an IP lookup, and do it again with a second database if the state matters.
- Decide how many identities you need. Then buy that many IPs. Not fewer.
- Check the platform's own view of location. Log in through the proxy and see what the platform shows as your location. Its database is the one that counts.
- Match the rest of the environment. Set the browser timezone and language to the IP's location. A Miami IP with a Berlin timezone is a mismatch every fraud system flags.
- Keep a rotating pool for collection. Use the static IP for the account, and a rotating residential plan for anything that looks like scraping. Mixing the two on one address is how good IPs get burned.
Frequently asked questions
Are static residential proxies from AT&T or Verizon?
The addresses are registered to US consumer ISPs, and AT&T, Verizon, Comcast, Spectrum and Cox are the networks that appear most often, alongside regional providers. The IP is routed to datacenter hardware under an arrangement with the ISP rather than to a home, so ASN and geolocation checks see a residential customer while you get server reliability. You normally choose the location, not the ISP.
Can static residential proxies target specific US states?
Yes, through the city. Inventory is organised by city, so you pick a city in the state you need and the state follows. Coverage is deepest in large metros and can be thin in smaller states, and IP geolocation databases occasionally disagree on the city, so verify an address with more than one lookup before relying on it for state-level logic.
Can I get residential proxies from specific US states?
Yes. For a fixed address in one state, use a static residential proxy in a city there. For many states at once or frequent changes, rotating residential proxies with city targeting, or rotating datacenter proxies with state targeting, are the right shape. A static IP is for holding one location, not for switching between them.
What is the best static residential proxy for US accounts?
One dedicated IP per account, in a city that matches the account's declared location, from an ISP with a consumer footprint there, paired with a browser whose timezone and language match. The provider matters less than the discipline of never sharing that IP with scraping traffic or other accounts.
Do static residential proxies have unlimited bandwidth?
Usually yes, because the bandwidth comes from a datacenter port rather than a household connection. Ours is unlimited at every term length. The limit that still applies is the target's own per-IP rate limit, which no bandwidth plan can remove.