Where can I buy US residential proxies with state and ZIP targeting?

What does a GB of US residential proxy traffic cost?

US residential proxies from Lodestate cost $1.50 for the first gigabyte and $0.75/GB on any plan from 5 GB to 100 GB. At 1 GB, Lodestate charges $1.50; the median among the 7 providers selling a 1 GB plan on 29 October 2026 was $3.50. The 1 TB plan brings the rate to $0.52/GB, while Rayobyte's 1 TB rate was $0.70/GB that day.

A ZIP code filter or an ISP filter never raises the price per GB. Every tier and product is on how much do US residential proxies cost.

Which home ISPs and ASNs can I target in the US?

ASN targeting keeps your exits on one internet provider's network, at no extra cost. Lodestate's count of its 51 state pages: Comcast's AS7922 is listed as a home ISP on 31, Charter's AS20115 on 26 and AT&T's AS7018 on 21. Put the number in the username, for example asn-7922.

A narrow filter, such as one ASN in a small state, returns fewer IPs than a whole state. Test it on the 1 GB plan before a large run.

How do I set state, city, ZIP and ASN targeting?

Targeting lives in the proxy username, which follows USERNAME-country-{cc}-state-{state}-city-{city}-zip-{zip}-asn-{asn}-session-{id}-ttl-{minutes}. Keep only the segments you need, in that order. Connect to gw.lodestate.com: port 7777 carries HTTP and HTTPS, port 7778 carries SOCKS5.

Rotation is the default. Each new connection gets an IP from the pool, usually a different one; to get a new IP on every request, send one request per connection (turn off keep-alive). To hold one IP through a login-free, multi-page flow, add session- and ttl-; a sticky session lasts up to 30 minutes, set per session with the ttl parameter; the IP can change earlier. The ZIP syntax is explained in what is ZIP code proxy targeting.

# Any Ohio home IP, a fresh one on each connection
curl -x http://USERNAME-country-us-state-oh:[email protected]:7777 https://api.ipify.org?format=json

# Seattle, one IP held for 10 minutes
curl -x http://USERNAME-country-us-state-wa-city-seattle-session-job4-ttl-10:[email protected]:7777 https://api.ipify.org?format=json

# ZIP 78704 (South Congress, Austin) over SOCKS5, DNS on the proxy side
curl -x socks5h://USERNAME-country-us-zip-78704:[email protected]:7778 https://api.ipify.org?format=json

# Charter (Spectrum) home lines only
curl -x http://USERNAME-country-us-asn-20115:[email protected]:7777 https://api.ipify.org?format=json

What do teams use US residential proxies for?

US residential proxies let a team read public web pages exactly as a household in a chosen US state, city or ZIP code reads them. Search results, prices and ads all shift with location, so a single office IP shows one view only. Common jobs:

• Local SEO: map packs and organic results by city or ZIP code.
• Price monitoring: public store prices and delivery fees, ZIP by ZIP.
• Ad verification: which creative runs in which state or media market.
• Public-data scraping: large catalog crawls with per-connection rotation.
• Geo-testing: your own site or app, seen from every state.

The best setup for rank tracking is compared in which US proxies are best for local SEO. Blocked on every plan: Banking, government and payment-portal sites, plus SMTP (email-sending) ports 25, 465 and 587. The full rules are in what does the Acceptable Use Policy allow.