USA Proxies: 4,756,709 US Residential, ISP & Mobile IPs

Our residential proxies are the default choice for USA traffic. They are real IP addresses assigned by American ISPs — Comcast, Spectrum, AT&T, Verizon and hundreds of regional providers — to real households. To the site you are visiting, a request through one of these looks like an ordinary person browsing from Ohio or Georgia, because at the network layer that is exactly what it is.

The US pool holds 4,756,709 addresses, the largest single-country pool we operate and part of a 35M+ global network. That depth matters more than it sounds: sites that rate-limit by IP only become a problem when you exhaust the pool, and at nearly five million American IPs most scraping jobs never revisit the same address twice.

Rotating vs sticky sessions

USA rotating proxies assign a fresh American IP to every single request. This is what you want for high-volume collection — price monitoring, search result scraping, catalogue crawls — where each request is independent and being seen as one continuous visitor is a liability rather than a benefit.

Sticky sessions do the opposite: they pin one US IP to your session for up to 24 hours. Use these whenever state has to survive between requests — logging into an account, walking through a checkout, or any multi-step flow that breaks the moment your IP changes mid-journey.

You choose per request, not per plan. Both modes are included on every residential plan, so a single set of credentials can run a rotating crawler and a sticky account session at the same time.

Which residential plan

• Residential Budget — $0.39/GB. The cheapest way into the US pool. Best when volume matters more than the very highest success rate.
• Residential — $2.29/GB. The standard tier, with the full 35M+ pool and 195+ countries if your project later outgrows the US.
• Unlimited Residential Budget — $5.00/day. Unmetered bandwidth billed by time instead of gigabytes, which is far cheaper once you are moving serious volume.
• Unlimited Residential — $20.00/hour, with 9M+ active IPs on a server dedicated to you alone.

A rotating pool is the wrong tool when a platform expects to see you arrive from the same place every time. That is the job of static ISP proxies: an American residential IP, registered to a real US internet provider, that is assigned to you and nobody else for as long as you keep the plan. These are sold under several names — private USA proxies, dedicated USA proxies, static residential USA proxies — and they all describe the same thing: a US IP with a single tenant.

That single-tenant part is the distinction that matters. On a rotating pool the IPs are shared, so the reputation of any given address reflects whatever everyone else did with it. On a private US proxy the address is yours exclusively and its reputation is shaped by your traffic alone. For anything tied to a long-lived identity — a social account, an ad platform login, a marketplace seller dashboard, a recurring report pull — that exclusivity is the whole point, and it is why dedicated USA residential proxies cost more per IP than pooled ones.

Static ISP or static datacenter?

Both give you a fixed US IP. They differ in what the address traces back to:

• Static ISP — $6.99/month. The IP resolves to a consumer ISP, so it carries residential trust. This is the one to pick for platforms that scrutinise where a login comes from.
• Static Datacenter — $4.99/month. The IP resolves to a hosting provider. Noticeably faster and cheaper, and perfectly adequate for targets that do not weigh IP origin heavily.

Both are month-to-month. If you are unsure which side of that line your target sits on, a small order on each is the fastest way to find out — it costs less than a day of guessing.

USA datacenter proxies trade residential trust for raw throughput. The IPs come from American hosting facilities rather than homes, which makes them dramatically faster and cheaper — $3.00/day — but also trivially identifiable as non-residential to any site that checks.

That trade-off is fine, and often correct, for a large class of work: hitting public APIs, monitoring your own infrastructure from a US vantage point, load testing, checking DNS and CDN behaviour on American edge nodes, or bulk-fetching pages from sites with no meaningful bot defences. Reach for datacenter first when the target does not care where you come from, and only step up to residential when it does.

IPv6 in the United States

We also run IPv6 across both flavours — IPv6 residential and IPv6 datacenter, each $3.00/day. The US is one of the few markets where IPv6 adoption is high enough for this to be genuinely useful rather than a novelty: major American carriers and content networks all speak it natively.

The practical draw is address space. IPv6 blocks are vast enough (80 Octillion addresses) that per-IP rate limits stop being a meaningful constraint at all. The catch is equally practical — a target that has not deployed IPv6 simply cannot be reached over it, so confirm your destination resolves an AAAA record before you commit. Our IPv6 test tool answers that in a few seconds.

USA mobile proxies route your traffic through IP addresses that American cellular carriers hand out to phones on 4G, 5G and LTE. Our Mobile USA plan covers this at $3.99/GB, with a pool of 50K+ dedicated AT&T carrier addresses. It is bought from the pricing page rather than the plan selector above, which lists our bandwidth and dedicated-IP plans.

They are the most expensive US proxies we sell, and there is a structural reason they are also the hardest to block. Mobile carriers put thousands of subscribers behind a single public IP through carrier-grade NAT. A platform that blocks one mobile IP is not blocking one user — it is blocking an entire cell tower's worth of real customers. Most decide the collateral damage is not worth it, which is why mobile addresses survive on targets where residential IPs start failing.

