US Residential Proxies in United States

What a "residential" IP means here, precisely

The US residential proxy market has a trust problem: at least half the pools advertised as "residential" are actually datacenter prefixes announced under recycled tier-3 ISP ASNs, or colocation allocations that passed through a trust laundry. Proxaro's US residential pool is two things and only two things:

• Operated last-mile partnerships. We run a consented peer program on desktop utilities in the US, and we have upstream commercial agreements with three tier-2 ISPs for supervised exit allocation. Every exit IP can be traced to either a signed peer record or an ISP contract. We keep the ledger auditable on request.
• No resale prefixes. We don't run traffic through pools we buy from anyone else. That rules out the cheap end of the market but it rules out the trust problem too.

That matters because the only reason to pay residential prices over datacenter is the trust signal at the exit, and that signal is worth nothing if the ASN isn't what it claims to be.

Carrier coverage, metro vs. tier-2

The US residential pool concentrates where the carriers concentrate:

• Major metros on Comcast and Spectrum — NYC, LA, Chicago, Miami, Houston, Dallas, Atlanta, Boston, Philadelphia, Denver, Seattle. At least 15,000 active exits at any given time across these markets, with Comcast density higher in the Northeast and Midwest, Spectrum density higher in the South and West.
• Secondary metros on Cox, Frontier, Xfinity, and CenturyLink — The Phoenix, Oklahoma City, Las Vegas, Nashville, Raleigh, Austin and Richmond markets, plus a growing Frontier footprint in Florida post-bankruptcy exit.
• Tier-2 cities — Spokane, Knoxville, Toledo, Tallahassee, El Paso and similar. Coverage here is thinner; if you need high concurrency in tier-2 metros, plan on rotating slowly and widening your DMA scope.

If your workflow depends on a specific sub-300k metro, ask us before committing — we'd rather tell you up front than pretend capacity we don't have.

The sticky-session math for logged-in US retail

A common Proxaro workload is logged-in account automation against a US retail target — watching a cart, refreshing a queue, holding a loyalty-tier state across a multi-step flow. The right sticky window is not "as long as possible." It's "as long as the real customer would hold."

A real residential user in Chicago does not keep the same public IP for 12 hours. Comcast rotates its dynamic allocations every few hours in most metros, and the underlying IP changes on router reboot and on DHCP lease expiry. A session that stays on the same IP for 8 hours is less human-looking than one that rotates at the 60-minute mark.

Our residential sticky window maxes at 60 minutes for this reason. For anything longer (queue-and-checkout on Shopify Plus, SNKRS queue hold), you want ISP, not sticky residential — they're different products and we price them differently on purpose.

Per-request rotation behaviour

On per-request rotation, you get a different exit IP on every connection. Real-world implication: if your scraper keeps a TCP connection open across 50 requests, you're on one IP for all 50. If it closes and reopens every request, you're on 50 different IPs. Keep-alive behaviour decides your rotation cadence more than the gateway does.

Implementation

curl --proxy http://USER:PASS@gateway.proxaro.io:7777 \
     --proxy-header "X-PX-Dma: 501" \
     --proxy-header "X-PX-Asn: as7922" \
     --proxy-header "X-PX-Session: sticky-30m" \
     https://example.com

The gateway is a single US anycast endpoint — gateway.proxaro.io. We don't offer regional gateway pins because the hop count from US-East to US-West inside our backbone is single-digit milliseconds and splitting the endpoint would fragment capacity for no real benefit.