United States proxies

In Europe a country-level address usually answers the question. In the US it usually does not, and that single fact drives most of what you should buy here.

American targets routinely serve different content by metro: stock, delivery estimates, local search results, advertising and regional broadcast availability all change with the exit address. A country-level request returns whichever state the gateway happened to pick, and repeating it returns a different one, so consecutive runs disagree for reasons that have nothing to do with the site.

Some targets go further and simply do not render outside the states they are licensed in, which reads as an empty page rather than an error. A scraper that treats an empty result as no data will quietly record absence where the truth is that it asked from the wrong state.

The practical consequence for what you buy: if your target varies by metro, you need city targeting plus a sticky session so a single run stays in one place, and a fallback for when the city is unavailable. If it does not vary, country level is more reliable and cheaper to run.

The country code is US, upper case. The city goes after it with _city_, hyphens instead of spaces.

Static American addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.

In the Netherlands city targeting is a refinement. In the United States it is frequently the entire job.

Device density in the large metros is high, so New York, Los Angeles, Chicago, Houston, Miami, Dallas, Atlanta and Seattle are usually available. Smaller cities fail more often, and the further you get from the coasts the more noticeable that becomes.

Write the fallback in advance and record whether it fired. A silent drop from city to country level is how a spreadsheet ends up holding prices for a state you never asked about, and nothing in the data itself will tell you.

One subtlety worth knowing: the city in a geolocation database and the delivery city a retailer uses are not the same thing. An address that geolocates to Newark may behave as New York metro for tax purposes. If tax is what you are measuring, verify at checkout rather than trusting the city label.

The order is the same as everywhere, but American datacenter inventory is the cheapest and largest we hold, so starting there pays off more here than elsewhere.

The US is the largest market for limited releases, and a good share of the people reading this page came for exactly that. So here is what a proxy does and does not do.

It does stop a site seeing forty attempts arrive from one address. That is a necessary condition, and without it nothing else is worth discussing.

It does not turn forty sessions into forty people. Browser fingerprint, payment instrument, delivery address, account age and behaviour all weigh more than the address, and the platforms this is aimed at have spent years on precisely that problem. Anyone selling proxies as the solution for drops is selling a component and calling it a solution.

The working setup is one ISP address per identity where the identity is long-lived, or mobile where the platform expects a carrier. Rotating residential is the worst choice here: an address that changes mid-session looks more suspicious than a stable address in another state.

American mobile is available and behaves as it does everywhere: the modem sits behind carrier-grade NAT next to real subscribers, so the address is shared with people on the same operator. That sharing is what buys the tolerance.

Rotation is a physical reconnect rather than a routing decision, so it takes seconds and the same address sometimes returns. Operator selection is available, and the operators you can actually pick are listed in the dashboard rather than on a marketing page.

At $5.76 per day this is the most expensive way to hold an American address, and it earns that only when the target specifically expects carrier traffic.

Three scenarios at our prices, so you have something to check a quote against.

Several of these are the opposite of the European ones, which is why experience in Europe misleads people here.

The country is wide enough that the physics show up in your logs. A round trip from Frankfurt to a New York exit is a different number from Frankfurt to Los Angeles, and when you are running a hundred thousand requests a day that difference stops being trivia.

Two rules cover most of it. Put your workers on the side of the Atlantic where your targets are, because the hop you control is the one between your machine and our gateway. And when you need coast-specific results, ask for the city rather than hoping the gateway picks nearby.

What does not help is tuning timeouts downward to compensate. Thirty seconds is the right client timeout for residential exits regardless of coast, and shortening it throws away working routes that were merely slow. Throughput comes from running more addresses in parallel, not from giving each one less patience.

Datacenter addresses are the exception worth knowing: American datacenter capacity is fast enough that latency rarely enters the conversation at all. If your target does not filter hosting ranges, you get both the cheapest traffic and the fastest routes in the same product.

American advertising is not bought by country. It is bought by metro area, and the industry has its own map for it: designated market areas, which cut the country into a couple of hundred regions that do not follow state lines.

That means verifying a US campaign from a single American address tells you almost nothing. A creative bought for the Chicago metro will not render for an address in Phoenix, and the absence proves nothing about whether the campaign is running correctly.

The practical setup is one sticky session per metro you bought, held for the length of the check, with the profile timezone matching the city. Rotating between checks is fine; rotating during one is how you end up with screenshots of two different placements stitched into one report.

Cost is not the constraint. Two hundred placements a day at roughly 400 KB each is under 2.5 GB a month, which is under three dollars of residential traffic. The expensive parts of ad verification are the browser automation and the people reading the output, in the US exactly as everywhere else.

The same login string in three shapes. Note that the timezone is set from the city rather than the country.

There is no single federal privacy law in the United States. There is a patchwork of state laws, starting with California, and your obligations follow whose data you collect rather than where your traffic exits. Routing through an American address does not place you under US law, and it does not take you out of the GDPR if your dataset includes people in Europe.

This is general information rather than legal advice. Our terms require lawful use and we act on abuse reports. Where the answer carries commercial risk, ask a lawyer rather than a proxy provider.

Under a minute. In the US the usual two checks gain a third: confirming you got the city you asked for rather than just the country.