When the premium is worth paying

• Mobile-first platforms. TikTok, Instagram and Snapchat expect their US traffic to arrive from phones. A carrier IP is simply the ordinary case there, where a datacenter IP is an anomaly.
• Hardened account work. Where residential IPs are triggering verification steps, carrier IPs usually stop it.
• Mobile ad verification. Checking what a US mobile user actually sees requires being a US mobile user at the network level.

For anything less sensitive, US residential is a better buy — the success rate is close and the cost is a fraction. Our wider mobile proxy network extends the same approach to more than 100 other countries if your work is not US-only.

Country-level targeting is rarely precise enough for American work. Retail pricing, tax, delivery windows, ad creative, sports blackouts and legal restrictions all vary between states and often between metros in the same state. A proxy that lands you somewhere in the US tells you very little about what a shopper in Sacramento actually sees.

We expose all three levels through the proxy password. Append the parameters to your password and the gateway routes you accordingly — no separate endpoints, no dashboard round-trip:

• Country: USER:PASS_country-us@HOST:PORT
• State: USER:PASS_country-us_state-california@HOST:PORT
• City: USER:PASS_country-us_state-california_city-losangeles@HOST:PORT

State and city names are lowercase with spaces removed, so New York becomes newyork and Los Angeles becomes losangeles. Because the whole instruction lives in the password field, it works with any client that supports proxy authentication — curl, Scrapy, Playwright, Puppeteer, an off-the-shelf browser extension — without special support for our API.

Where the coverage is deepest

The US pool spans 51 states and 1,918 cities. Coverage tracks population, so the largest states carry the most granularity: California 198 cities, Texas 156, Florida 143, Ohio 122, New York 105, North Carolina 104, Georgia 85 and Illinois 78. Smaller states have fewer cities but every one of the 50 states plus Washington DC is represented.

Our California and Pennsylvania pages go deeper on those two markets, and the state grid above links to the rest.

US pricing runs from $0.39/GB for budget residential up to $3.99/GB for dedicated mobile carrier IPs. What you should actually pay depends far more on how your target defends itself than on how much data you plan to move.

Per-GB plans suit spiky or exploratory work where you would rather not commit; per-day and per-month plans win decisively once usage is steady. The crossover usually arrives sooner than people expect — if you are consistently moving more than a few gigabytes a day, unlimited is already cheaper.

Rather than model it, test it. A free trial or a $2 order is enough to run your actual target through a US IP and read a real success rate instead of a projected one. Full plan comparisons live on the pricing page.

Free US proxy lists are easy to find and, for a narrow set of uses, fine. If you want to confirm that a page renders differently from an American IP, or check a geo-redirect once, a free proxy answers the question and costs nothing. There is no reason to pay for that.

They stop being viable the moment the work is repeated or matters. Public lists are scraped and republished constantly, so the same handful of addresses is hammered by thousands of people at once — which is why most entries are dead within hours and the survivors are already on every major blocklist. Uptime is unpredictable, throughput is poor, and there is nobody to ask when it breaks.

The security gap deserves more attention than it usually gets. A proxy operator sees your traffic. Running an unencrypted request through an anonymous server means handing your data to someone whose motives you know nothing about, and free HTTP proxies have a long, documented history of injecting ads, stripping TLS and harvesting credentials. Never send a login through one.

Paid US proxies fix the operational problems — a pool of 4,756,709 addresses instead of a shared few dozen, state and city targeting, sticky sessions, HTTP and SOCKS5, and a support team that answers within a few hours — but the honest framing is that you are buying reliability and accountability, not magic. If your use case genuinely is one lookup, a free proxy is the right call. If it is a job that has to finish, it is not.

Either way, verify before you trust: our free proxy checker tests any proxy's country, anonymity level and response time, whoever it came from.

Every USA plan speaks HTTP, HTTPS and SOCKS5 on the same credentials. There is no protocol upcharge and no separate endpoint to provision — switch by changing the scheme in your connection string.

• HTTP / HTTPS — the right default for web traffic. Understands requests at the HTTP layer, which means it can cache and handle CONNECT tunnelling for TLS. Supported by essentially every scraping library, browser and HTTP client.
• SOCKS5 — operates lower down, forwarding raw TCP (and UDP) without interpreting it. That makes it protocol-agnostic: anything that is not HTTP — mail, custom TCP services, torrent clients, some automation tooling — works over SOCKS5 and will not work over an HTTP proxy.

One detail worth getting right: prefer socks5h:// over socks5:// in curl and most libraries. The h makes DNS resolve at the proxy rather than on your machine. Without it your own resolver leaks the hostname you are visiting, and you also lose US-local DNS — which matters, because plenty of American sites return different records by region.

Concurrent connections are not capped on any plan, so protocol choice is purely about what your client needs rather than what your licence allows.